[ros-dev] [VOTE] Changes to release process

[Ge van Geldorp]

I received no feedback on the proposed change below, so I've created a vote
on the forum (http://www.reactos.org/forum/viewtopic.php?p=10003). The vote
will run for 7 days.

Gé van Geldorp.

>   -----Original Message-----
>  Our current release process is documented at 
>  http://www.reactos.org/wiki/index.php/Release_Management_Overv
>  iew. With the outcome of the TC function description vote, we 
>  need to change it to incorporate the TC role in the release 
>  process. I'd like to propose the following changes:
>  
>  - change "Once the project coordinator signals that a release 
>  is to be made, dates are set for all three stages and the 
>  release process begins." to "Once the testing coordinator (in 
>  consultation with the release engineer) signals that a 
>  release is to be made, tentative dates are set for all three 
>  stages and the release process begins.". Rationale: TC 
>  involvement, dates are not fixed but dependent on blocker bugs.
>  - change "At the time of feature freeze, the first release 
>  candidate is produced by the release engineer." to "At the 
>  time of feature freeze, a release preview is produced by the 
>  release engineer.". Rationale: "release candidate" is 
>  probably not the best term to describe the state of the .iso.
>  "Beta" is confusing since we're in alpha. "Preview" seems a 
>  nice generic term.
>  - change "Code freeze is the next stage of the release 
>  process." to "Code freeze, the next stage of the release 
>  process, is entered when the testing coordinator indicates 
>  that all blocker bugs in the release branch have been 
>  fixed.". Rationale: TC involvement.
>  - change "At the time of code freeze, the second and final 
>  release candidate is produced by the release engineer." to 
>  "At the time of code freeze, a release candidate is produced 
>  by the release engineer.". Rationale: I think we can safely 
>  call this one a release candidate.