Closed Bug 1354818 (dawn-project-seamonkey) Opened 3 years ago Closed 3 years ago

Project Dawn for SeaMonkey (remove aurora channel)

Categories

(SeaMonkey :: General, enhancement)

enhancement
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rsx11m.pub, Assigned: frg)

References

Details

(Keywords: meta)

Attachments

(5 files, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #1353924 +++

This is the SeaMonkey version of bug 1353821, whatever needs to be done specifically for SeaMonkey. Probably a lot will be taken care of in Thunderbird bug 1353924.

Fallen's task list in the other bug:
* Update aurora users to beta like in bug 1353825
* Remove aurora builds from buildbot configs and other build code
* Clean up ftp
* Make sure localization dashboard works as expected
* Update websites
* Update various services like dxr, [treeherder] to remove aurora
(In reply to rsx11m from comment #0)
> +++ This bug was initially created as a clone of Bug #1353924 +++
> 
> This is the SeaMonkey version of bug 1353821, whatever needs to be done
> specifically for SeaMonkey. Probably a lot will be taken care of in
> Thunderbird bug 1353924.

Not really, since our infra and buildbot stuff are not the same as TB's,
we need to do a bunch of things.  

On the top of my head:

1) The first thing would be to update our buildbot-config files.
2) Change our updates server to not serve aurora and move them to c-b.
  (on balrog).  Not entirely sure if there's anything to do (or worth
  doing) on aus2.
3) Possible website changes.
Looked at the buildbot files which include references to aurora over the weekend. There are a few but possible not all relevant (calendar etc...).

Switching users to beta is imho not necessary. There are at least 2 bugs stating that automatic updates are broken. Something to look at after the balrog move imho.

What about l10n? With l10n builds broken I don't see a (new) problem here but is anything linked to aurora?

2 code references for aurora and maybe a few others where a2 is explicitly checked in the version. DidnÄt fand any and shouldn't be a problem. Can be taken care of after the tree is dead.
(In reply to Frank-Rainer Grahl from comment #2)
> Switching users to beta is imho not necessary. 
Maybe I am misunderstanding this, but you need to move aurora users somewhere. You don't want to leave them in a dead end.
> Maybe I am misunderstanding this, but you need to move aurora users somewhere. You don't want to leave them in a dead end.

Unfortunately they are already there and need to update manually. Automatic updates are broken for Nightly and Aurora. ewong is moving SeaMonkey to balrog and that is one of the things to fix afterwards. So testers aon the chanlle know that they need to install a full package.
Attached patch [configs] proposed patch (v1) (obsolete) — Splinter Review
Since 2.52 (Gecko 55) is on trunk, it will stay there for the next
two iterations.  Then it hits Beta.

So once 2.52 hits beta, none of the version after it will hit aurora,
so we can then remove mentions of comm-aurora.
Attachment #8859487 - Flags: review?(frgrahl)
>> +if BRANCHES['comm-aurora']['gecko_version'] < 55:

Do we really need this any longer? I would just delete aurora everything on the buildbot. Its dead Jim and will stay at 54/2.51 forever.
Flags: needinfo?(ewong)
(In reply to Frank-Rainer Grahl from comment #6)
> >> +if BRANCHES['comm-aurora']['gecko_version'] < 55:
> 
> Do we really need this any longer? I would just delete aurora everything on
> the buildbot. Its dead Jim and will stay at 54/2.51 forever.

my mistake.  hadn't realized that there was a merge and that 2.51 is already
on beta.
Flags: needinfo?(ewong)
Attachment #8859487 - Attachment is obsolete: true
Attachment #8859487 - Flags: review?(frgrahl)
Attachment #8859813 - Flags: review?(frgrahl)
Comment on attachment 8859813 [details] [diff] [review]
[configs] proposed patch (v2)

Looks good.
Attachment #8859813 - Flags: review?(frgrahl) → review+
Attachment #8860679 - Flags: review?(iann_bugzilla)
Comment on attachment 8860679 [details] [diff] [review]
1354818-remove-aurora.patch

Thanks r=me
Attachment #8860679 - Flags: review?(iann_bugzilla) → review+
Website patch. I changed the approval text to reflect reality but didn't put IanN as the current sole approver directly in it :)
Attachment #8860722 - Flags: review?(iann_bugzilla)
(In reply to Frank-Rainer Grahl from comment #13)
> Created attachment 8860722 [details] [diff] [review]
> 1354818-aurora-website.patch
> 
> Website patch. I changed the approval text to reflect reality but didn't put
> IanN as the current sole approver directly in it :)

What web page would you get after this patch if you are on the alpha channel?
Flags: needinfo?(frgrahl)
> What web page would you get after this patch if you are on the alpha channel?

The patch shouldn't change anything here. The redirect is unmodified and should still redirect to http://www.seamonkey-project.org/dev/get-involved

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

Aas for as I know the removed aurora page is not used as a starting page anywhere in SeaMonkey.
Flags: needinfo?(frgrahl)
Assignee: nobody → frgrahl
Status: NEW → ASSIGNED
Comment on attachment 8860722 [details] [diff] [review]
1354818-aurora-website.patch

Thanks r=me
Attachment #8860722 - Flags: review?(iann_bugzilla) → review+
I overlooked to remove a variable in the website patch. According to a post in todays irc log it causes problems with Adblock Plus so I did a patch with rs.

1354818-aurora-website2.patch:
https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/rev/e14189e839c5a16e6362c1398faaa65ea6040fb0
Should we close this? I think automation is dead, website is updated and references in sourceode removed. 

What should still be done?

Move aurora users to next beta in a separate bug? We would need to spin a 2.51 for this. Probably profile unhealthy to go from 2.51a2 to 2.48b1.

Some final news on the website/blog?
(In reply to Frank-Rainer Grahl from comment #19)
> Should we close this? I think automation is dead, website is updated and
> references in sourceode removed. 
> 
> What should still be done?
> 
> Move aurora users to next beta in a separate bug? We would need to spin a
> 2.51 for this. Probably profile unhealthy to go from 2.51a2 to 2.48b1.

I'm going to agree with this.  

Automation changes haven't been made in production as the config changes
haven't been pushed. (gonna do that now.. but I'm going to expect 
our infra to go a bit wonkers..  well it is a little 'weird' right now
as I have in the builders page, a building c-a mochitest, but there isn't
any mochitest jobs running.  So the master is a little weird. I'm hoping
this push will make it less weird.
oh.. it was pushed.. (https://hg.mozilla.org/build/buildbot-configs/rev/c6b3f4dfe825)
so I guess I haven't reconfig'd the master.

doing that now.
Comment on attachment 8865346 [details] [diff] [review]
[configs] remove remaining c-a mentions in buildbot-configs.

thanks
Attachment #8865346 - Flags: review?(frgrahl) → review+
https://hg.mozilla.org/build/buildbot-configs/rev/3d91107189412d48370e81e80e36a2343e132906
Bug 1354818 - Remove remaining references to comm-aurora in buildbot configs r=frg
c-a has been removed from buildbot, so it's just now c-c, c-b and c-r.  

Next stop... add esr52.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
No longer blocks: 1353825
You need to log in before you can comment on or make changes to this bug.