mirror of
https://github.com/nextcloud/android.git
synced 2024-11-24 22:25:44 +03:00
update release cycle description
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
This commit is contained in:
parent
87379285aa
commit
742d42fdd2
1 changed files with 2 additions and 2 deletions
|
@ -178,11 +178,11 @@ beware, that beta releases for an upcoming version will always use the minor and
|
|||
For dev the version name is in format YYYYMMDD. It is mainly as a reference for reporting bugs and is not related to stable/release candidates as it is an independent app.
|
||||
|
||||
## Release cycle
|
||||
* for each release we choose several PRs that will be included in the next release. Currently there are many open PRs from ownCloud, but after merging them, the intention is to choose the PRs that are ready (reviewed, tested) to get them merged very soon.
|
||||
* these will be merged into master, tested heavily, maybe automatic testing
|
||||
* Releases are planned every ~2 months, with 6 weeks of developing and 2 weeks of stabilising
|
||||
* after feature freeze a public release candidate on play store and f-droid is released
|
||||
* ~2 weeks testing, bug fixing
|
||||
* release final version on f-droid and play store
|
||||
* Bugfix releases (dot releases, e.g. 3.2.1) are released on demand from the branch created with first stable release (stable-3.2.x). If changes to the library are required, we do the same: create a branch from the version used in stable release (e.g. 1.0.43) and then release a dot release (1.0.43.1).
|
||||
|
||||
To get an idea which PRs and issues will be part of the next release simply check our [milestone plan](https://github.com/nextcloud/android/milestones)
|
||||
|
||||
|
|
Loading…
Reference in a new issue