Closed Bug 486055 Opened 16 years ago Closed 16 years ago

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: brendan, Assigned: justdave)

Details

Standards are fun! We did this already from 3.1 to 3.x -- archive and everything updated nicely. Dave says he can do it again. Thanks, /be
You should probably post to the list warning people about the rename before we actually do it, just so that said warning gets caught by their existing list filters, since users will have to change any filters matching the list. Let me know here once you've done that (or if you think it's not necessary) and I'll go ahead and do the rename. It's all scripted these days, much less hassle than it used to be. :)
Assignee: server-ops → justdave
Will do -- stand by, probably tomorrow at this point. Thanks, /be
ready yet?
Not yet, Ecma folks out of office and such. Soon, perhaps this week yet. /be
Ready (this past Thursday, my fault for not notifying sooner here). /be
Did this happen? /be
Sorry, got lost in the shuffle after my vacation... [root@dm-mailman01 ~]# renamelist es3.x-discuss es5-discuss If you don't know what you're doing, hit Control-C now. Otherwise press ENTER to continue. Shutting down mailman: [ OK ] Renaming Es3.x-discuss to es5-discuss Moving list data and archives... (lots of output about list archive rebuilding omitted) Pickling archive state into /var/lib/mailman/archives/private/es5-discuss/pipermail.pck Regenerating mailman-maintained aliases... adding forwarding aliases for legacy name to /etc/postfix/virtual-mozilla... virtual-mozilla,v --> virtual-mozilla revision 1.860 (locked) done virtual-mozilla,v <-- virtual-mozilla new revision: 1.861; previous revision: 1.860 done Starting mailman: [ OK ] Done.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.