299630 - Version number of the first SeaMonkey release should be higher than 1.7.x

Status: VERIFIED WONTFIX

(SeaMonkey :: General, defect)

Description

[Prognathous]

We already have a browser (code)named "Seamonkey 1.0". It was released three
years ago. To avoid confusion, please use a version number higher than the last
Seamonkey/Suite release. It doesn't really matter if it's 1.8, 2.0, or something
else, as long it can't be confused with an older release.

Actually, it's not just a matter of clarity, using a higher number would reflect
the continued development of a mature product that is currently at version
1.7.x. Using v1.0 would erase this legacy.

Prog.

Comment 1

[Robert Kaiser]

There was nothing labelled "SeaMonkey 1.0" any time. And this is a new project,
and it starts counting from the beginning.

This topic has been discussed by the SeaMonkey Council months ago, and we
decided to go for SeaMonkey 1.0 as the first release.

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

also, iirc, mozfoundation didn't want us to use 1.8 as the version.

Comment 3

[Prognathous]

(In reply to Robert Kaiser, comment #1)
> There was nothing labelled "SeaMonkey 1.0" any time.

Not labeled, but commonly referred to as such.

> And this is a new project, and it starts counting from the beginning.

It's not really a new project. It's more like the next release in a long string
of Seamonkey/Suite milestones, except that this time, the main feature will be a
change in branding - the codename becomes the official name. It's still the same
application (at least I hope so).

> This topic has been discussed by the SeaMonkey Council months ago, and we
> decided to go for SeaMonkey 1.0 as the first release.

Now would be a great time to re-think this decision, after the first release is
out may be too late.

(In reply to Christian Biesinger, comment #2)
> also, iirc, mozfoundation didn't want us to use 1.8 as the version.

How about v2.0 then?

Prog.

Comment 4

[Robert Kaiser]

(In reply to comment #3)
> > And this is a new project, and it starts counting from the beginning.
> 
> It's not really a new project. It's more like the next release in a long string
> of Seamonkey/Suite milestones, except that this time, the main feature will be a
> change in branding - the codename becomes the official name. It's still the same
> application (at least I hope so).

It's basically the same application, that's right.

It's a very new project though, not managed by Mozilla Foundation any more.

Additionally, "Seamonkey" was not even a semi-official codename for the suite
actually, though it has been increasingly used for it. It's been the internal
codename for the later-labeled-as-such Netscape 6 release originally.

> Now would be a great time to re-think this decision, after the first release is
> out may be too late.

The decision has been made and is final. Sorry. End of discussion.

Comment 5

[Felix Miata]

There should be a link in this bug to wherever that discussion took place. I'd
like to know how they decided something which is distinguishable from what
should have been Mozilla 1.8 only by its name and a new directory on the mirrors
is a "new" project. The "first" Seamonkey release will be better than 1.7.x is,
and will be the replacement for 1.7.x for users of 1.7.x, regardless what the
official foundation position would have us believe.

The foundation has no current suite, as 1.7.x branched over 14 months ago,
making IE the only older "current" browser. Yet the purpose of the foundation at
least initially was to continue the tradition begun with Netscape, a complete
suite of interrelated and tightly integrated internet applications. For the
foreseeable future at least, only Seamonkey will be continuing that tradition,
and in that context, starting over at version 1.0 makes no sense.

2.0 would work for me, even if it doesn't get released as such until FF 2.0.
Even 5.0, which never happened in official Mozilla or Netscape releases, makes
more sense to me than 1.0.

Comment 6

[Dan Tobias]

For that matter, there was a "Mozilla 1.0" a long time ago, since that's what
Netscape 1.0 was code-named.

Comment 7

[Christian :Biesinger (don't email me, ping me on IRC)]

>The foundation has no current suite, as 1.7.x branched over 14 months ago,

not like it has a current (non-alpha) firefox.

Comment 8

[OstGote!]

*** This bug has been confirmed by popular vote. ***