Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-06 Thread Jens Hatlak

On 10/6/2009 5:44 PM Bob Fleischer wrote:

Jens Hatlak wrote:

On 10/5/2009 10:35 PM Bob Fleischer wrote:

Does that mean there won't be another beta before release?


Correct, only 1-2 Release Candidates. Code Freeze is tomorrow already
after all.


Sorry, I forget that your definition is different from our definition of 
beta.  We usually beta until the bug rate goes way down to what one 
would expect in a released product.  That doesn't appear to be the case 
here.


What makes you feel like that? The problems described in this thread 
(which were regressions introduced through a recently added feature, 
tabmail) are already fixed for the upcoming Release Candidates. Lots of 
other things have been fixed, too, both between the last beta and now 
and (even more) in comparison to the current stable 1.1.x product line. 
Some major problems will even be fixed as late as today. SM 2.0 won't be 
perfect but developers are trying as good as they can to fix the most 
visible bugs left given the limited resources the project has.


The standard reply to questions when there will be a release has been 
when it's done. That worked as long as there was no light at the end 
of the tunnel but at some point the decision was made to put an end to 
the delay. The reasons for releasing this month go beyond bug counts and 
product quality but that doesn't mean those things are unimportant 
either. It's just time to finally wrap things up.


Greetings,

Jens

--
Jens Hatlak http://jens.hatlak.de/
SeaMonkey Trunk Tracker http://smtt.blogspot.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-06 Thread Robert Kaiser

Jens Hatlak wrote:

The standard reply to questions when there will be a release has been
when it's done. That worked as long as there was no light at the end
of the tunnel but at some point the decision was made to put an end to
the delay. The reasons for releasing this month go beyond bug counts and
product quality but that doesn't mean those things are unimportant
either. It's just time to finally wrap things up.


The point in time comes when the tradeoff between being how much the 
current stable version sucks and how much the current development 
state for the new version sucks requires some hard decisions to actually 
ship it.


From all I see, we already have way fewer problems on 2.0 nightly 
versions than on 1.1.18, which means to me that we really should ship it.


Robert Kaiser
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-06 Thread Jens Hatlak

On 10/6/2009 7:51 PM chicagofan wrote:

[Bugzilla]
It has occurred to me, after reading responses there on several bugs,
that the project members might not want users who can't help 
technically to clutter up that forum.  Is that the case?   I could 
understand that... just trying to determine if I should confine my 
comments/problems to this newsgroup.  :)


Bugzilla is a bug tracking system, i.e. any comment that helps 
understanding the problem or fixing the bug is on topic, anything else 
is not (unless I forgot some scenario). That includes not only technical 
help but also information about how/when/under which conditions a bug 
can be experienced and also since when. The latter is what we call 
finding a regression window, i.e. finding the day the bug first appeared 
by checking nightly builds (which are archived on the FTP server).


In other words, if you have some new information, post it. If not, don't 
(you may add yourself to the CC list or vote for the bug, though). If 
you want to start a discussion, post to a newsgroup (like here) or go to 
IRC and ask politely (and don't expect too much there, from experience 
it takes some time to get a reply, if any, when not asking specific people).


Good:
- filing a bug (after having checked that one doesn't exist already)
- adding new useful info, including narrowing down the problem (e.g. 
happens also on platform X if only confirmed on Y yet)

- adding a patch. ;-)

Bad:
- writing something someone else has written in previous comments
- writing that you really, really want XY or that XY is bad without 
adding otherwise useful information


HTH

Jens

--
Jens Hatlak http://jens.hatlak.de/
SeaMonkey Trunk Tracker http://smtt.blogspot.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-05 Thread Martin Freitag
chicagofan schrieb:
 
 It's been marked as *fixed* now [mark messages] which is great news.   :)
 
 Do I understand correctly that the final release is scheduled for
 October... sometime?

That's correct.
regards

Martin
-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - http://www.gerstbach.at/2004/ascii
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-05 Thread Bob Fleischer

chicagofan wrote:

Jens Hatlak wrote:

On 9/16/2009 10:07 PM chicagofan wrote:

Jens Hatlak wrote:

Known:https://bugzilla.mozilla.org/show_bug.cgi?id=514876


I reported this earlier at bugzilla too, but I'm not tech savvy, and
can't
help find where it went wrong between b1 and b2. I sure hope someone
will
look at this soon, because this is a MAJOR problem for people who use
Usenet a lot, as well as e-mail.


It's a regression from the introduction of the new tabmail feature. Some
initial analysis is available and the bug is already marked
wanted-seamonkey2+ so chances are this will be fixed before release.


It doesn't just fail to mark messages, it opens the *wrong* message when
you try to reply... or forward a message.


Yes, 1-5 (tagging) is affected, too. That will probably be handled in
another
bug that is yet to be filed, though, cf. the Bad MailNews experience in
current nightly? thread in m.d.a.seamonkey.

HTH

Jens



It's been marked as *fixed* now [mark messages] which is great news. :)

Do I understand correctly that the final release is scheduled for
October... sometime?

bj


Does that mean there won't be another beta before release?

Bob
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-05 Thread Jens Hatlak

On 10/5/2009 10:35 PM Bob Fleischer wrote:

chicagofan wrote:

Do I understand correctly that the final release is scheduled for
October... sometime?


Does that mean there won't be another beta before release?


Correct, only 1-2 Release Candidates. Code Freeze is tomorrow already 
after all.


Greetings,

Jens

--
Jens Hatlak http://jens.hatlak.de/
SeaMonkey Trunk Tracker http://smtt.blogspot.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-10-04 Thread chicagofan

Jens Hatlak wrote:

On 9/16/2009 10:07 PM chicagofan wrote:

Jens Hatlak wrote:

Known:https://bugzilla.mozilla.org/show_bug.cgi?id=514876


I reported this earlier at bugzilla too, but I'm not tech savvy, and can't
help find where it went wrong between b1 and b2.  I sure hope someone will
look at this soon, because this is a MAJOR problem for people who use
Usenet a lot, as well as e-mail.


It's a regression from the introduction of the new tabmail feature. Some
initial analysis is available and the bug is already marked
wanted-seamonkey2+ so chances are this will be fixed before release.


It doesn't just fail to mark messages, it opens the *wrong* message when
you try to reply... or forward a message.


Yes, 1-5 (tagging) is affected, too. That will probably be handled in another
bug that is yet to be filed, though, cf. the Bad MailNews experience in
current nightly? thread in m.d.a.seamonkey.

HTH

Jens



It's been marked as *fixed* now [mark messages] which is great news.   :)

Do I understand correctly that the final release is scheduled for October... 
sometime?


bj
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-09-16 Thread chicagofan

Jens Hatlak wrote:

On 9/15/2009 11:33 PM Bob Fleischer wrote:

Using SeaMonkey 2.0b2 on Vista:  reading sequentially through unread emails
in a folder (or news items in a newsgroup) using a separate message window
doesn't mark the subsequent messages as read.


Known: https://bugzilla.mozilla.org/show_bug.cgi?id=514876

HTH

Jens



I reported this earlier at bugzilla too, but I'm not tech savvy, and can't help
find where it went wrong between b1 and b2.  I sure hope someone will look at
this soon, because this is a MAJOR problem for people who use Usenet a lot, as
well as e-mail.

It doesn't just fail to mark messages, it opens the *wrong* message when you try
to reply... or forward a message.  In general, it's the kind of flaw, that makes
you want to go back to a previous version.

I tried to vote for it being a major bug, but it won't record my vote... OR I'm
not doing it right.  :)   Haven't used bugzilla a lot.  :\
bj


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-09-16 Thread chicagofan

chicagofan wrote:

Jens Hatlak wrote:

On 9/15/2009 11:33 PM Bob Fleischer wrote:

Using SeaMonkey 2.0b2 on Vista:  reading sequentially through unread emails
in a folder (or news items in a newsgroup) using a separate message window
doesn't mark the subsequent messages as read.


Known:https://bugzilla.mozilla.org/show_bug.cgi?id=514876

HTH

Jens



I reported this earlier at bugzilla too, but I'm not tech savvy, and can't help
find where it went wrong between b1 and b2.  I sure hope someone will look at
this soon, because this is a MAJOR problem for people who use Usenet a lot, as
well as e-mail.

It doesn't just fail to mark messages, it opens the *wrong* message when you try
to reply... or forward a message.  In general, it's the kind of flaw, that makes
you want to go back to a previous version.

I tried to vote for it being a major bug, but it won't record my vote... OR I'm
not doing it right.  :)   Haven't used bugzilla a lot.  :\
bj




OOPS... I went back to see who filed the original bug report, and saw that my 
vote has been entered.  Now I understand the change doesn't happen instantly. 
Sorry 'bout that.

bj
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-09-16 Thread Jens Hatlak

On 9/16/2009 10:07 PM chicagofan wrote:

Jens Hatlak wrote:

Known: https://bugzilla.mozilla.org/show_bug.cgi?id=514876


I reported this earlier at bugzilla too, but I'm not tech savvy, and 
can't help find where it went wrong between b1 and b2.  I sure hope 
someone will look at this soon, because this is a MAJOR problem for 
people who use Usenet a lot, as well as e-mail.


It's a regression from the introduction of the new tabmail feature. Some 
initial analysis is available and the bug is already marked 
wanted-seamonkey2+ so chances are this will be fixed before release.


It doesn't just fail to mark messages, it opens the *wrong* message 
when you try to reply... or forward a message.


Yes, 1-5 (tagging) is affected, too. That will probably be handled in 
another bug that is yet to be filed, though, cf. the Bad MailNews 
experience in current nightly? thread in m.d.a.seamonkey.


HTH

Jens

--
Jens Hatlak http://jens.hatlak.de/
SeaMonkey Trunk Tracker http://smtt.blogspot.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


2.0b2: reading next message in separate window doesn't mark it as read

2009-09-15 Thread Bob Fleischer
Using SeaMonkey 2.0b2 on Vista:  reading sequentially through unread 
emails in a folder (or news items in a newsgroup) using a separate 
message window doesn't mark the subsequent messages as read.


Bob
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-09-15 Thread Gerald Ross

Bob Fleischer wrote:

Using SeaMonkey 2.0b2 on Vista:  reading sequentially through unread
emails in a folder (or news items in a newsgroup) using a separate
message window doesn't mark the subsequent messages as read.

Bob

Same on XP.

--
Gerald Ross
Cochran, GA

How long a minute is depends on which
side of the bathroom door you're on.





___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0b2: reading next message in separate window doesn't mark it as read

2009-09-15 Thread Bob Fleischer
Other things fail on the subsequent messages (but not the first).  For 
example, if images are blocked, one cannot show them.


Bob

Gerald Ross wrote:

Bob Fleischer wrote:

Using SeaMonkey 2.0b2 on Vista: reading sequentially through unread
emails in a folder (or news items in a newsgroup) using a separate
message window doesn't mark the subsequent messages as read.

Bob

Same on XP.



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey