Consider making RC releases [#3069394]

Just a proposal, feel free to reject.

In EVA, we have a huge user base and surely want to avoid regressions, but also like major cleanups and improvements.

Now that d.o supports this, we do it like this:
* Have 1.15 stable
* At some point, create a 1.16-rc1 release
* d.o will show them both and users can choose between well-hung and bleeding edge
* we have usage statistics for the rc (which we don't for dev)
* At some point, we release RC as stable and restart

Comments

Comment #1

22 July 2019 at 14:17

axel.rutz created an issue. See original summary.

Comment #2

itamair commented 22 July 2019 at 18:03

Interesting. Do we have documentation on this new feature (rc versions) on Drupal.org ?
To make more sure about naming conventions and deployment procedures, etc ...

Comment #3

itamair commented 22 July 2019 at 18:03

Status:

Active

» Postponed (maintainer needs more info)

Comment #4

itamair commented 22 July 2019 at 18:11

Anyway ... I got your point,
but sincerely I don't think it would be worth and necessary to add further tmp version branches,
and for instance now deploy a tmp 1.16-rc1 release, when there is already a 1.15 stable one.
In my case I am very quick and frequent in releasing new progressive stable project versions ... one after each other.
In the meanwhile, if the user doesn't want to rely on the dev branch (potentially unstable), he can add specific RTBC patches into his stable version, via composer via cweagans/composer-patches ...