SeaMonkey 1.1.7 candidate builds - please help testing! - Mozilla

This is a discussion on SeaMonkey 1.1.7 candidate builds - please help testing! - Mozilla ; Hi all, You might have noticed recent posts about a Firtefox 2.0.0.10 being in the works ( ) and a test day for that stability and security release ( ) and wondered if we'll do a SeaMonkey 1.1.7 in sync ...

+ Reply to Thread
Results 1 to 13 of 13

Thread: SeaMonkey 1.1.7 candidate builds - please help testing!

  1. SeaMonkey 1.1.7 candidate builds - please help testing!

    Hi all,

    You might have noticed recent posts about a Firtefox 2.0.0.10 being in
    the works () and a test day for
    that stability and security release
    () and wondered if we'll do a
    SeaMonkey 1.1.7 in sync with it.

    And yes, you're right, we're planning to do this SeaMonkey 1.1.7 in sync
    with the Firefox update, planned for next week (see
    for their
    schedule).

    A number of bugs will be fixed in this release, most notable we also
    hope to have fixed the problems with launching SeaMonkey from read-only
    installations, just like a Mac Disk Image.

    Our candidate builds are now available at
    http://ftp.mozilla.org/pub/mozilla.o...didates-1.1.7/
    and we need your help to get good testing of them on all major platforms
    before release.

    Please help us with this testing so we can have a good SeaMonkey 1.1.7
    release!

    If you can do some smoketesting, please go to
    and do a SeaMonkey 1.1 test run
    (). For further
    questions, stop by on IRC in #seamonkey, and ask our QA head ajschult or
    other people around there who should know what can/should/needs to be
    tested.


    Thanks for your help,

    Robert Kaiser
    SeaMonkey Council member


  2. Re: SeaMonkey 1.1.7 candidate builds - please help testing!

    Hi Robert Kaiser,

    Thanks for the continued work on my favorite browser/mailer!

    I have found a problem while testing SeaMonkey 1.1.7 (browser)
    After installing the extension "noscript",
    the navigation toolbar is no longer updated when a new page is loaded.
    I do not have this problem with SeaMonkey 1.1.6
    (If this is a "noscript" problem rather than a SeaMonkey problem,
    my apologies.....)

    Marc Allaart

    ------------------------------------------------------------------

    Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.10) Gecko/20071119 SeaMonkey/1.1.7
    Linux, Suse 10, KDE 3.5
    Used seamonkey-installer, complete install in not-default directory
    One extension: noscript-1.1.8-fx+mz+sm+fl.xpi

    ------------------------------------------------------------------

    Robert Kaiser wrote:
    > Hi all,
    >
    > You might have noticed recent posts about a Firtefox 2.0.0.10 being in
    > the works () and a test day for
    > that stability and security release
    > () and wondered if we'll do a
    > SeaMonkey 1.1.7 in sync with it.
    >
    > And yes, you're right, we're planning to do this SeaMonkey 1.1.7 in sync
    > with the Firefox update, planned for next week (see
    > for their
    > schedule).
    >
    > A number of bugs will be fixed in this release, most notable we also
    > hope to have fixed the problems with launching SeaMonkey from read-only
    > installations, just like a Mac Disk Image.
    >
    > Our candidate builds are now available at
    > http://ftp.mozilla.org/pub/mozilla.o...didates-1.1.7/
    > and we need your help to get good testing of them on all major platforms
    > before release.
    >
    > Please help us with this testing so we can have a good SeaMonkey 1.1.7
    > release!
    >
    > If you can do some smoketesting, please go to
    > and do a SeaMonkey 1.1 test run
    > (). For further
    > questions, stop by on IRC in #seamonkey, and ask our QA head ajschult or
    > other people around there who should know what can/should/needs to be
    > tested.
    >
    >
    > Thanks for your help,
    >
    > Robert Kaiser
    > SeaMonkey Council member
    >


  3. Re: SeaMonkey 1.1.7 candidate builds - please help testing!

    Marc Allaart wrote:
    > Hi Robert Kaiser,
    >
    > Thanks for the continued work on my favorite browser/mailer!
    >
    > I have found a problem while testing SeaMonkey 1.1.7 (browser)
    > After installing the extension "noscript",
    > the navigation toolbar is no longer updated when a new page is loaded.
    > I do not have this problem with SeaMonkey 1.1.6
    > (If this is a "noscript" problem rather than a SeaMonkey problem,
    > my apologies.....)


    IMO I would believe it is a noscript problem. Perhaps you
    need to update it.

    --
    *IMPORTANT*: Sorry folks, but messages emailed to me will be
    disregarded!!!!

    Peter Potamus & His Magic Flying Balloon:
    http://www.toonopedia.com/potamus.htm

  4. SeaMonkey 1.1.7 will be respinned!

    Hi,

    > Please help us with this testing so we can have a good SeaMonkey 1.1.7
    > release!


    Unfortunately, all Firefox and SeaMonkey testing did not reveal a
    regression in canvas code (known one-line-fix forgotten to be included
    in the code), we needed Firefox 2.0.0.10 to be in the wild for a few
    hours to spot this. Nothing as bad as the last time something like that
    happened, but still annoying enough.

    As we caught it just the moment I wanted to move SeaMonkey files to
    public, we'll respin builds and hope to get really fast QA to still
    release this week, as it's already public that we have those three
    vulnerabilities in 1.1.6:
    http://www.mozilla.org/projects/secu...seamonkey1.1.7

    If you personally want to be on the safe side and don't need canvas
    functionality, you probably should use the 1.1.7 candidates, but be
    aware that they'll be replaced with new builds very soon. I'll announce
    that here again when it's done.

    Robert Kaiser


  5. New SeaMonkey 1.1.7 candidates - please help testing!

    >> Please help us with this testing so we can have a good SeaMonkey 1.1.7
    >> release!

    >
    > Unfortunately, all Firefox and SeaMonkey testing did not reveal a
    > regression in canvas code (known one-line-fix forgotten to be included
    > in the code), we needed Firefox 2.0.0.10 to be in the wild for a few
    > hours to spot this. Nothing as bad as the last time something like that
    > happened, but still annoying enough.


    We have new builds up at
    http://ftp.mozilla.org/pub/mozilla.o...didates-1.1.7/

    PLEASE help us testing them, so we can ship the release very soon now!

    We already know we have those 3 vulnerabilities out in the wild with the
    current stable version, which are fixed in this new SeaMonkey 1.1.7:
    http://www.mozilla.org/projects/secu...seamonkey1.1.7

    In comparison with the last candidates, we additionally took a fix for
    the regression that forced the Firefox team to prepare a
    2.0.0.11 release, and another small fix that makes our builds launch
    correctly again from Mac disk images.

    Release notes are prepared on
    http://www.seamonkey-project.org/rel...eamonkey1.1.7/ already and
    contain a fully list of fixed bugs in this release.

    If you can do some smoketesting, please go to
    and do a SeaMonkey 1.1 test run
    (). For further
    questions, stop by on IRC in #seamonkey, and ask our QA head ajschult or
    other people around there who should know what can/should/needs to be
    tested.

    Robert Kaiser
    SeaMonkey Council member


  6. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    On 11/28/2007 03:27 PM, Robert Kaiser wrote:
    >>> Please help us with this testing so we can have a good SeaMonkey 1.1.7
    >>> release!

    >>
    >> Unfortunately, all Firefox and SeaMonkey testing did not reveal a
    >> regression in canvas code (known one-line-fix forgotten to be included
    >> in the code), we needed Firefox 2.0.0.10 to be in the wild for a few
    >> hours to spot this. Nothing as bad as the last time something like that
    >> happened, but still annoying enough.

    >
    > We have new builds up at
    > http://ftp.mozilla.org/pub/mozilla.o...didates-1.1.7/
    >
    > PLEASE help us testing them, so we can ship the release very soon now!
    >
    > We already know we have those 3 vulnerabilities out in the wild with the
    > current stable version, which are fixed in this new SeaMonkey 1.1.7:
    > http://www.mozilla.org/projects/secu...seamonkey1.1.7
    >
    > In comparison with the last candidates, we additionally took a fix for
    > the regression that forced the Firefox team to prepare a
    > 2.0.0.11 release, and another small fix that makes our builds launch
    > correctly again from Mac disk images.
    >
    > Release notes are prepared on
    > http://www.seamonkey-project.org/rel...eamonkey1.1.7/ already and
    > contain a fully list of fixed bugs in this release.
    >
    > If you can do some smoketesting, please go to
    > and do a SeaMonkey 1.1 test run
    > (). For further
    > questions, stop by on IRC in #seamonkey, and ask our QA head ajschult or
    > other people around there who should know what can/should/needs to be
    > tested.
    >
    > Robert Kaiser
    > SeaMonkey Council member
    >


    Robert,

    Why is it you always cross post these in the mozilla.support.seamonkey
    group with followups set to mozilla.dev.apps.seamonkey?

    I am sure that mozilla.support.seamonkey users may be willing to give
    the build(s) a try & possibly even perform smoketesting (I've done so in
    the past for most versions), but many mozilla.support.seamonkey users
    may not even be subscribed to mozilla.dev.apps.seamonkey.

    Please if you are to cross post the announcements, also notify
    mozilla.support.seamonkey users that they should subscribe to
    mozilla.dev.apps.seamonkey in order to read and/or continue any posts to
    the thread.
    That said, are you sure that you actually want
    mozilla.support.seamonkey users over on the mozilla.dev.apps.seamonkey
    group simply for reports regarding a new build test request? Perhaps a
    separate mozilla.support.seamonkey might be a better idea?

    Followup to this post set to: mozilla.support.seamonkey


  7. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    NoOp wrote:
    > Robert,
    >
    > Why is it you always cross post these in the mozilla.support.seamonkey
    > group with followups set to mozilla.dev.apps.seamonkey?


    Primarily because feedback for developers on unreleased builds is more
    of a dev thing than a support thing.

    > I am sure that mozilla.support.seamonkey users may be willing to give
    > the build(s) a try & possibly even perform smoketesting (I've done so in
    > the past for most versions), but many mozilla.support.seamonkey users
    > may not even be subscribed to mozilla.dev.apps.seamonkey.


    That's not so bad.

    The worst case scenario is that they reply and post to m.d.a.seamonkey
    and a developer asks for more feedback and they don't see it. That's
    still better than posting to m.s.seamonkey and not having a developer
    see it. If the developer really wants the info, he'll notice the lack
    of response and track down the poster in m.s.seamonkey or just send a
    private email.

    m.s.seamonkey users would also miss out on the resulting discussion, but
    since it will be primarily developer-oriented, they probably won't miss
    it much.

    In general cross-posting is not uncommon and when it does happen, a
    followup-to group should be set. If someone reading the post is not in
    that group, they'll need to either decide the discussion isn't too
    important or subscribe to that group.

    --
    Andrew Schultz
    ajschult@verizon.net
    http://www.sens.buffalo.edu/~ajs42/


  8. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    NoOp wrote:
    > Why is it you always cross post these in the mozilla.support.seamonkey
    > group with followups set to mozilla.dev.apps.seamonkey?


    Because netiquette says that it's bad to post without a followup to a
    single group.

    mozilla.dev.apps.seamonkey is for development and testing, while
    mozilla.support.seamonkey is for end-user support. End users should be
    notified that there are testing versions, but testers should always use
    the dev group for test feedback, as everything but actually released
    builds are development builds of some kind.

    You might noticed that release announcements go the other way, with
    followup set to the support group.

    Robert Kaiser


  9. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    Andrew Schultz wrote:
    > NoOp wrote:
    >> Robert,
    >>
    >> Why is it you always cross post these in the mozilla.support.seamonkey
    >> group with followups set to mozilla.dev.apps.seamonkey?

    >
    > Primarily because feedback for developers on unreleased builds is more
    > of a dev thing than a support thing.
    >
    >> I am sure that mozilla.support.seamonkey users may be willing to give
    >> the build(s) a try & possibly even perform smoketesting (I've done so in
    >> the past for most versions), but many mozilla.support.seamonkey users
    >> may not even be subscribed to mozilla.dev.apps.seamonkey.

    >
    > That's not so bad.


    Other than the people doing the work not getting to share the
    information, and the developers missing out on user B better
    characterizing a problem reported by user A, such that it can be fixed.
    >
    > The worst case scenario is that they reply and post to m.d.a.seamonkey
    > and a developer asks for more feedback and they don't see it. That's
    > still better than posting to m.s.seamonkey and not having a developer
    > see it. If the developer really wants the info, he'll notice the lack
    > of response and track down the poster in m.s.seamonkey or just send a
    > private email.


    If the request for testing is on-topic here, so are the replies.
    >
    > m.s.seamonkey users would also miss out on the resulting discussion, but
    > since it will be primarily developer-oriented, they probably won't miss
    > it much.
    >
    > In general cross-posting is not uncommon and when it does happen, a
    > followup-to group should be set. If someone reading the post is not in
    > that group, they'll need to either decide the discussion isn't too
    > important or subscribe to that group.
    >

    The followups should be limited to the groups where discussion is on
    topic. I don't know where you got the idea that you must or even should
    trim to one group, and certainly not the one group most convenient to
    you and not to the people you ask to help you test.

    --
    Bill Davidsen
    "We have more to fear from the bungling of the incompetent than from
    the machinations of the wicked." - from Slashdot

  10. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    Bill Davidsen wrote:
    > The followups should be limited to the groups where discussion is on
    > topic. I don't know where you got the idea that you must or even should
    > trim to one group, and certainly not the one group most convenient to
    > you and not to the people you ask to help you test.


    See "No crossposting"
    http://www.mozilla.org/community/etiquette.html

    --
    Andrew Schultz
    ajschult@verizon.net
    http://www.sens.buffalo.edu/~ajs42/


  11. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    On 11/30/2007 09:40 PM, Andrew Schultz wrote:
    > Bill Davidsen wrote:
    >> The followups should be limited to the groups where discussion is on
    >> topic. I don't know where you got the idea that you must or even should
    >> trim to one group, and certainly not the one group most convenient to
    >> you and not to the people you ask to help you test.

    >
    > See "No crossposting"
    > http://www.mozilla.org/community/etiquette.html
    >


    You'll have to look at dev to see my response to Robert from this thread
    as his response to me had Followup-to: mozilla.dev.apps.seamonkey set.

    If the "No crossposting" rule should apply, then my point regarding the
    crossposting of these announcements should equally apply. Post one to
    mozilla.dev.apps.seamonkey and one to mozilla.support.seamonkey. The one
    in mozilla.support.seamonkey should include information for subcribing
    to mozilla.dev.apps.seamonkey to view, continue to comment etc., and the
    post/thread in this group should remain as mozilla.dev.apps.seamonkey.

    Reasoning for this is: 1) many users of mozilla.support.seamonkey may
    not subscribe, or want to subscribe to mozilla.dev.apps.seamonkey, but
    should be aware of the group and the ability to contribute there, 2)
    many users of this mozilla.support.seamonkey may actually wish to see
    the response/experience of other users that try a new candidate.

    Regarding point #2: if after such a 'please help test' post a user tries
    candidate xyz and it hoses their system, they may not want to give it a
    try. On the otherhand, if user responses are "works great, no problems,
    etc.," more users just might be willing to give the RC a try.

    Either way, I understand the initial reasoning for the initial dual
    post; meaning that Robert/SeaMonkey would like to get the message out &
    that a new RC needs testing & SM would like help testing. I'd just like
    to see a post of this type to include *user* oriented text in the post
    and a continued thread here so that "users" have some idea on how
    testing by other "users" is going.






  12. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    On 12/01/2007 07:01 PM, NoOp wrote:

    > If the "No crossposting" rule should apply, then my point regarding the
    > crossposting of these announcements should equally apply. Post one to
    > mozilla.dev.apps.seamonkey and one to mozilla.support.seamonkey. The one
    > in mozilla.support.seamonkey should include information for subcribing
    > to mozilla.dev.apps.seamonkey to view, continue to comment etc., and the
    > post/thread in this group should remain as mozilla.dev.apps.seamonkey.


    Correction:

    post/thread in this group should remain as mozilla.support.seamonkey

  13. Re: New SeaMonkey 1.1.7 candidates - please help testing!

    NoOp wrote:
    > If the "No crossposting" rule should apply, then my point regarding the
    > crossposting of these announcements should equally apply. Post one to
    > mozilla.dev.apps.seamonkey and one to mozilla.support.seamonkey. The one
    > in mozilla.support.seamonkey should include information for subcribing
    > to mozilla.dev.apps.seamonkey to view, continue to comment etc., and the
    > post/thread in this group should remain as mozilla.dev.apps.seamonkey.


    I would have to agree with this, and I'm a prime example of
    what happened. Robert made 2 annoucements with one followup
    to the other group, and the other with a followup to this
    group. I forgot he did that, and posted my response from
    this group, but it went to the other group.

    --
    *IMPORTANT*: Sorry folks, but messages emailed to me will be
    disregarded!!!!

    Peter Potamus & His Magic Flying Balloon:
    http://www.toonopedia.com/potamus.htm

+ Reply to Thread