Hi,

> --- Ursprüngliche Nachricht ---
> Von: "G. Roderick Singleton" <[EMAIL PROTECTED]>
> Datum: Wed, 01 Mar 2006 07:37:21 -0500
> 
> Early in the 2.0.2 development cycle, I encountered many users having
> problems testing the snapshots. These replaced existing 2.x varients. I
> opened http://www.openoffice.org/issues/show_bug.cgi?id=62360  to get
> this fixed and called it a defect. As of today, Christian Lohmaier the
> co-lead of the web provided an explanation that this is a policy that is
> built-in. One of the other commenters provided a manual workaround and
> this is what is going into the guide. I will not update the website but
> will attach the revision to 37513 for review.


sorry .. biut reading your comments at the issue, there ar simply wrong
expectations about what an RC really is.

As of stated several times at the issue, an RC is supposed to behave exactly
as the final version would do. When building an RC, we *think* it is stable
(that's why it behaves like the final version). But we need to do some tests
to be shure. 
If no errors are found, the RC would become the final version .. that means,
the final version is *exactly* the same as the aproved RC.

If an RC ould not behave as the suppoesd final version, we would need to do
a repackaging after testing the RC. But as the repackaged version would not
be the same as the testet RC, we cannot be shure, if errors have been
introduced by the repackging process .. so we would need to do some testing
again. That means .. we would need to have to mark this repackaged version
as "not ready for production use", although it would install as 2.0.2 final.
*sigh* and we would run in circles.


btw .. for "testing snapshots" Sun release engineering provides snapshots
that install as OOo-dev .. and could be installed as separate version
without any problems. 

andré

-- 
"Feel free" mit GMX FreeMail!
Monat für Monat 10 FreeSMS inklusive! http://www.gmx.net

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

Reply via email to