On 12/29/2010 10:05 PM, NoOp wrote:
On 12/29/2010 04:15 AM, Neil wrote:
NoOp wrote:
As you all know, it was a pretty difficult transition for some
users to go from SM 1.x to 2.0. If 2.0 is now "maintenance only"
mode, then I wonder if it is worth continuing with SeaMonkey
further.
I think you have misunderstood the point of "maintenance". New
features are always developed on trunk. At some point, we'll put a
temporary freeze on new features, to allow as many remaining bugs in
those features to be discovered and fixed. Locale strings are also
normally frozen at this point. Eventually we decide we're ready and
create a release branch. Development on the next version of SeaMonkey
can then restart on trunk (in practice we don't have the resources
for this until after the release.) Meanwhile the release branch fixes
last-minute bugs at which point we can then release the x.x.0
version. But that's not the end of the branch; bugs are always being
found, and if they have a severe impact (e.g. data loss, crash) then
they are fixed on the branch and typically every month a maintenance
release containing these fixes is delivered.
I don't think that I've misunderstood;
Yes you have misunderstood what maintenance mode means. The following
part of your explanation does not correlate to what maintenance mode
means. nor does it have anything to do with our discussion, even so I'll
address those points.
> 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),
Yes it was opened against Firefox. and as such was not reported as a
SeaMonkey Bug. (So 2.0.1pre, and 1.1.18 are irrelevant here -- even if
it exists in SeaMonkey). But lets presume that it was a SeaMonkey bug
for sake of argument... it was found AFTER the 2.0.0 release (2.0.1pre)
which means it would fall into criteria for a maintenance release.
see:
https://bugzilla.mozilla.org/show_bug.cgi?id=475896. It is NOT a "New
feature".
No it is a trivial "bug fix" that accompanies with it a behavior change
that some others may rely on. We do not take behavior changes/new
features in a security release. The only behavior changes that matter
are those that fix even more serious bugs [not an edge case like this]
or are accompanying a real security threat. And are rated on a case by
case basis. [read on]
There are thousands of 2.0.x SeaMonkey users (at least one would hope
so) out there that still have this issue.
The bug is valid, so every user has this issue. The fact though is that
not every user encounters it, nor of those that do actually care. [or
perhaps RELY on the space behavior for other reason]
> Marking the bug as 'FIXED' on
a yet to be released 2.1 trunk IMO simply doesn't cut it IMO.
Marking the bug as FIXED didn't happen. Its not fixed, there is not even
a reviewed patch that can be requested approval for the maintenance
branch. And as I said above, its a Firefox bug, in Firefox code. So
nothing (aside from writing the fix it for Firefox ourselves, with our
limited resources) we could do for it.
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.
No, any user can copy/paste a url from the url bar. Pasting back into
the urlbar of any current Mozilla-Based application, space or no space,
will work just fine. It's said other applications bug if they don't
convert ' ' to '%20'. If copy/paste was entirely broken, in SeaMonkey
2.0.x that would be not only a regression, but a blocker imo; and I
would be sure to devote resources to fix it, and happy to approve it
landing in the 2.0 maintenance branch.
Here is a paste of:
<https://help.ubuntu.com/community#Getting to know and work with your
system>
directly from 2.0.11. There are of course more examples in the bug
report, but that one works for me.
Which is in and of itself not broken. Copy/Paste of it works. You just
get spaces, which if you copy/paste that whole string back into
SeaMonkey you'll load the page (at the anchor) correctly.
You know as well as I the release dates:
https://wiki.mozilla.org/Releases
https://wiki.mozilla.org/Releases/Old
So my point& questions stand.
I don't follow how release dates (from your links) further your point in
any way.
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
