On 10-12-29 10:05 PM, NoOp wrote:
I don't think that I've misunderstood; the bug was opened in November
2009 with 2.0.1pre& 1.1.18. It was/is well documented, and is an
outstanding issue going back to January 2009 (Firefox), see:
https://bugzilla.mozilla.org/show_bug.cgi?id=475896. It is NOT a "New
feature".
There are thousands of 2.0.x SeaMonkey users (at least one would hope
so) out there that still have this issue. Marking the bug as 'FIXED' on
a yet to be released 2.1 trunk IMO simply doesn't cut it IMO.
If we expect users to install 2.1pre versions simply so that they can
copy& paste a url from the url bar, then I suspect that no fixes in any
"current" version of SeaMonkey (http://www.seamonkey-project.org/) will
ever be satisfied.
Hi NoOp,
Unfortunately, your understanding of how development and bugzilla works
is incorrect. Put it this way, when a new major version of SeaMonkey is
released, are developers supposed to start going through hundreds of
bugs they've fixed over the past year and start making them as fixed?
What if the bug is in more than one release?
Maintenance mode (or stable branch) means that changes can only be made
to the code if doesn't:
* break extensions
* require localizers to translate more strings
(and probably more, but the general idea is not to make changes that are
going to break other things)
If a bug appears in both the trunk and branch (which is usually the
case), the fix is first applied to the trunk. You can then request that
it be applied to the branch. Someone will then review patch, to see if
it is safe enough to be applied to the stable branch, and if it is apply
that patch and add the appropriate keyword to the bug. In some cases,
the assignee may need to create a separate patch just for the stable
branch.
No-one is telling users that you have to download a pre-release to see
the fix (Although it would be helpful to test it). It's just a matter of
which end-user release users will experience the fix: the next 2.0.x
release or 2.1.
Phillip marked the bug as a duplicate of bug 613199, so bug 613199 is
the one you need to nominate for SeaMonkey 2.0.
--
Chris Ilias <http://ilias.ca>
Newsgroup moderator
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
