415964 - Wiki Page should be updated with release tags

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Shawn Wilsher :sdwilsh]

We have a wiki page that advertises CVS tags, but it doesn't appear to be updated.

I visited with Aptana last week, and one of their difficulties with using mozilla was not knowing how to get a "stable" tag of the source tree like 1.9b3.  Having an up-to-date wiki page for outside developers would be a huge win for dev-rel.

We should at least do something to make things easier for them.  That page isn't structured very well, so perhaps some re-factoring should go into it.

Comment 1

[Robert Helmer [:rhelmer]]

We track release over here too:
http://wiki.mozilla.org/Releases

I'd like to minimize the number of different pages with the same information, if possible :) Wiki is also not a very nice place to track this kind of thing, but it's better than nothing.

I think that we're not that great in general at exposing this kind of thing because we're focused on releasing our own products. Using this tags page as a way to keep up-to-date on the platform seems really suboptimal.

Comment 2

[Shawn Wilsher :sdwilsh]

I think that we should do something at least.  As it stands, it isn't obvious to me what tag to pull to get 1.9b3 from the page you linked (and then going to the firefox 3 b 3 page, and then trying to find it).

Comment 3

[Uri Sarid]

Thanks Shawn, it really would be great to make it easier for outsiders like us to stay on top of releases. We also contribute back bugs, fixes and enhancements, so it helps Mozilla's own product releases as well. I agree it would be good to keep it one place. 

At least for now, what *is* the right tag to pull to get 1.9b3? We need to pull it this week, for many purposes but in particular to get around the flush-to-disk problems with SQLite3.

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

The tag
  FIREFOX_3_0b3_RELEASE 
was applied to MOZ_CO_PROJECTS=all, which includes xulrunner, firefox, thunderbird etc etc (see client.mk for the full list).

Comment 5

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

We have tag information in our build pages, done for each release. Here's some examples:
http://wiki.mozilla.org/Firefox_2.0.0.12:BuildNotes
http://wiki.mozilla.org/Firefox_3.0b4:BuildNotes

Is that enough, or do we need to find a way to duplicate this info?

Comment 6

[Shawn Wilsher :sdwilsh]

That requires people to find those pages first.  The most useful thing to outside consumers would be to have all that information on one page.

Comment 7

[[e-mail] (:bhearsum)]

I'm closing this bug.

We've been pretty good at keeping CVS_Tags up-to-date, afaict. In any case, I don't think keeping this bug open any longer serves any purpose.

Comment 8

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.