RE: [ros-dev] Pending 0.2.7 RC2

[Casper Hornstrup]

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of
> Murphy, Ged
>  (Bolton)
>  Sent: 20. juli 2005 16:47
>  To: 'ReactOS Development List'
>  Subject: RE: [ros-dev] Pending 0.2.7 RC2
>  
>  Robert k. <rob(a)koepferl.de> wrote:
> >   Hi,
> >
> >  since there was just one change to the branch 0.2.7 I did not yet
> >  publish the RC2 version. I decided to wait until monday to publishing
> >  RC2.
> >  
>  
>  It seems RC1 is being forgotten about.
>  
>  I know this has been discussed a few times before, but can we not look into
>  the possibility of branching off for releases in a different way.
>  
>  Although it means changing SVN URL for HEAD, is it not better to follow the
>  path of branching a new HEAD and freezing the current address for the next
>  release. This may help people to remember to concentrate more on bugfixes
>  for the upcoming release and not on implementing new features to HEAD.
>  
>  I'd hate to see another buggy release like 0.2.6, which was possibly a
>  regression on 0.2.5
>  
>  Ged. 
You are confusing HEAD with trunk. Trunk is the main development branch. HEAD
is the youngest (highest) revision in the repository. HEAD is not tied to any
particular branch.

If you run a company where you pay your developers their $70K/year to work for
you, then your approach might be better. For ReactOS however, it is not better since
forcing people to do work is not something we do around here. You might find
that developers just don't contribute anything at all during the freeze if you make
trunk read-only. You also assume that anyone can fix any bug in ReactOS. Were I
to track down and fix a bug in say win32k today, I could probably spend most of
my day doing that. If I were to track down and fix a bug in rbuild today,
I could probably do it much faster.

Casper