Phoenix 0.5 (Naples) as of 12/7/2002 08:00 USA-EST

[fangorn_ent]

Page http://mozilla.org/projects/phoenix/pho ... notes.html indicates a build of "Naples"

*BUT*

the Windoze and Linux links are inconsistent:

Windows: http://ftp.mozilla.org/pub/phoenix/rele ... -win32.zip
Linux: http://ftp.mozilla.org/pub/phoenix/rele ... gnu.tar.gz

Also, clicking on the Windows link gets

"The requested URL /pub/phoenix/releases/0.5/phoenix-0.5-win32.zip was not found on this server."

Oops?

[seb]

I guess you haven't seen the background of the page.
It reads DRAFT about a hundred times in big.

-> Phoenix 0.5 isn't available yet, the links won't work until it's available.

[laszlo]

Look at the background of the page... It says "DRAFT" in BIG letters, which at least in my interpretation means that it's not yet official. There's also no 0.5 directory yet on ftp://mozilla.org/pub/phoenix/releases .

[fangorn_ent]

I did see the word "draft" and was confused by this. Normally, we don't publish test objects into production and let users looking for stable releases encounter them.

Suggestion: Create (at least) 2 areas:

1) Production i.e. http://mozilla.org/projects/phoenix/pho ... notes.html

2) Integrated Test or Staging (somewhere else) which is private to developers and testers

Anyways, that is what folks normally do in other projects, in my experience.

-Richard

[johnh123]

So......when will it not be draft?

[laszlo]

So......when will it not be draft?

As soon as the background image has vanished, I assume.

[djst]

I did see the word "draft" and was confused by this. Normally, we don't publish test objects into production and let users looking for stable releases encounter them.

Suggestion: Create (at least) 2 areas:

1) Production i.e. http://mozilla.org/projects/phoenix/pho ... notes.html

2) Integrated Test or Staging (somewhere else) which is private to developers and testers

Anyways, that is what folks normally do in other projects, in my experience.

-Richard

This is version 0.5, so any user of Phoenix so far is a tester.

[Franck]

about phoenix : Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
very closed

the feature "multiple home pages" works perfectly ...
let's play

[fangorn_ent]

This is version 0.5, so any user of Phoenix so far is a tester.

Agreed.

BUT www.mozilla.org ==> to the draft 0.5 web page which it calls "Phoenix 0.4" instead of to http://mozilla.org/projects/phoenix/0.4 ... notes.html.

When the Phoenix 0.5 web page is ready (not a draft), THEN it can become what is pointed to by Mozilla and Mozilla's page could be updated to say "0.5".

Perhaps I should have said that to begin with in my first post.

[djst]

This is version 0.5, so any user of Phoenix so far is a tester.

Agreed.

BUT www.mozilla.org ==> to the draft 0.5 web page which it calls "Phoenix 0.4" instead of to http://mozilla.org/projects/phoenix/0.4 ... notes.html.

When the Phoenix 0.5 web page is ready (not a draft), THEN it can become what is pointed to by Mozilla and Mozilla's page could be updated to say "0.5".

Perhaps I should have said that to begin with in my first post.

I can agree it would be better to have "phoenix-release-notes.html" point to the latest official release and not a draft to a forthcoming release, but I'm sure the developers have a reason for doing it this way.

[scratch]

I did see the word "draft" and was confused by this. Normally, we don't publish test objects into production and let users looking for stable releases encounter them.

Suggestion: Create (at least) 2 areas:

1) Production i.e. http://mozilla.org/projects/phoenix/pho ... notes.html

2) Integrated Test or Staging (somewhere else) which is private to developers and testers

Anyways, that is what folks normally do in other projects, in my experience.

-Richard

They have "draft" builds up constantly, so why not draft release notes?

[Blake]

It's really just for convenience's sake that we update the live page, since we can then use mozilla.org's web-based edit system. The alternative is to use cvs, pull the whole mozilla.org doctree, etc. We do archive release notes; the 0.4 ones are linked to at the bottom. While I could just update the 0.4 release notes link to that page temporarily, I really don't see the point (we have stats on how many people are still visiting the 0.4 relnotes pages, it's very few, and we plan on releasing today.)

[djst]

It's really just for convenience's sake that we update the live page, since we can then use mozilla.org's web-based edit system.

I figured that was the reason.

[asa]

I did see the word "draft" and was confused by this. Normally, we don't publish test objects into production and let users looking for stable releases encounter them.

This is a pre-release (0.5) open source project. Anyone using any build of Phoenix, nightly or milestone, are _not_ production or stable. If the idea of _testing_ pre-1.0 software and the release documentation that goes along with it doesn't appeal to you then I suggest you wait until after the product is 1.0 and never use anything but 1.0 and other major point releases.

--Asa