------- Comment #28 from dberlin at gcc dot gnu dot org 2010-07-19 12:00 ------- Subject: Re: Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
On Thu, Jul 15, 2010 at 7:04 PM, LpSolit at netscape dot net <gcc-bugzi...@gcc.gnu.org> wrote: > > > ------- Comment #27 from LpSolit at netscape dot net 2010-07-15 23:04 ------- > For those who are interested, I'm on vacation till mid-August, meaning that I > have some free time to help upgrading GCC Bugzilla to 3.6.1. > > As it's not acceptable to play with a production installation, we would need a > test installation on which we can apply patches and test them (we could file > bugs and attach patches to the test installation directly, so that we can test > the installation for real). That's fine. I used to do this on my local machine (home.dberlin.org). You could also setup a test instance on sourceware.org (which is what gcc.gnu.org is really running on) > Once everybody is happy with how things work, and > thinks everything which is needed has been ported to the new installation, we > can make a monolithic patch with all changes in it, and attach it to this bug > for the record (as the test installation will probably go away once the > upgrade > process is complete). > Sounds right > The only efficient way I know to customize a Bugzilla installation is to use > e.g. CVS or bzr to apply patches, and let the test installation be upgraded > from there, so that we can easily generate patches and back them out. Else > it's > going to be a mess pretty quickly. Is this doable by the GCC team? Currently bugzilla is under cvs, but it's a bit of a mess (my fault, of course ;P). The rest of GCC uses SVN, the www stuff has never been moved over because there are a bunch of automated checkin scripts/etc that nobody has had the urge to port. > Else I would > have to do it locally, and apply patches manually to the test installation, > meaning that I would be the only one able to generate patches on top of other > patches. > > What do you think? I think you should probably set yourself up an account on sourceware. Fill out this form: http://sourceware.org/cgi-bin/pdw/ps_form.cgi and list me as your referrer. The bugzilla stuff for GCC is in /www/gcc/bugzilla I honestly do not remember the qmail related magic that makes the incoming aliases go to the right perl scripts. However, overseers@ has the folks who set this up and understand how qmail works. --Dan -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
