mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "J.H." <warthog19@eaglescrag.net>
Cc: users@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
	support@osuosl.org, Jon Tollefson <kniht@linux.vnet.ibm.com>,
	Martin Bligh <mbligh@mbligh.org>,
	"Jorge O. Castro" <jorge@ubuntu.com>,
	bugme-admin@linux-foundation.org,
	"FTPAdmin Kernel.org" <ftpadmin@kernel.org>,
	Jim Zemlin <jzemlin@linux-foundation.org>
Subject: Re: [KORG] Bugzilla Upgrade / Server move
Date: Wed, 25 Mar 2009 11:57:54 +0000	[thread overview]
Message-ID: <20090325115754.7ffb67ce@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <49C9D99D.2050400@eaglescrag.net>

> The code base has had a rather extensive upgrade, migrating custom
> fields over to Bugzilla's 3.x custom field support, and dealing with
> kernel.org specific changes.

That has been needed for soooo long - thanks a lot.

> If you have any issues, problems, concerns, please don't hesitate to get
> a hold of me, ftpadmin@kernel.org and/or bugme-admin@linux-foundation.org

Looks basically sound on a quick test. I've closed a lot of the bugs in
our bugzilla against our bugzilla as they are now fixed.

Only glitch so far is formatting (needed a shift-reload to clear the old
style sheet) but then still has problems because the version some people
enter is very very long and that field doesn't have a sensible width
forced in the list format.

There are some other things that need sorting once its settled - a lot of
the owner data and auto-assignment stuff is stale (eg reiser is still
assigned to namesys!) perhaps they should all be assigned to a mailing
list of the form bugzilla-category-subcat so that it becomes entirely
mailman "self service" ?

  reply	other threads:[~2009-03-25 12:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  7:13 J.H.
2009-03-25 11:57 ` Alan Cox [this message]
2009-03-25 14:38   ` Martin Bligh
2009-03-25 20:21 ` [kernel.org users] " Pierre Ossman
2009-03-26  1:12   ` Dave Airlie
2009-03-26  7:11     ` Pierre Ossman
2009-03-26  7:23 ` Tejun Heo
2009-03-26  7:48   ` Stefan Richter
2009-03-26  8:04     ` Stefan Richter
2009-03-26 19:21       ` J.H.

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=20090325115754.7ffb67ce@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bugme-admin@linux-foundation.org \
    --cc=ftpadmin@kernel.org \
    --cc=jorge@ubuntu.com \
    --cc=jzemlin@linux-foundation.org \
    --cc=kniht@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --cc=support@osuosl.org \
    --cc=users@kernel.org \
    --cc=warthog19@eaglescrag.net \
    /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

all inboxes | Powered by JetHome®