[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Comment #55 from Manuel López-Ibáñez manu at gcc dot gnu.org 2010-09-24 11:51:09 UTC --- (In reply to comment #54) Upgrade complete. Have fun! By the way, I think I speak for the GCC project and its users when I say: Merci beaucoup, Frédéric! I hope we weren't very annoying with the little fiddling and bike-shedding. The new bugzilla looks nice. You indeed did something that many of us thought was an impossible feat! -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 --- Comment #56 from Frédéric Buclin LpSolit at netscape dot net 2010-09-24 16:35:58 UTC --- (In reply to comment #55) By the way, I think I speak for the GCC project and its users when I say: Merci beaucoup, Frédéric! I hope we weren't very annoying with the little fiddling and bike-shedding. Thanks a lot! I really appreciate. :) No worry, the GCC team was very nice. It was a pleasure to work with you all. -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 --- Comment #57 from Tom Tromey tromey at gcc dot gnu.org 2010-09-24 21:34:23 UTC --- Thank you very much for doing this. I am hoping you would also be interested in upgrading the sourceware.org bugzilla installation. It is hosted on the same machine... -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 --- Comment #58 from Frédéric Buclin LpSolit at netscape dot net 2010-09-24 21:39:26 UTC --- (In reply to comment #57) I am hoping you would also be interested in upgrading the sourceware.org bugzilla installation. It is hosted on the same machine... Yup, see http://sourceware.org/bugzilla/show_bug.cgi?id=4790 -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 Steven Bosscher steven at gcc dot gnu.org changed: What|Removed |Added CC||steven at gcc dot gnu.org --- Comment #59 from Steven Bosscher steven at gcc dot gnu.org 2010-09-24 21:49:46 UTC --- This deserves mentioning on gcc.gnu.org. Thanks for the upgrade! -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 --- Comment #60 from Gerald Pfeifer gerald at pfeifer dot com 2010-09-24 21:58:18 UTC --- (In reply to comment #59) This deserves mentioning on gcc.gnu.org. Thanks for the upgrade! Yep, I had asked Frédéric for some input already. :-) -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #52 from LpSolit at netscape dot net 2010-09-22 20:16 --- Created an attachment (id=21864) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21864action=view) upgrade to 3.6.2 patch, final (v2) Based on recently filed bugs and on some changes which have been accepted upstream meanwhile, here is an updated version of the core changes. This is the version I plan to use tomorrow. -- LpSolit at netscape dot net changed: What|Removed |Added Attachment #21851|0 |1 is obsolete|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #53 from LpSolit at netscape dot net 2010-09-22 20:18 --- Created an attachment (id=21865) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21865action=view) GCC extension for 3.6.2, final (v2) And its extension counterpart. I fixed all bugs reported yesterday and today, so we are ready to upgrade. -- LpSolit at netscape dot net changed: What|Removed |Added Attachment #21852|0 |1 is obsolete|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #50 from LpSolit at netscape dot net 2010-09-20 21:43 --- Created an attachment (id=21851) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21851action=view) upgrade to 3.6.2 patch, final Here is my last iteration of the patch for the 3.6.2 upgrade. This patch alters core code. I will attach the GCC extension separately. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #51 from LpSolit at netscape dot net 2010-09-20 21:47 --- Created an attachment (id=21852) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21852action=view) GCC extension for 3.6.2, final Here is the final version of GCC extension itself. You untar it from the bugzilla/ base directory, i.e. you will get bugzilla/extensions/GCC/. Now is a good time to hammer the test installation. I prefer bugs to be reported *before* the upgrade. If you see something wrong after the upgrade, don't complain. :) -- LpSolit at netscape dot net changed: What|Removed |Added Attachment #19830|0 |1 is obsolete|| Attachment #19831|0 |1 is obsolete|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #49 from LpSolit at netscape dot net 2010-09-16 22:51 --- (In reply to comment #48) The current bugzilla has extra separating lines with the column names. The new installation does not. Yeah, it is so by design. Not something I'm going to reimplement. Note that we finally won't upgrade tomorrow. I have severe hardware failures with my PC, and I cannot reliably run the upgrade process under these conditions. It's a miracle when I can comment in a bug without seeing my PC shut down for no reason. Sorry about that. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #47 from LpSolit at netscape dot net 2010-09-15 21:16 --- Per the email Ian sent a few minutes ago, we will upgrade Bugzilla this Friday, September 17, for three hours starting at 18:00 GMT (11:00 PDT). So *please* give a try at our test installation, and report any problem with it asap. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #46 from LpSolit at netscape dot net 2010-09-12 20:24 --- I read the patch attached to this bug, and I created a TODO list from it: http://gcc.gnu.org/bugzilla-test/buglist.cgi?quicksearch=%3ABugzilla Tell me if some of these features are no longer needed, to not make me waste my time. Also file a bug (on the test installation) if I missed something which should be ported to the new installation. I intentionally ignored all scripts in the contrib/ directory, because I'm pretty sure everything can already be accomplished with the official email_in.pl script. There are also some minor tweaks which I ignored as they don't seem important enough, at least for now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #41 from rguenth at gcc dot gnu dot org 2010-09-10 09:33 --- (In reply to comment #40) A test installation based on a copy of the GCC Bugzilla database (snapshot taken today, September 9) and upgraded to Bugzilla 3.6.2 is now live at http://gcc.gnu.org/bugzilla-test/. Please give it a look, and file bugs related to missing or broken customizations in the new Bugzilla product on the test installation, i.e. using this link: http://gcc.gnu.org/bugzilla-test/enter_bug.cgi?product=Bugzilla Note that I didn't port *any* customization yet, so you probably have a lot to say. ;) You probably should announce this on g...@gcc.gnu.org. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #42 from jv244 at cam dot ac dot uk 2010-09-10 09:58 --- (In reply to comment #40) Please give it a look, and file bugs related to missing or broken customizations in the new Bugzilla product on the test installation, i.e. using this link: http://gcc.gnu.org/bugzilla-test/enter_bug.cgi?product=Bugzilla FYI, I can't login to the new bugzilla because my current password is 5 chars, which seemingly is less than the minimum for the new bugzilla. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #43 from burnus at gcc dot gnu dot org 2010-09-10 10:29 --- The attachment is not viewable in your browser due to security restrictions enabled by Bugzilla. In order to view the attachment, you first have to download it. I think at least text/* attachments should be shown. I think the restriction is to avoid problems with, e.g., HTML attachments, which can steal cookies. Thus some sites (like bugzilla.mozilla.org) use a different (sub)domain for the attachments. (A different subdomain would be fine for me as well - as would be HTTPS [at least for the login] but I think that's an item for overseers.) In any case, I would like to see the possibility to view patches and examples w/o downloading. Example: http://gcc.gnu.org/bugzilla-test/attachment.cgi?id=21126action=edit -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #44 from LpSolit at netscape dot net 2010-09-10 10:34 --- (In reply to comment #43) I think at least text/* attachments should be shown. Ah yes, sorry, I forgot to enable the allow_attachment_display parameter (which is off by default). This is now fixed. Thanks for catching that! :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #45 from jakub at gcc dot gnu dot org 2010-09-10 10:46 ---
The Log In line in elinks looks quite weird. There is
a text field Bugzilla_login, then Bugzilla_password (both expected), but then
there is another text field prefilled with password:
input id=Bugzilla_login_top
class=bz_login
name=Bugzilla_login
onfocus=mini_login_on_focus('_top')
input class=bz_password
id=Bugzilla_password_top
name=Bugzilla_password
type=password
input class=bz_password bz_default_hidden bz_mini_login_help type=text
id=Bugzilla_password_dummy_top value=password
onfocus=mini_login_on_focus('_top')
Took me a while to figure out one shouldn't input password in there...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #40 from LpSolit at netscape dot net 2010-09-09 22:43 --- A test installation based on a copy of the GCC Bugzilla database (snapshot taken today, September 9) and upgraded to Bugzilla 3.6.2 is now live at http://gcc.gnu.org/bugzilla-test/. Please give it a look, and file bugs related to missing or broken customizations in the new Bugzilla product on the test installation, i.e. using this link: http://gcc.gnu.org/bugzilla-test/enter_bug.cgi?product=Bugzilla Note that I didn't port *any* customization yet, so you probably have a lot to say. ;) -- LpSolit at netscape dot net changed: What|Removed |Added URL||http://gcc.gnu.org/bugzilla- ||test/ http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #39 from LpSolit at netscape dot net 2010-09-08 21:35 --- I have done some progress. The DB has been successfully upgraded to 3.6.2 (locally, of course), and I have converted GCC hardcoded columns into custom fields, i.e. using offically supported features in Bugzilla 3.x. So I will be able to install a test installation on the server soon, so that you can have a first look at the new installation. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #30 from LpSolit at netscape dot net 2010-09-07 14:54 --- Daniel, did you get the email I sent you on August 19? I need some help to start working on this project. Just in case someone else can help too, here is the content of the email I sent to Daniel: The welcome email I got contains this command, which doesn't work: $ cvs -z9 -d :ext:lpso...@sourceware.org:/cvs/sourceware co sourceware cvs server: cannot find module `sourceware' - ignored cvs [checkout aborted]: cannot expand modules Same for this broken link: http://sourceware.org/cgi-bin/cvsweb.cgi/sourceware?cvsroot=sourceware I saw that the Bugzilla code is located at /cvs/gcc/wwwdocs/bugzilla/. How am I supposed to access it, then? Have I been added to the wrong group? I also tried: $ cvs -z9 -d :ext:lpso...@sourceware.org:/cvs/gcc/wwwdocs co bugzilla Cannot access /cvs/gcc/wwwdocs/CVSROOT No such file or directory Is the welcome message obsolete or am I doing something wrong? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #31 from tromey at gcc dot gnu dot org 2010-09-07 15:50 --- (In reply to comment #30) $ cvs -z9 -d :ext:lpso...@sourceware.org:/cvs/sourceware co sourceware cvs server: cannot find module `sourceware' - ignored cvs [checkout aborted]: cannot expand modules Use the module name infra instead: cvs -z9 -d :ext:lpso...@sourceware.org:/cvs/sourceware co infra I haven't looked at the welcome instructions in a long time, but they are auto-generated, so maybe they are misleading in this case. I saw that the Bugzilla code is located at /cvs/gcc/wwwdocs/bugzilla/. How am I supposed to access it, then? Have I been added to the wrong group? I also tried: $ cvs -z9 -d :ext:lpso...@sourceware.org:/cvs/gcc/wwwdocs co bugzilla Check out the wwwdocs module from gcc's cvs repository: cvs -z9 -d :ext:lpso...@sourceware.org:/cvs/gcc co wwwdocs There are actually 2 bugzilla instances running on sourceware. I am not certain that the second one is in cvs at all. Also, of course, the databases are not in cvs, you will have to get them by some other means. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #32 from gerald at pfeifer dot com 2010-09-07 16:15 --- I believe the following should work: cvs -z9 -d :ext:lpso...@gcc.gnu.org:/cvs/gcc co wwwdocs bugzilla is a subdirectory there, not a module. sourceware.org and gcc.gnu.org should both work, but since is GCC Bugzilla and I am using the gcc.gnu.org server name, I figured I'd provide those. :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #33 from LpSolit at netscape dot net 2010-09-07 16:22 --- I guess you meant to be CC'ed? -- LpSolit at netscape dot net changed: What|Removed |Added CC||gerald at pfeifer dot com GCC build triplet|ger...@pfeifer.com | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #34 from tom dot browder at gmail dot com 2010-09-07 17:58 --- (In reply to comment #33) I guess you meant to be CC'ed? Yes. The work I started was a Perl script to convert a 2.20+ database to the latest version. The last question I had of Daniel was could we get a test bed so others could try out the new bugzilla setup--looks like that is underway. There was another problem I had that I don't remember at the moment, but that was where I left it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #35 from LpSolit at netscape dot net 2010-09-07 18:11 --- (In reply to comment #34) The last question I had of Daniel was could we get a test bed so others could try out the new bugzilla setup--looks like that is underway. Yes, we will have a test installation, as discussed in comment 27. But I first need shell access, which is why I'm blocked right now. Waiting for Daniel or someone else for help here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #36 from fche at redhat dot com 2010-09-07 18:16 --- You're all set with plain shell access now. Connect to irc.freenode.net #overseers for any further needs. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
-- fche at redhat dot com changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |LpSolit at netscape dot net |dot org | Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #37 from dberlin at gcc dot gnu dot org 2010-09-07 22:50 --- Subject: Re: Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6 You should have shell access, do you not? On Tue, Sep 7, 2010 at 2:11 PM, LpSolit at netscape dot net gcc-bugzi...@gcc.gnu.org wrote: --- Comment #35 from LpSolit at netscape dot net 2010-09-07 18:11 --- (In reply to comment #34) The last question I had of Daniel was could we get a test bed so others could try out the new bugzilla setup--looks like that is underway. Yes, we will have a test installation, as discussed in comment 27. But I first need shell access, which is why I'm blocked right now. Waiting for Daniel or someone else for help here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #38 from LpSolit at netscape dot net 2010-09-07 22:54 --- (In reply to comment #37) You should have shell access, do you not? I have now, yes, thanks to fche, see comment 36. I now have a working local copy of GCC Bugzilla to play with (both code and DB). I have one question for you, Daniel: what is the extra_emails DB table used for? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #29 from LpSolit at netscape dot net 2010-08-09 22:21 --- (In reply to comment #28) 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. Done! I selected sourceware as project. I hope that was the correct one. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- 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
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- 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). 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). 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? 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? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #26 from nightstrike at gmail dot com 2010-05-27 23:26 --- (In reply to comment #25) Subject: Re: Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6 Note: I have no urge or time to upgrade gcc's bugzilla anymore. If ya'll want to work on it, i'm happy to give you all the info i have and get you shell access to gcc.gnu.org + the current bugzilla code + it's mysql so you can do it. I'll volunteer to do it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #24 from LpSolit at netscape dot net 2010-03-30 09:54 --- We are very close from releasing Bugzilla 3.6: https://bugzilla.mozilla.org/show_bug.cgi?id=554523 The plan is to release it next week. So you may as well upgrade to 3.6 directly. Note that I'm on vacation this week and next week. If you need help for the upgrade, now is a good time! :) -- LpSolit at netscape dot net changed: What|Removed |Added Summary|Upgrade gcc.gnu.org/bugzilla|Upgrade gcc.gnu.org/bugzilla |to Bugzilla 3.4.5 |to Bugzilla 3.6 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
[Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
--- Comment #25 from dberlin at gcc dot gnu dot org 2010-03-30 23:18 --- Subject: Re: Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6 Note: I have no urge or time to upgrade gcc's bugzilla anymore. If ya'll want to work on it, i'm happy to give you all the info i have and get you shell access to gcc.gnu.org + the current bugzilla code + it's mysql so you can do it. On Tue, Mar 30, 2010 at 5:54 AM, LpSolit at netscape dot net gcc-bugzi...@gcc.gnu.org wrote: --- Comment #24 from LpSolit at netscape dot net 2010-03-30 09:54 --- We are very close from releasing Bugzilla 3.6: https://bugzilla.mozilla.org/show_bug.cgi?id=554523 The plan is to release it next week. So you may as well upgrade to 3.6 directly. Note that I'm on vacation this week and next week. If you need help for the upgrade, now is a good time! :) -- LpSolit at netscape dot net changed: What |Removed |Added Summary|Upgrade gcc.gnu.org/bugzilla|Upgrade gcc.gnu.org/bugzilla |to Bugzilla 3.4.5 |to Bugzilla 3.6 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
