public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sourceware Overseers <overseers@sources.redhat.com>
Cc: GDB Development <gdb@sourceware.org>,
	        Binutils Development <binutils@sourceware.org>,
	        Frysk List <frysk@sourceware.org>,
	newlib@sourceware.org,         systemtap@redhat.com,
	libc-alpha@sourceware.org
Subject: upcoming bugzilla outage
Date: Wed, 10 Dec 2008 20:35:00 -0000	[thread overview]
Message-ID: <m3r64fixbd.fsf@fleche.redhat.com> (raw)

Hi all.  Please excuse the cross-post.  And, if you do respond, please
trim the CC list (but also please continue to CC me, since I am not on
all of these lists).

I've been wanting to move gdb from gnats to bugzilla for some time
now.  I think I've finally procrastinated enough.

I intend to do the switchover next Thursday, Dec 18.  If this poses a
problem for you, please let me know.

If you are seeing this on a list other than the gdb list, it is
because this outage will take down bugzilla for your project while I
do the transition.  An outage is necessary because we would like the
converted bug IDs to be sequential.

I will dump the database before starting, so if something awful
happens, I will have a backup.  I thought you'd want to know.

I have done this upgrade several times on a local bugzilla instance,
and I think it should go reasonably well.  Still, it may take a few
hours.  I'll start in the morning, US Mountain time.


GDB readers: I'm going to disable gnats before I start.  I'll send a
patch to update the web pages.  I have a patch to fix the scripts in
CVSROOT so that commits are logged in bugzilla, not gnats.  I will
check this in once everything is working.  If you could briefly
refrain from commits which update Gnats, that would be helpful.

Overseers: I'd like to keep the gnats database around for a while,
just in case we happen to need something.  But, I think that once this
conversion is complete, we can at the very least disable the service.

Tom

                 reply	other threads:[~2008-12-10 20:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3r64fixbd.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=frysk@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=newlib@sourceware.org \
    --cc=overseers@sources.redhat.com \
    --cc=systemtap@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).