[Development] Proposal to adjust release candidate process

[Thiago Macieira]

On segunda-feira, 27 de março de 2017 02:40:08 PDT Jani Heikkinen wrote:
> 2. After first beta release we don't deliver any binary snapshots anymore
> but do release additional beta releases ~ once per week (with more
> lightweight process than current releases are done: no blog post from every
> beta release, limited test round before additional beta N release and full
> test round when beta N is publicly available, no official approval from
> release team meetings ...) - This is mandatory step now when delivering
> snapshot & pre-releases via online installer: New snapshot / pre-releases
> are updates to previous one -> after beta2 is released there is no first
> beta available via online installer. 3. When beta N is well enough we will
> create and release RC.
> 4. If RC seems to be good enough we will release final but if some blocker
> found during RC testing we will release immediate RC2 (again with more
> lightweight process) etc..

Sounds good, but please remember we'll need to keep at least the source 
tarballs for each and every beta and RC that we release.

Maybe every week is too aggressive, since few people will test every week and 
give feedback in time for the next release. We may find that every other week 
is better.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center