[ros-kernel] Release process
Casper Hornstrup
chorns at users.sourceforge.net
Thu Oct 16 10:10:52 CEST 2003
> -----Oprindelig meddelelse-----
> Fra: ros-kernel-bounces at reactos.com
> [mailto:ros-kernel-bounces at reactos.com] På vegne af Vizzini
> Sendt: 16. oktober 2003 00:10
> Til: ReactOS General List
> Emne: Re: [ros-kernel] Release process
>
> I have merged any remaining changes from the 0.1.4 release
> branch into HEAD.
>
> I propose that any developer who commits a fix on any branch
> be responsible for merging that change into HEAD. Anyone disagree?
>
> As Casper pointed out, merging is a bit tricky, as you cannot
> re-merge after an initial merge or CVS will get confused. I
> think our patches are small enough, though, that this won't
> be much of a problem.
>
> -Vizzini
I think we should commit to both HEAD and release branch and perform
no merging after the release. This way, patches are not forgotten at
the release branch and a missing patch on HEAD is not stopping anyone
from developing on the HEAD branch.
Casper
Re
More information about the Ros-kernel
mailing list