765814 - Please redirect nightly-profiling users to the nightly branch

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[(no longer active)]

The profiling branch is being repurposed, and is no longer useful for human users.  I'll file another bug to stop doing nightly builds on it.

Comment 1

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

So just point them at mozilla-central builds and leave the channel alone ? Are you planning to do nightlies on the buildwithfp repo, and if so on what channel ?

Comment 2

[(no longer active)]

(In reply to Nick Thomas [:nthomas] from comment #1)
> So just point them at mozilla-central builds and leave the channel alone ?

Yes.

> Are you planning to do nightlies on the buildwithfp repo, and if so on what
> channel ?

No, the nightlies have already been disabled there.

Comment 3

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

Attachment: [cvs] AUS config change

Comment 4

[[e-mail] (:bhearsum)]

Comment on attachment 634287 [details] [diff] [review]
[cvs] AUS config change

Do we need to channel-change these folks too? Or just keep this active forever?

Comment 5

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

That's what I was asking in comment #1. Turns out there about about 30 blocklist pings a day on the nightly-profiling channel, so natural attrition will probably take care of things.

Comment 6

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

Comment on attachment 634287 [details] [diff] [review]
[cvs] AUS config change

Checking in config-dist.php;
/cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v  <--  config-dist.php
new revision: 1.216; previous revision: 1.215
done

$ cvs tag AUS2_PRODUCTION config-dist.php 
W config-dist.php : AUS2_PRODUCTION already exists on version 1.215 : NOT MOVING tag to version 1.216
$ cvs tag -F AUS2_PRODUCTION config-dist.php 
T config-dist.php

Comment 7

[(no longer active)]

While updates now work for me, the About dialog still tells me that I'm on the nightly-profiling channel.  Do you know why that is?  And is that something that I should be worried about?

Comment 8

[Rail Aliiev [:rail]]

Because of defaults/pref/channel-prefs.js which is not updated by our normal MAR files.

Comment 9

[(no longer active)]

So is that something which people need to update manually?  Or can they just ignore it?

Comment 10

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

Either of those, or we can whip up small mar files that just modify channel-prefs.js.

Comment 11

[(no longer active)]

(In reply to Nick Thomas [:nthomas] from comment #10)
> Either of those, or we can whip up small mar files that just modify
> channel-prefs.js.

That would be cool!  :-)