On Wed, 2006-03-01 at 14:01 +0100, Andre Schnabel wrote: > 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.
Then explain it on the download page for anything in development. Expecting users to know that this is the way things are without telling them is not a good idea. I was not aware and see it as a defect. > > 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. users do not look at issues, do they? > > 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. > Then explain this policy on the webpage. Expecting the general user to know this is not a good idea. > > 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é > ANd that is what should have been continued during the rc cycle. It was not and users paniced. Hence the issue. Is it such a big deal that this policy is not explained before users download devel releases? I do not think so. At least the setup guide will attempt to explain this and the workaround so it is writing in a place that normal users can get what they need to make an intelligent decision on whether to help with testing or not. At the present time, this is not the case. Thanks for your input. -- PLEASE KEEP MESSAGES ON THE LIST. OpenOffice.org Documentation Co-Lead http://documentation.openoffice.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
