RE: [ros-dev] RE: 0.2.9 RC2 is Out!

[Murphy, Ged (Bolton)]

Ge van Geldorp wrote:

>   Reminder to devs: with the release of 0.2.9-RC2
> we're now in 
>  code freeze for
>  the branch. During code freeze, the only allowed commits are 
>  bugfixes to
>  release-blocking bugs. These fixes are generally discussed on 
>  the mailing
>  list prior to committing a fix.
>  
>  GvG 
I'm not sure if I'm missing something here, but these rules seem to
contradict themselves.

According to the rules :
We don't move from Feature Freeze to Code Freeze until, and I quote "the
testing coordinator indicates that all blocker bugs in the release branch
have been fixed"

I interpret this as, we move to Code Freeze, when and only when all blockers
have been fixed.

We then dictate that "During code freeze, the only allowed commits are
bugfixes to release-blocking bugs"

If all blockers must be fixed before we move to Code Freeze, and we can only
commit bug fixes to free up blockers during Feature Freeze, what is the
actual point in having a Code Freeze as we will never have any blockers to
fix.

I hope that reads ok.

Ged.



************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk 
<mailto:[e-mail]> and then delete this message. 

Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com

[Ge van Geldorp]

>   From: Murphy, Ged (Bolton)
>  
>  According to the rules :
>  We don't move from Feature Freeze to Code Freeze until, and I 
>  quote "the testing coordinator indicates that all blocker bugs
>  in the release branch have been fixed"
>  
>  I interpret this as, we move to Code Freeze, when and only 
>  when all blockers have been fixed. 
That's my interpretation too.

>   We then dictate that "During code freeze, the
> only allowed
>  commits are bugfixes to release-blocking bugs"
>  
>  If all blockers must be fixed before we move to Code Freeze, 
>  and we can only commit bug fixes to free up blockers during
>  Feature Freeze, what is the actual point in having a Code
>  Freeze as we will never have any blockers to fix. 
It's possible that the testing done during code freeze reveals new blockers.

GvG

[Royce Mitchell III]

Ge van Geldorp wrote:

>  It's possible that the testing done during code
> freeze reveals new blockers.
>   
>  
I think 1145 should be a blocker for 0.2.9:

http://www.reactos.org/bugzilla/show_bug.cgi?id=1145

[WaxDragon]

Is it a regression from 0.2.8?  If so, can we identify when?

On 12/19/05, Royce Mitchell III <royce3(a)ev1.net> wrote:
>   Ge van Geldorp wrote:
>
> >  It's possible that the testing done during
> > code freeze reveals new blockers.
> >
> >  
>  I think 1145 should be a blocker for 0.2.9:
>
>  http://www.reactos.org/bugzilla/show_bug.cgi?id=1145
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

--
<Russell> argh
<Russell> iterator shenanigans :/