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; 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.

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.

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.



_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to