160127 - latest milestone on start page is out of date

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Matt Kraai]

The default start page suggests 1.1 Alpha for Milestone-build users.  It should
suggest 1.1 Beta.

Comment 1

[Matt Kraai]

Attachment: patch

Comment 2

[Alfonso Martinez]

*** Bug 161058 has been marked as a duplicate of this bug. ***

Comment 3

[Michael Lefevre]

*** Bug 161289 has been marked as a duplicate of this bug. ***

Comment 4

[Roozbeh Pournader]

Please note that it suggests '1.1 Alpha' even if you are already running '1.1
Beta'. With some newbies confusing the definition of alpha and beta (no this is
not a joke, but a real situation), this will lead them to bad headaches.

Comment 5

[Bradley Baetz (:bbaetz)]

*** Bug 161476 has been marked as a duplicate of this bug. ***

Comment 6

[Matt Kraai]

Whoops.  I just noticed the last sentence on the page:

 Suggestions for this page to Gerv

Comment 7

[Gervase Markham [:gerv]]

Someone fixed this.

Gerv

Comment 8

[Michael Lefevre]

rather than filing yet another new bug, seems reasonable to reopen this one...

latest milestone is now 1.1, not 1.1beta, so the start page needs updating again.

Comment 9

[Matt Kraai]

Attachment: patch for 1.1

Comment 10

[Gervase Markham [:gerv]]

I won't have the ability to fix this until next week. If you can find someone 
else to do it, that would be great. In general, we need a better solution to 
this. Anyone got any ideas?

Gerv

Comment 11

[Matt Kraai]

The download links on the main page, the release page, and the start page should
all generated from one source.

Until this happens, though, it would be nice to include the start page in the
list of pages that should be updated for each release.  Does such a list exist?

Comment 12

[benc]

Well, we need some master file that says "the current release is <BLAH>"

What is needed to tweek that page? Just a single string change? if so, I can do
it, I've looked at the page a bit.

If there is javascript-isms involved as well, I probaly shouldn't. Now that I
think about it, we need to tell 1.1b users to go to 1.1 right?

Comment 13

[Matt Kraai]

You can fix the problem for now by applying my patch for 1.1.

Comment 14

[Gervase Markham [:gerv]]

Fixed (wait 1 hour for site to sync.) Thanks, Matt :-)

Gerv

Comment 15

[Michael Lefevre]

that's great.

however, given that 1.2a should be out in just a few days, is there any chance
of preparing and making a rather more timely update for it?

Comment 16

[Michael Lefevre]

reopening once again.

1.2a was released, so the start page needs updating again...

Comment 17

[Gervase Markham [:gerv]]

Should be fixed now.

Gerv

Comment 18

[Michael Lefevre]

it is indeed. thanks.

verified.

Comment 19

[Michael Lefevre]

time to fix it again...

Comment 20

[Gervase Markham [:gerv]]

Fixed.

Gerv

Comment 21

[Michael Lefevre]

Unfixed again

Comment 22

[Michael Lefevre]

I see from the page (and bonsai -
http://www.mozilla.org/webtools/bonsai/cvslog.cgi?file=mozilla-org/html/start/index.html&rev=&root=/cvsroot/
) that endico fixed this today. resolving as fixed.

Comment 23

[Michael Lefevre]

changed again, reopening...

Comment 24

[Michael Lefevre]

*** Bug 186877 has been marked as a duplicate of this bug. ***

Comment 25

[Michael Lefevre]

*** Bug 186843 has been marked as a duplicate of this bug. ***

Comment 26

[Michael Lefevre]

*** Bug 186967 has been marked as a duplicate of this bug. ***

Comment 27

[Michael Lefevre]

*** Bug 184036 has been marked as a duplicate of this bug. ***

Comment 28

[Gervase Markham [:gerv]]

I can't fix this for a while; if anyone else can, please do. Use the Doctor :-)

Gerv

Comment 29

[Gervase Markham [:gerv]]

This should be fixed in the next couple of hours.

Gerv

Comment 30

[Michael Lefevre]

seems to be fixed now. pretty good for "I can't fix this for a while" :-)

thanks.