On 12/29/2010 08:22 PM, Justin Wood (Callek) wrote: > 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.
It was reported after this thread: "SM 2.0 URL escape character auto conversion" 10/30/2009 I then went ahead and filed the bug. Use your *SeaMonkey* newsreader to review. > >> 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] If it's trivial, then why not target it for something other than Target Milestone: seamonkey2.1b2 ?? 2.0.12 *might* occur... But Philipp's "fix" was dated: 2010-11-21 07:38:47 PST SeaMonkey 2.0.11 was released December 9: https://wiki.mozilla.org/Releases <quote> SeaMonkey 2.0.11 December 9 (tied to Firefox 3.5.16) </quote> > >> 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] BS > > > 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. OK, it was marked as RESOLVED as in: This bug has been marked as a duplicate of bug 613199 *** https://bugzilla.mozilla.org/show_bug.cgi?id=613199 Status: RESOLVED FIXED Product: SeaMonkey Hence, it was technically marked as FIXED. <https://bugzilla.mozilla.org/show_activity.cgi?id=531210> > >> 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. Really? Why don't you switch to SM 2.0.11 instead of Thunderbird 3.1.7 and try it? > >> 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. Right. Paste the link here from 2.0.11. Then try to use that link from your resulting post. > >> 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. > BTW: if you are going to continue to post/comment here (mozilla.support.seamonkey) it might be a good idea if you actually *use* the subject product: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 BTW: let us know how Lightning/1.0b2 or Lightning/1.1X works with SeaMonkey (2.0.11 or 2.1bX goes for you. Inquiring minds want to know. Posting on this newsgroup using Thunderbird is akin to posting on a linux only newsgroup using Microsoft Outlook. I mentioned this to you on 11/25/2010 & your response was: Subject: Re: Testing SeaMonkey 2.0.11 candidates - help wanted! <quote> Heh I tend to use Thunderbird as my stable mailer since I like trunk SeaMonkey, and by using Thunderbird I can load trunk SeaMonkey easily when I click links. But you are right that "I should eat my own dogfood" more often and use SeaMonkey for my mail. [To feel confident on trunk for more than News though I think we need/want more test coverage in mail though] </quote> Maybe you should try using SeaMonkey 2.0.11 (stable) like the rest of the users on this newsgroup & come back and post afterwards... _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
