667333 - Add htaccess rules for redirecting nightly relnotes to dev/get-involved [seamonkey2.4a1 404]

Status: RESOLVED FIXED

(SeaMonkey :: Website, defect)

Description

[Jens Hatlak (:InvisibleSmiley)]

With the new rapid release model, trunk builds always identify themselves as <version>a1, Aurora as <version>a2 and Beta as <version>. For Beta, the same relnotes pages as for to-be final need to be created (with a dedicated bug per case), and maybe a simple page should be set up for Aurora builds, too (but that's beyond the scope of this bug).

This bug is about adding htaccess rules for redirecting nightly relnotes to dev/get-involved. Currently the rules look like this:

# redirect relnotes of -pre versions to the get involved page
RedirectMatch temp ^/releases/seamonkey.*pre/ http://www.seamonkey-project.org/dev/get-involved
Redirect temp /releases/seamonkey1.5a/ http://www.seamonkey-project.org/dev/get-involved

The tricky part here is to write a set of rules that work for any release from 2.2 and on (we can ignore the fact that there were no 2.2a1, 2.2a2 or 2.3a1 here) while not messing with 2.1 and earlier releases, since we need to keep the dedicated relnotes we have for these.

Draft, (hopefully) taking 1.0, 1.1, 2.0 (plus any minor versions of the three) and 2.1 into account:

RedirectMatch temp ^/releases/seamonkey(?![12]\.[01]).*a1/ http://www.seamonkey-project.org/dev/get-involved

Zero-width negative lookahead. PCRE FTW! :-)

Speak up now (prove me wrong) or forever hold your peace!

Comment 1

[Jens Hatlak (:InvisibleSmiley)]

Interesting, there is no 1.0a1 nor 1.1a1, only 1.0a and 1.1a. Also there is no a1 for any of the minor releases. So it's only 2.0a1 and 2.1a1. Anyway, the above regex is still the best way to go forward since it doesn't redirect for any of the older versions for which pages never will exist. Committing now.

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

redirect relnotes of rapid release train trunk (need to exclude 1.0-2.1

Checking in .htaccess;
/www/seamonkeyproject-org/src/.htaccess,v  <--  .htaccess
new revision: 1.17; previous revision: 1.16
done

Comment 3

[Robert Kaiser]

What about aurora builds (*a2)?

Comment 4

[Jens Hatlak (:InvisibleSmiley)]

(In reply to comment #3)
> What about aurora builds (*a2)?

Quoting from comment 0: "and maybe a simple page should be set up for Aurora builds, too (but that's beyond the scope of this bug)"

Comment 5

[Jens Hatlak (:InvisibleSmiley)]

Coming back to the aurora question: Basically it depends on what we want to do in the future. In the past we've had relnotes for alphas, betas and releases. If we don't want to announce alphas anymore (which, given the shorter release cycles, might make sense), then doing the same for aurora (a2) as for trunk (a1) would be OK (and simple; technically just replacing a1 by a[12]).

KaiRo, Callek, what do you think? Or does this need further discussion elsewhere?

Comment 6

[Robert Kaiser]

I actually think we should redirect both of them to a better page than the current get-involved, but we should be the same for both.

I think we should have a better first-run experience for all versions, though, pointing to Personas and other stuff interesting for users and/or testers.

Comment 7

[Jens Hatlak (:InvisibleSmiley)]

(In reply to comment #6)
> I actually think we should redirect both of them to a better page than the
> current get-involved, but we should be the same for both.

For this bug, that "same for both" is relevant, so I did what I explained in comment 5 now (see below). Anything's better than a 404, that's for sure. But I currently lack the time to write a full new page, especially since I'll be mostly (completely?) AFK next week. Just checked in:

Handle Aurora like Beta

Checking in src/.htaccess;
/www/seamonkeyproject-org/src/.htaccess,v  <--  .htaccess
new revision: 1.18; previous revision: 1.17
done