Hi *,
On Sat, Jan 21, 2006 at 10:01:36AM +0100, Rainer Bielefeld wrote: > Christian Lohmaier schrieb: > > all this can be discussed, when we will have 2.0.1 for or product > relevant issues :-/ ? > >And yes, every milestone must be listed in the developer-components, > >otherwise filing (and finding) regressions would be a major pain. > > I don't think so. In Bugzilla for the Mozilla projects, there is a > version selection "Trunk" for all "unstable" versions in the main > development line, Mozilla has a different development process. Mozilla doesn't use childworkspaces and Mozilla doesn't use the "milestones" as OOo uses them. So what Mozilla does is not relevant. > [...] > >If it is found in a milestone, specify the milestone. Both 680m149 and > >680m150 are available. > > Available where? I can_t see any selection for those milestones. > <http://free.pages.at/rainerbielefeld/bilder/milestoneselector.png> If you have a look at the issue activity, you'll see that it was reassigned to a different component. Word-processor (as this was the component the issue was reported with) has these milestones. > Or course I can specify that in the issue report, but it seems to be > no good idea to list it as "version 2.0.1" So you request a Mozilla-Like scheme "One version fits all" and say it is no problem because everyone specifies the release in the report. And when it comes to OOo because some components don't have every milestone available, this suddenly is a problem? ciao Christian -- NP: nichts --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
