Hi,
> I noticed that Yuri checked in some code on the branch already. Can we
> please follow some guideline how we handle such release branches?
> Changes on a release branch should be discussed before and should be in
> relation to a proposed and approved fix (if you want showstopper) that
> will go in the next release.
sorry, but maybe I'm not understanding something; why do AOO400 (which
is a branch) fixes going into next release (AOO401) require another
branch?
I committed to AOO400 because I supposed that newer (minor) releases
were going into this branch, not into a different one.
And I don't undestand at all why branching again for 401, while we can
just use tagging to monitor minor bugfixes releases from AOO400
branch.
I understand that a 4.1 release will incorporate new code while we can
still produce 4.0.2 on the older branch, so branching for 4.1 makes
more sense.
with this branching tecnique, a bugfix must be sideported to every
active branch, e.g. trunk, AOO401, AOO410 (maybe more in the future).
If I missed some guideline doc on the wiki please excuse me.
thanks,
--
Bye,
Yuri Dario
/*
* OS/2 open source software
* http://web.os2power.com/yuri
* http://www.netlabs.org
*/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
