releases  

[releases] releases, stopper, and propagation of fixes (was: [releases] Re: [2.4.1] possible showstopper 88709)

Frank Schönheit - Sun Microsystems Germany
Sun, 27 Apr 2008 14:30:46 -0700

Hi James,

> Please do so.  We need separate bug reports for both 2.4 and 3.0 as they 
> are separate products.

Unless I missed something, this is not the case. Bug fixes for 2.4.1
will automatically be copied to the 3.0 branch - this has always been
the case with previous releases. There's an exception to this automatism
(basically if the code in both branches diverges so much autoomatisms
don't work anymore), but even in this case, it's the responsibility of
the developer/QA involved with the issue to ensure the fix is propagated
to the other version, too.

Except ... do you talk about *3.0 Beta* here? In this case, separate
issues might be needed, but only if the issue is really approved as
stopper for the Beta.

(I quite often notice in this list that people talk about "stopper for
3.0". We're not in this phase, yet, not by far. We're in the "stopper
for 3.0 Beta" phase.)

Ciao
Frank

-- 
- Frank Schönheit, Software Engineer         [EMAIL PROTECTED] -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]