public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeffrey Forman <jforman@gentoo.org>
To: gentoo-core@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] DOWNTIME/upgrade for bugs.g.o at 2000 UTC
Date: Sun, 17 Jul 2005 15:12:43 -0400	[thread overview]
Message-ID: <42DAADAB.4010004@gentoo.org> (raw)

Hey all,

It's that time again...the time you get to get up from your
chairs/couches/bathtubs and grab a drink from the fridge because I am
bringing down bugs.g.o for about 30 minutes at 2000UTC, give or take. I
am applying the 2.18.1 -> 2.18.3 upgrade as evidenced by some recently
discovered and patched bugs in bugzilla itself.

Things also to be done:
1. I will also be fixing a bunch of bugs that were closed as duplicates,
but for some reason the DUPLICATE resolution tag never was applied.
2. I am applying a spiffy new autolink feature. Just like being able to
cite "bug #XXXX" and a link is created, now "glsa #XXXX-Y" will be
active so that our security folks can more easily reference glsa's.

anything else i've forgotten, i credit to the bugzilla devs and their
uber-helpful nature over in irc.mozilla.org.

just to recap:
1. bugzillza downtime at 2000UTC (thats 4pm EDT, 1pm PDT) for about 30
minutes
2. get up, get preferred beverage, and consume
3. wait until i bring bugs.g.o back up with spiffy new version.

Regards,
Jeffrey

-jeff

-- 

------------------
Jeffrey Forman
Gentoo Infrastructure
Gentoo Release Engineering
Bugs.Gentoo.Org Admin
jforman@gentoo.org
------------------

-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2005-07-17 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 19:12 Jeffrey Forman [this message]
2005-07-17 20:12 ` [gentoo-dev] Re: [gentoo-core] DOWNTIME/upgrade for bugs.g.o at 2000 UTC Jeffrey Forman
2005-07-17 21:27 ` [gentoo-dev] " Kumba
2005-07-18 11:34   ` Ned Ludd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42DAADAB.4010004@gentoo.org \
    --to=jforman@gentoo.org \
    --cc=gentoo-core@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox