Christian Lohmaier schrieb:
Hi,
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, and it never was a problem to find such regressions,
even though there we have a new build _every_day_, because everyone is
used to add the complete build information (like "Mozilla/5.0
(Windows; U; Windows NT 5.1; de-AT; rv:1.9a1) Gecko/20050914
SeaMonkey/1.1a") to the bug report.
Example: <https://bugzilla.mozilla.org/show_bug.cgi?id=302829>
So I believe that should be a good solution for OOo, too, because
necessity for version selection upgrades in IZ will decrease.
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>
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"
Rainer
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
