From gonzalo.garrone at gmail.com Sun Oct 6 00:51:52 2013 From: gonzalo.garrone at gmail.com (Gonza Garrone) Date: Sat, 5 Oct 2013 21:51:52 -0300 Subject: No subject Message-ID: I commented that while I'm trying to integrate with cruise control bugzilla on ubuntu, without satisfactory results. sorry to bother you with this query but I'm a little lost. you could guide me in the process of integration? I need to integrate bugzilla with cruise control, so I'm missing some plug that reads XML cruise control to insert into the Bugzilla database. Is there any similar development? it is feasible to be done? thank you very much Gonzalo -------------- next part -------------- An HTML attachment was scrubbed... URL: From kboubi.sidki at gmail.com Sun Oct 6 20:56:20 2013 From: kboubi.sidki at gmail.com (Sidki Kboubi) Date: Sun, 6 Oct 2013 22:56:20 +0200 Subject: Self-Introduction: Sidki KBOUBI Message-ID: - Full legal name: Sidki KBOUBI - IRC: Sidkizz - Bizerte, Tunisia - Computer science engineering student - ESPRIT: Private Higher School of Engineering Technologies, Tunisia - I want to help web users by the means i can - Historical qualifications - Projects: GNU Distro, Tunisia-Events, Tasks/Actions Manager - Computer skills: Not so horrible xP - Other skills: GUI's improvement, managing resources - It's ok to share even a 15 minutes of our time per day trying to help s.one, i've needed help & i prayed that s.one will help me, and it was a good feeling when you know that s.one has dedicated his time and helped you -- Cordialement, *Sidki Kboubi,* * ** El?ve ing?nieur en g?nie informatique | ESPRIT : Ecole Sup?rieure Priv?e d'Ing?nierie et de Technologie* * * *Secr?taire g?n?ral adjoint et coordinateur scientifique: Club Jeunes Science El-Alia CJSE * *Formateur en Informatique dans l'Association Jeunes Science De Tunisie* *Secr?taire g?n?ral Club ESPRIT Libre* *Responsable de la communication externe et des relations: Club ESPRIT Game Developers * * * Contact: http://www.facebook.com/ kbbsidki, http://www.linkedin.com/in/sidkikboubi *Mobile* +216 53 828 992 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Tue Oct 8 15:26:11 2013 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 08 Oct 2013 16:26:11 +0100 Subject: No subject In-Reply-To: References: Message-ID: <52542413.9080401@mozilla.org> On 06/10/13 01:51, Gonza Garrone wrote: > I commented that while I'm trying to integrate with cruise control > bugzilla on ubuntu, without satisfactory results. sorry to bother you > with this query but I'm a little lost. > you could guide me in the process of integration? > I need to integrate bugzilla with cruise control, so I'm missing some > plug that reads XML cruise control to insert into the Bugzilla database. > Is there any similar development? it is feasible to be done? Thank you for your email. However, if you are seeking community support for Bugzilla, please see http://www.bugzilla.org/support/ , particularly the section titled "Private Emails Do Not Help Others", and then post your message in the mozilla.support.bugzilla newsgroup. Many thanks :-) Gerv From aiyushdhar85 at gmail.com Tue Oct 15 10:43:56 2013 From: aiyushdhar85 at gmail.com (Aiyush Dhar) Date: Tue, 15 Oct 2013 16:13:56 +0530 Subject: Aiyush Dhar Message-ID: Name:Aiyush Dhar City: Kolkata Country:India Student Status:1st year engineering student in computer science and engineering School:South Point High School College:Government college of engineering and ceramic technology(west bengal) I want to help fix bugs and after gaining a bit of experience help out in NSS. Qualification: No past experience in any actual project Basic knowledge of C and html. i am good at communicationg with others. I want to do this to improve my knowledge regarding coding and develop my skills.I think taking part in bugzilla would be the best start.And i would greatly like to make some friends here along the way :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcote at mozilla.com Mon Oct 21 16:19:42 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 21 Oct 2013 12:19:42 -0400 Subject: Moving Bugzilla to git? Message-ID: <5265541E.8080405@mozilla.com> Hi all, I'm the manager of Mozilla's Bugzilla team. We've talked about this idea before, but I thought I would flesh it out and ask for feedback. I think we should move the Bugzilla code off of the Bazaar system hosted by Mozilla and onto git, and maybe even GitHub. There are a few reasons for this: * git is pretty much the de facto standard for VCSs these days. This means many people are familiar with it and like its flexibility (I certainly do). * On the other side, Bazaar is almost dead. There are maybe 2-3 commits to trunk every month. * GitHub is extremely popular, and for good reason, since it's a very powerful system. Exposure via GitHub could mean increased contributions (whether we can keep up with them or not is, of course, another question. * Mozilla would very much like to retire Tinderbox, since Bugzilla is the only system still using it. Moving to GitHub means we could use travis-ci, which is really nice (we use it for other projects on my team). * Mozilla would also very much like to retire the Bazaar and CVS servers, both of which are used solely by Bugzilla. Doing a one-time migration is quite easy using fast-import/fast-export. I've verified that it works, with one small error that should be simple to fix (a single file not deleted in the git version). However, even with some advance warning, I don't think we can convert and then abandon Bazaar immediately due to Bugzilla's suggested upgrade path, which is to install a package and then pull updates directly from the Bazaar repository. If we had to do a security release, it doesn't seem right to require users to switch VCSs to get that fix. That said, I don't think we need to maintain Bazaar indefinitely, just for some grace period. I suggest 9 months, which would put that sometime mid-2014. I would, however, like to shut down CVS when we migrate to git, so that we don't have to maintain three VCSs at the same time. I haven't found a suitable solution to automatically mirror changes from git to Bazaar; there is one project[1] that at first glance appeared suitable, but after running into problems, I had a discussion with the package's author, who stated that there difficult bugs that would prevent it from working the way we would need it to. Luckily Bugzilla has already gone through this before, from CVS to Bazaar, and we have a script[2] that steps through Bazaar commits and applies them to a CVS repo. I've been modifying that script to do a similar git-to-bzr translation, and I'm confident I can get it working. The mirroring would be in a single direction, that is, from git to Bazaar; after the migration, Bazaar would be read only to everyone except the mirroring script. We would still need migration instructions, which I believe we can do using the old cvs-to-bzr instructions[3] as a base. As for location of the repository, we could have Mozilla host the official git repository and set up two-way mirroring to GitHub. How does this sound to everyone? Any strong objections? I and the rest of the BMO team are willing to do most of the work. Mark [1] https://launchpad.net/bzr-git [2] http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl [3] https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsbecker at nexbridge.com Mon Oct 21 16:30:43 2013 From: rsbecker at nexbridge.com (Randall S. Becker) Date: Mon, 21 Oct 2013 12:30:43 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <5265541E.8080405@mozilla.com> References: <5265541E.8080405@mozilla.com> Message-ID: <00ab01cece7a$e4026fe0$ac074fa0$@com> Hi Mark, If we have a mirror from Bazaar to CVS, we should be able to migrate to git and preserve history quite cleanly. I have used the cvs2git conversion successfully. It is non-destructive and should allow the procedure to be tested and verified prior to making the call to cut over. I am a big fan of git, and have a moderate amount of experience navigating its subtleties, so if you wish to contact me for assistance, don?t hesitate. Regards, Randall From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Mark C?t? Sent: October-21-13 12:20 PM To: developers at bugzilla.org Subject: Moving Bugzilla to git? Hi all, I'm the manager of Mozilla's Bugzilla team. We've talked about this idea before, but I thought I would flesh it out and ask for feedback. I think we should move the Bugzilla code off of the Bazaar system hosted by Mozilla and onto git, and maybe even GitHub. There are a few reasons for this: * git is pretty much the de facto standard for VCSs these days. This means many people are familiar with it and like its flexibility (I certainly do). * On the other side, Bazaar is almost dead. There are maybe 2-3 commits to trunk every month. * GitHub is extremely popular, and for good reason, since it's a very powerful system. Exposure via GitHub could mean increased contributions (whether we can keep up with them or not is, of course, another question. * Mozilla would very much like to retire Tinderbox, since Bugzilla is the only system still using it. Moving to GitHub means we could use travis-ci, which is really nice (we use it for other projects on my team). * Mozilla would also very much like to retire the Bazaar and CVS servers, both of which are used solely by Bugzilla. Doing a one-time migration is quite easy using fast-import/fast-export. I've verified that it works, with one small error that should be simple to fix (a single file not deleted in the git version). However, even with some advance warning, I don't think we can convert and then abandon Bazaar immediately due to Bugzilla's suggested upgrade path, which is to install a package and then pull updates directly from the Bazaar repository. If we had to do a security release, it doesn't seem right to require users to switch VCSs to get that fix. That said, I don't think we need to maintain Bazaar indefinitely, just for some grace period. I suggest 9 months, which would put that sometime mid-2014. I would, however, like to shut down CVS when we migrate to git, so that we don't have to maintain three VCSs at the same time. I haven't found a suitable solution to automatically mirror changes from git to Bazaar; there is one project[1] that at first glance appeared suitable, but after running into problems, I had a discussion with the package's author, who stated that there difficult bugs that would prevent it from working the way we would need it to. Luckily Bugzilla has already gone through this before, from CVS to Bazaar, and we have a script[2] that steps through Bazaar commits and applies them to a CVS repo. I've been modifying that script to do a similar git-to-bzr translation, and I'm confident I can get it working. The mirroring would be in a single direction, that is, from git to Bazaar; after the migration, Bazaar would be read only to everyone except the mirroring script. We would still need migration instructions, which I believe we can do using the old cvs-to-bzr instructions[3] as a base. As for location of the repository, we could have Mozilla host the official git repository and set up two-way mirroring to GitHub. How does this sound to everyone? Any strong objections? I and the rest of the BMO team are willing to do most of the work. Mark [1] https://launchpad.net/bzr-git [2] http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl [3] https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcote at mozilla.com Mon Oct 21 16:36:57 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 21 Oct 2013 12:36:57 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <00ab01cece7a$e4026fe0$ac074fa0$@com> References: <5265541E.8080405@mozilla.com> <00ab01cece7a$e4026fe0$ac074fa0$@com> Message-ID: <52655829.9060605@mozilla.com> The initial migration is fairly straightforward; bzr fast-export | git fast-import works very close to perfectly. I have to do a bit of tweaking to fix one tiny problem and to preserve Bazaar's bug ID metadata in the git commit messages, but that's not difficult. The more difficult part is keeping bzr in sync with git after the migration, but that should be possible with a custom script, most of which I have already written. Mark On 2013-10-21 12:30 PM, Randall S. Becker wrote: > > Hi Mark, > > > > If we have a mirror from Bazaar to CVS, we should be able to migrate > to git and preserve history quite cleanly. I have used the cvs2git > conversion successfully. It is non-destructive and should allow the > procedure to be tested and verified prior to making the call to cut > over. I am a big fan of git, and have a moderate amount of experience > navigating its subtleties, so if you wish to contact me for > assistance, don?t hesitate. > > > > Regards, > > Randall > > > > *From:*developers-owner at bugzilla.org > [mailto:developers-owner at bugzilla.org] *On Behalf Of *Mark C?t? > *Sent:* October-21-13 12:20 PM > *To:* developers at bugzilla.org > *Subject:* Moving Bugzilla to git? > > > > Hi all, I'm the manager of Mozilla's Bugzilla team. We've talked about > this idea before, but I thought I would flesh it out and ask for feedback. > > I think we should move the Bugzilla code off of the Bazaar system hosted > by Mozilla and onto git, and maybe even GitHub. There are a few reasons > for this: > > * git is pretty much the de facto standard for VCSs these days. This > means many people are familiar with it and like its flexibility (I > certainly do). > > * On the other side, Bazaar is almost dead. There are maybe 2-3 commits > to trunk every month. > > * GitHub is extremely popular, and for good reason, since it's a very > powerful system. Exposure via GitHub could mean increased contributions > (whether we can keep up with them or not is, of course, another question. > > * Mozilla would very much like to retire Tinderbox, since Bugzilla is > the only system still using it. Moving to GitHub means we could use > travis-ci, which is really nice (we use it for other projects on my team). > > * Mozilla would also very much like to retire the Bazaar and CVS servers, > both of which are used solely by Bugzilla. > > Doing a one-time migration is quite easy using fast-import/fast-export. > I've verified that it works, with one small error that should be simple > to fix (a single file not deleted in the git version). > > However, even with some advance warning, I don't think we can convert > and then abandon Bazaar immediately due to Bugzilla's suggested upgrade > path, which is to install a package and then pull updates directly from > the Bazaar repository. If we had to do a security release, it doesn't > seem right to require users to switch VCSs to get that fix. That said, I > don't think we need to maintain Bazaar indefinitely, just for some grace > period. I suggest 9 months, which would put that sometime mid-2014. I > would, however, like to shut down CVS when we migrate to git, > so that we don't have to maintain three VCSs at the same time. > > I haven't found a suitable solution to automatically mirror changes from > git to Bazaar; there is one project[1] that at first glance appeared > suitable, but after running into problems, I had a discussion with the > package's author, who stated that there difficult bugs that would > prevent it from working the way we would need it to. > > Luckily Bugzilla has already gone through this before, from CVS to > Bazaar, and we have a script[2] that steps through Bazaar commits and > applies them to a CVS repo. I've been modifying that script to do a > similar git-to-bzr translation, and I'm confident I can get it working. > The mirroring would be in a single direction, that is, from git to > Bazaar; after the migration, Bazaar would be read only to everyone > except the mirroring script. > > We would still need migration instructions, which I believe we can do > using the old cvs-to-bzr instructions[3] as a base. > > As for location of the repository, we could have Mozilla host the > official git repository and set up two-way mirroring to GitHub. > > How does this sound to everyone? Any strong objections? I and the rest > of the BMO team are willing to do most of the work. > > Mark > > > [1] https://launchpad.net/bzr-git > [2] http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl > [3] https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar > -------------- next part -------------- An HTML attachment was scrubbed... URL: From justdave at bugzilla.org Mon Oct 21 17:01:44 2013 From: justdave at bugzilla.org (Dave Miller) Date: Mon, 21 Oct 2013 13:01:44 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <5265541E.8080405@mozilla.com> References: <5265541E.8080405@mozilla.com> Message-ID: "Mark C?t?" wrote: >I think we should move the Bugzilla code off of the Bazaar system >hosted >by Mozilla and onto git, and maybe even GitHub. For the record, I support this plan. If for no other reason, because github has check-in monitoring tools very similar to bonsai, which is something bzr is still missing (loggerhead isn't quite there). >* On the other side, Bazaar is almost dead. There are maybe 2-3 commits >to trunk every month. This is a poor data point though. That could only mean it's stable. (Don't fix what isn't broken). A real qualifier here would be time-to-fix on important bugs. >* GitHub is extremely popular, and for good reason, since it's a very >powerful system. Exposure via GitHub could mean increased contributions >(whether we can keep up with them or not is, of course, another >question. I'm personally kind of ambivalent on whether to make github the master copy or git.mozilla.org, but if we use git.mozilla.org, we should definitely mirror it to github. >* Mozilla would very much like to retire Tinderbox, since Bugzilla is >the only system still using it. Not to mention it's full of security holes nobody wants to fix, which means we have to have it locked down where no one but the core contributors can access it, and it would be really nice to let anyone get to it again. >* Mozilla would also very much like to retire the Bazaar and CVS >servers, >both of which are used solely by Bugzilla. Not true in the case of CVS, but pretty close. There's one other project besides us still using it. >That said, I don't think we need to maintain Bazaar indefinitely, just for some >grace period. I suggest 9 months, which would put that sometime mid-2014. I >would, however, like to shut down CVS when we migrate to git, >so that we don't have to maintain three VCSs at the same time. The rule we stated before was that we would stop mirroring new branches to CVS and would stop supporting CVS altogether as soon as the last branch mirrored there was no longer supported. There is currently one branch left mirrored to CVS, so the next time we do a new branch release it goes bye bye, if we stick to that promise. Now... I'm not against forcing people to switch VCS systems to upgrade from a Bazaar release... moving from bzr to git is *considerably* easier than moving from CVS to bzr. I think a pre-defined grace period is a good compromise in this case. >As for location of the repository, we could have Mozilla host the >official git repository and set up two-way mirroring to GitHub. +1 >How does this sound to everyone? Any strong objections? I and the rest >of the BMO team are willing to do most of the work. I'm behind this if no one had strong objections. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. From dkl at mozilla.com Mon Oct 21 17:05:56 2013 From: dkl at mozilla.com (David Lawrence) Date: Mon, 21 Oct 2013 13:05:56 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <5265541E.8080405@mozilla.com> References: <5265541E.8080405@mozilla.com> Message-ID: <52655EF4.8030306@mozilla.com> +1 and not just because Mcote is my boss :) dkl On 10/21/2013 12:19 PM, Mark C?t? wrote: > Hi all, I'm the manager of Mozilla's Bugzilla team. We've talked about > this idea before, but I thought I would flesh it out and ask for feedback. > > I think we should move the Bugzilla code off of the Bazaar system hosted > by Mozilla and onto git, and maybe even GitHub. There are a few reasons > for this: > > * git is pretty much the de facto standard for VCSs these days. This > means many people are familiar with it and like its flexibility (I > certainly do). > > * On the other side, Bazaar is almost dead. There are maybe 2-3 commits > to trunk every month. > > * GitHub is extremely popular, and for good reason, since it's a very > powerful system. Exposure via GitHub could mean increased contributions > (whether we can keep up with them or not is, of course, another question. > > * Mozilla would very much like to retire Tinderbox, since Bugzilla is > the only system still using it. Moving to GitHub means we could use > travis-ci, which is really nice (we use it for other projects on my team). > > * Mozilla would also very much like to retire the Bazaar and CVS servers, > both of which are used solely by Bugzilla. > > Doing a one-time migration is quite easy using fast-import/fast-export. > I've verified that it works, with one small error that should be simple > to fix (a single file not deleted in the git version). > > However, even with some advance warning, I don't think we can convert > and then abandon Bazaar immediately due to Bugzilla's suggested upgrade > path, which is to install a package and then pull updates directly from > the Bazaar repository. If we had to do a security release, it doesn't > seem right to require users to switch VCSs to get that fix. That said, I > don't think we need to maintain Bazaar indefinitely, just for some grace > period. I suggest 9 months, which would put that sometime mid-2014. I > would, however, like to shut down CVS when we migrate to git, > so that we don't have to maintain three VCSs at the same time. > > I haven't found a suitable solution to automatically mirror changes from > git to Bazaar; there is one project[1] that at first glance appeared > suitable, but after running into problems, I had a discussion with the > package's author, who stated that there difficult bugs that would > prevent it from working the way we would need it to. > > Luckily Bugzilla has already gone through this before, from CVS to > Bazaar, and we have a script[2] that steps through Bazaar commits and > applies them to a CVS repo. I've been modifying that script to do a > similar git-to-bzr translation, and I'm confident I can get it working. > The mirroring would be in a single direction, that is, from git to > Bazaar; after the migration, Bazaar would be read only to everyone > except the mirroring script. > > We would still need migration instructions, which I believe we can do > using the old cvs-to-bzr instructions[3] as a base. > > As for location of the repository, we could have Mozilla host the > official git repository and set up two-way mirroring to GitHub. > > How does this sound to everyone? Any strong objections? I and the rest > of the BMO team are willing to do most of the work. > > Mark > > > [1] https://launchpad.net/bzr-git > [2] http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl > [3] https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar > -- David Lawrence dkl at mozilla.com From mcote at mozilla.com Mon Oct 21 17:08:40 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 21 Oct 2013 13:08:40 -0400 Subject: Moving Bugzilla to git? Message-ID: <0o-dnV5-gYoEwvjPnZ2dnUVZ_h-dnZ2d@mozilla.org> (Cross-posted to developers at bugzilla.org) Hi all, I'm the manager of Mozilla's Bugzilla team. We've talked about this idea before, but I thought I would flesh it out and ask for feedback. I think we should move the Bugzilla code off of the Bazaar system hosted by Mozilla and onto git, and maybe even GitHub. There are a few reasons for this: * git is pretty much the de facto standard for VCSs these days. This means many people are familiar with it and like its flexibility (I certainly do). * On the other side, Bazaar is almost dead. There are maybe 2-3 commits to trunk every month. * GitHub is extremely popular, and for good reason, since it's a very powerful system. Exposure via GitHub could mean increased contributions (whether we can keep up with them or not is, of course, another question. * Mozilla would very much like to retire Tinderbox, since Bugzilla is the only system still using it. Moving to GitHub means we could use travis-ci, which is really nice (we use it for other projects on my team). * Mozilla would also very much like to retire the Bazaar and CVS servers, both of which are used solely by Bugzilla. Doing a one-time migration is quite easy using fast-import/fast-export. I've verified that it works, with one small error that should be simple to fix (a single file not deleted in the git version). However, even with some advance warning, I don't think we can convert and then abandon Bazaar immediately due to Bugzilla's suggested upgrade path, which is to install a package and then pull updates directly from the Bazaar repository. If we had to do a security release, it doesn't seem right to require users to switch VCSs to get that fix. That said, I don't think we need to maintain Bazaar indefinitely, just for some grace period. I suggest 9 months, which would put that sometime mid-2014. I would, however, like to shut down CVS when we migrate to git, so that we don't have to maintain three VCSs at the same time. I haven't found a suitable solution to automatically mirror changes from git to Bazaar; there is one project[1] that at first glance appeared suitable, but after running into problems, I had a discussion with the package's author, who stated that there difficult bugs that would prevent it from working the way we would need it to. Luckily Bugzilla has already gone through this before, from CVS to Bazaar, and we have a script[2] that steps through Bazaar commits and applies them to a CVS repo. I've been modifying that script to do a similar git-to-bzr translation, and I'm confident I can get it working. The mirroring would be in a single direction, that is, from git to Bazaar; after the migration, Bazaar would be read only to everyone except the mirroring script. We would still need migration instructions, which I believe we can do using the old cvs-to-bzr instructions[3] as a base. As for location of the repository, we could have Mozilla host the official git repository and set up two-way mirroring to GitHub. How does this sound to everyone? Any strong objections? I and the rest of the BMO team are willing to do most of the work. Mark [1] https://launchpad.net/bzr-git [2] http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl [3] https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Mon Oct 21 17:29:31 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 21 Oct 2013 13:29:31 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <5265647B.6090100@mozilla.com> On 2013-10-21 1:01 PM, Dave Miller wrote: > > "Mark C?t?" wrote: > >> * On the other side, Bazaar is almost dead. There are maybe 2-3 commits >> to trunk every month. > This is a poor data point though. That could only mean it's stable. (Don't fix what isn't broken). A real qualifier here would be time-to-fix on important bugs. True. It appears that that metric is low as well. There was a big discussion on the Emacs developers' list about moving to git. The general consensus seems to have been that bug fixes in Bazaar take a very long time. Essentially RMS had get involved to get a bug that was very important to them fixed. > >> * Mozilla would also very much like to retire the Bazaar and CVS >> servers, >> both of which are used solely by Bugzilla. > Not true in the case of CVS, but pretty close. There's one other project besides us still using it. Ah, I stand corrected. > >> That said, I don't think we need to maintain Bazaar indefinitely, just for some >> grace period. I suggest 9 months, which would put that sometime mid-2014. I >> would, however, like to shut down CVS when we migrate to git, >> so that we don't have to maintain three VCSs at the same time. > The rule we stated before was that we would stop mirroring new branches to CVS and would stop supporting CVS altogether as soon as the last branch mirrored there was no longer supported. There is currently one branch left mirrored to CVS, so the next time we do a new branch release it goes bye bye, if we stick to that promise. Okay, good to know. Mark From andrey.vovk at gmail.com Mon Oct 21 20:25:53 2013 From: andrey.vovk at gmail.com (andrey.vovk at gmail.com) Date: Mon, 21 Oct 2013 13:25:53 -0700 (PDT) Subject: Wide character in syswrite at /usr/lib/perl5/5.8.8/Net/Cmd.pm line 436.pm In-Reply-To: References: Message-ID: <8c58303f-7684-4624-83bd-42cbff587653@googlegroups.com> Updating Net::Cmd to the latest version (1.21 in my case) resolved the problem. Regards -- Andrey _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From bugzilla at colinogilvie.co.uk Mon Oct 21 23:39:05 2013 From: bugzilla at colinogilvie.co.uk (Colin Ogilvie) Date: Tue, 22 Oct 2013 00:39:05 +0100 Subject: Moving Bugzilla to git? In-Reply-To: <5265541E.8080405@mozilla.com> References: <5265541E.8080405@mozilla.com> Message-ID: On 21 October 2013 17:19, Mark C?t? wrote: > How does this sound to everyone? Any strong objections? I and the rest > of the BMO team are willing to do most of the work. > > Git seems far more supported and easier to use than bzr, and being on github may, as you say, encourage contributors. I'd say go for it in my view... Cheers, Colin -- Colin Ogilvie There are 10 types of people in the world: those that understand binary and those that don't. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmarshal at yahoo-inc.com Mon Oct 21 23:55:59 2013 From: dmarshal at yahoo-inc.com (David Marshall) Date: Mon, 21 Oct 2013 23:55:59 +0000 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: On Oct 21, 2013, at 4:39 PM, Colin Ogilvie wrote: > On 21 October 2013 17:19, Mark C?t? wrote: > How does this sound to everyone? Any strong objections? I and the rest > of the BMO team are willing to do most of the work. > > > Git seems far more supported and easier to use than bzr, and being on github may, as you say, encourage contributors. > I recall that Max once gave me a lot of reasons why bzr was preferred to git. That was a long time ago, so some of his objections may have been mitigated. I wouldn't have thought that Mozilla had a github.com presence, but it does, so I recommend hosting directly on github.com. It would be probably be easier to manage pull requests there. FWIW, I think it is possible to configure launchpad.net to import from git directly, so folks would probably be able to pull bazaar updates from there. From mcote at mozilla.com Tue Oct 22 00:57:28 2013 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Mon, 21 Oct 2013 20:57:28 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <4086f110-e55f-4057-96e0-f405b23015ed@email.android.com> David Marshall wrote: > >On Oct 21, 2013, at 4:39 PM, Colin Ogilvie > > wrote: > >> On 21 October 2013 17:19, Mark C?t? wrote: >> How does this sound to everyone? Any strong objections? I and the >rest >> of the BMO team are willing to do most of the work. >> >> >> Git seems far more supported and easier to use than bzr, and being on >github may, as you say, encourage contributors. >> > >I recall that Max once gave me a lot of reasons why bzr was preferred >to git. That was a long time ago, so some of his objections may have >been mitigated. That was before my time, so I am unfamiliar with his reasons. I will, however, admit my reasons are more pragmatic than technical, though I do really like git's design, now that I've mostly wrapped my head around it. >I wouldn't have thought that Mozilla had a github.com presence, but it >does, so I recommend hosting directly on github.com. It would be >probably be easier to manage pull requests there. Indeed we do. I believe the larger projects are mirrored from our own git repo (so that is a solved problem for Bugzilla), but many are located primarily or solely on github. > >FWIW, I think it is possible to configure launchpad.net to import from >git directly, so folks would probably be able to pull bazaar updates >from there. That is very interesting. I'll check into that. Thanks, Mark From justdave at bugzilla.org Tue Oct 22 01:19:56 2013 From: justdave at bugzilla.org (Dave Miller) Date: Mon, 21 Oct 2013 21:19:56 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <5265D2BC.2070804@bugzilla.org> David Marshall wrote: > I recall that Max once gave me a lot of reasons why bzr was preferred > to git. That was a long time ago, so some of his objections may have > been mitigated. IIRC, git was brand spanking new at the time, and was basically considered by most people to just be one of Linus's toys. It wasn't considered a mature VCS at the time. It's come a LONG way since then. -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From gerv at mozilla.org Wed Oct 23 11:38:04 2013 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 23 Oct 2013 12:38:04 +0100 Subject: Moving Bugzilla to git? In-Reply-To: <0o-dnV5-gYoEwvjPnZ2dnUVZ_h-dnZ2d@mozilla.org> References: <0o-dnV5-gYoEwvjPnZ2dnUVZ_h-dnZ2d@mozilla.org> Message-ID: Hi Mark, I support this move, although I have some comments on making it work well. On 21/10/13 18:08, Mark C?t? wrote: > I think we should move the Bugzilla code off of the Bazaar system hosted > by Mozilla and onto git, and maybe even GitHub. I think we should master it (insofar as git has a master) on Mozilla's git server (assuming it's up by now?) and mirror to github. That gives better continuity in the face of problems on a service we don't control, but also the exposure that github brings. > However, even with some advance warning, I don't think we can convert > and then abandon Bazaar immediately due to Bugzilla's suggested upgrade > path, which is to install a package and then pull updates directly from > the Bazaar repository. If we had to do a security release, it doesn't > seem right to require users to switch VCSs to get that fix. That said, I > don't think we need to maintain Bazaar indefinitely, just for some grace > period. I suggest 9 months, which would put that sometime mid-2014. I > would, however, like to shut down CVS when we migrate to git, > so that we don't have to maintain three VCSs at the same time. Are you planning only to move trunk to github, or also a number of branches? What is the current status of the CVS mirror? My point is: if some old installations are still stuck on CVS, can we make it so they don't have to make _two_ VCS transitions to get to git? In other words, can we make the lowest-numbered branch available via Git be the same as the highest-numbered branch available via CVS? I can't work out what the highest-numbered branch available via CVS is; trunk has the version number 4.5.1+, which I assume is because there's some sort of mirroring going on. > We would still need migration instructions, which I believe we can do > using the old cvs-to-bzr instructions[3] as a base. Yes; I am very much in favour of the "change one thing at once" style of migration where the user moves VCS systems without making any other change, and only then performs some sort of upgrade. > As for location of the repository, we could have Mozilla host the > official git repository and set up two-way mirroring to GitHub. +1. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From denis.roy at eclipse.org Wed Oct 23 13:49:46 2013 From: denis.roy at eclipse.org (Denis Roy) Date: Wed, 23 Oct 2013 09:49:46 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <0o-dnV5-gYoEwvjPnZ2dnUVZ_h-dnZ2d@mozilla.org> Message-ID: <5267D3FA.4030807@eclipse.org> On 10/23/2013 07:38 AM, Gervase Markham wrote: > Hi Mark, > > I support this move, although I have some comments on making it work well. > > On 21/10/13 18:08, Mark C?t? wrote: >> I think we should move the Bugzilla code off of the Bazaar system hosted >> by Mozilla and onto git, and maybe even GitHub. > I think we should master it (insofar as git has a master) on Mozilla's > git server (assuming it's up by now?) and mirror to github. That gives > better continuity in the face of problems on a service we don't control, > but also the exposure that github brings. FWIW, at Eclipse we've tried mirroring a number of projects to Github, and we've found it to be generally broken and have since given up on Github mirrors. We host our Git code in-house as well, for the same reason you've mentioned. As a long-time bugzilla user & admin, I'm happy to see this discussion happening. Thanks to the team for all the great work. Denis From jitenagarwal19 at gmail.com Thu Oct 24 12:38:59 2013 From: jitenagarwal19 at gmail.com (jiten agarwal) Date: Thu, 24 Oct 2013 18:08:59 +0530 Subject: Self-Introduction: Jiten Message-ID: Hi, My name is Jiten Agarwal, I live in allahabad, India. I am a student at IIIT-A with IT branch. I am looking forward to help the bugzilla community and learn new things and help other members of community. I am good at java, c and c++ and i have worked on recommender system and made some games on java. I am very much excited to join the opensource world and looking forward for it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpsolit at gmail.com Thu Oct 24 20:09:25 2013 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 24 Oct 2013 22:09:25 +0200 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <52697E75.5010504@gmail.com> Le 22. 10. 13 01:55, David Marshall a ?crit : > I recall that Max once gave me a lot of reasons why bzr was preferred > to git. That was a long time ago, so some of his objections may have > been mitigated. For the record, here are the discussions about bzr vs Hg vs git: http://blog.gmane.org/gmane.comp.bug-tracking.bugzilla.devel/day=20090904 http://blog.gmane.org/gmane.comp.bug-tracking.bugzilla.devel/day=20081220 Do not forget to read comments posted the following days as there are much more replies than those displayed on a single page. About killing bzr in 9 months, I'm opposed to that. I'm not speaking as a former Bugzilla approver/core developer but as a Bugzilla installation maintainer (GCC Bugzilla). It's way too short, and it's a pain to move to another VCS when doing minor upgrades (i.e. on the same branch). Just for your information, we stopped using CVS and moved to bzr for GCC Bugzilla only *5 months* ago, see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52239. It wasn't because I didn't want to move to bzr earlier, but because I *technically* couldn't. Now the migration is done, GCC Bugzilla is running 4.4.1, and I don't expect to have to move to git to upgrade to another 4.4.x release. So we should stop running the bzr server only when the 4.4 branch reaches EOL, which means at the end of 2015 or 2016 at the earliest. Sorry if that seems too long for you. And about attracting more contributors thanks to a migration to git, I absolutely don't believe in this at all. I spent enough time on the Bugzilla project to know that it's irrelevant. What matters is the language used by Bugzilla, i.e. Perl, and developers coding in this language. LpSolit From denis.roy at eclipse.org Thu Oct 24 20:24:51 2013 From: denis.roy at eclipse.org (Denis Roy) Date: Thu, 24 Oct 2013 16:24:51 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <52697E75.5010504@gmail.com> References: <5265541E.8080405@mozilla.com> <52697E75.5010504@gmail.com> Message-ID: <52698213.3040707@eclipse.org> On 10/24/2013 04:09 PM, Fr?d?ric Buclin wrote: > And about attracting more contributors thanks to a migration to git, I > absolutely don't believe in this at all. I spent enough time on the > Bugzilla project to know that it's irrelevant. What matters is the > language used by Bugzilla, i.e. Perl, and developers coding in this > language. FWIW, when Bugzilla was on CVS I used to submit the occasional patch, but the switch to bzr killed me. Like you, I couldn't get bzr running and after trying exactly once, I gave up. I now upgrade Bugzilla using tarballs and patches. If I can fix small bugs fairly easily, I will, but I didn't feel like struggling with bzr. If Mozilla uses a code review system like Gerrit (I highly recommend it), it makes reviewing and accepting contributions a breeze. YMMV Denis From damien.nozay at gmail.com Fri Oct 25 02:08:08 2013 From: damien.nozay at gmail.com (Damien) Date: Thu, 24 Oct 2013 19:08:08 -0700 Subject: Moving Bugzilla to git? In-Reply-To: <52697E75.5010504@gmail.com> References: <5265541E.8080405@mozilla.com> <52697E75.5010504@gmail.com> Message-ID: > > And about attracting more contributors thanks to a migration to git, I > absolutely don't believe in this at all. I spent enough time on the > Bugzilla project to know that it's irrelevant. What matters is the > language used by Bugzilla, i.e. Perl, and developers coding in this > language. > Speaking for myself only, I would __strongly__ disagree that VCS is irrelevant. Be it gitorious or github, I like to be able to simply fork something, push, send a pull request. Some will think it is a "throwing garbage over the wall" mentality but hey that works for me... https://github.com/dnozay/bugzilla https://travis-ci.org/dnozay/bugzilla Actually I lie, I let Travis test my changes before I throw them over the wall. Contributing something to bzr goes like this: https://wiki.mozilla.org/Bugzilla:Developers <--- 11 steps! https://wiki.mozilla.org/Bugzilla:Committing_Patches <--- 11 steps! http://www.mozilla.org/hacking/committer/ <---- errrhhh. Language matters of course, but I don't want to use bzr. VCS matters too. I don't want to do anything with bzr; "my religion is against it". I believe if the tools are easy to use, people will use them. Contributing to git goes like this: 1. fork the repo. 2. make your changes. 3. push to your copy. 4. you think it's ready, send a pull request +1 for Gerrit suggestion for review process even though I'm not really a fan. - dnozay From timello at bugzilla.org Fri Oct 25 03:51:01 2013 From: timello at bugzilla.org (Tiago Mello) Date: Fri, 25 Oct 2013 01:51:01 -0200 Subject: Moving Bugzilla to git? In-Reply-To: <52697E75.5010504@gmail.com> References: <5265541E.8080405@mozilla.com> <52697E75.5010504@gmail.com> Message-ID: On Thu, Oct 24, 2013 at 6:09 PM, Fr?d?ric Buclin wrote: > > > And about attracting more contributors thanks to a migration to git, I > absolutely don't believe in this at all. I spent enough time on the > Bugzilla project to know that it's irrelevant. What matters is the > language used by Bugzilla, i.e. Perl, and developers coding in this > language. > > It's not irrelevant. Having a good infrastructure for development is key. A project isn't built only by its programming language. I +1 for git and github -- timello -------------- next part -------------- An HTML attachment was scrubbed... URL: From timello at gmail.com Fri Oct 25 03:36:06 2013 From: timello at gmail.com (Tiago Mello) Date: Fri, 25 Oct 2013 01:36:06 -0200 Subject: Moving Bugzilla to git? In-Reply-To: <52697E75.5010504@gmail.com> References: <5265541E.8080405@mozilla.com> <52697E75.5010504@gmail.com> Message-ID: Em 24/10/2013 18:10, "Fr?d?ric Buclin" escreveu: > > And about attracting more contributors thanks to a migration to git, I > absolutely don't believe in this at all. I spent enough time on the > Bugzilla project to know that it's irrelevant. What matters is the > language used by Bugzilla, i.e. Perl, and developers coding in this > language. It's not irrelevant. Having a good infrastructure for development is key. A project isn't built only by its programming language. I +1 for git and github -- timello -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdaugherty at gmail.com Fri Oct 25 07:38:03 2013 From: sdaugherty at gmail.com (Stephanie Daugherty) Date: Fri, 25 Oct 2013 03:38:03 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> <52697E75.5010504@gmail.com> Message-ID: +1 to github as well, mozilla already operates an organizational account ( https://github.com/mozilla) and github provides functionality to painlessly accept casual contributions, which IMHO are badly needed to revitalize the project. On Thu, Oct 24, 2013 at 11:36 PM, Tiago Mello wrote: > > Em 24/10/2013 18:10, "Fr?d?ric Buclin" escreveu: > > > > > And about attracting more contributors thanks to a migration to git, I > > absolutely don't believe in this at all. I spent enough time on the > > Bugzilla project to know that it's irrelevant. What matters is the > > language used by Bugzilla, i.e. Perl, and developers coding in this > > language. > It's not irrelevant. Having a good infrastructure for development is key. > A project isn't built only by its programming language. > > I +1 for git and github > > -- > timello > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Fri Oct 25 12:08:25 2013 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 25 Oct 2013 13:08:25 +0100 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: On 24/10/13 21:09, Fr?d?ric Buclin wrote: > for your information, we stopped using CVS and moved to bzr for GCC > Bugzilla only *5 months* ago, see > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52239. It wasn't because I > didn't want to move to bzr earlier, but because I *technically* > couldn't. Reading that bug, it looks like the issue was that the server couldn't run bzr because the Python version was too old. (There were also issues with upgrading Bugzilla, but those are separate - a VCS change should IMO be done between two copies of Bugzilla which are identical.) Do we know what dependencies git has, and whether it runs OK on older Linux distros? Can someone produce a statically-linked git binary that runs everywhere? > Now the migration is done, GCC Bugzilla is running 4.4.1, and > I don't expect to have to move to git to upgrade to another 4.4.x > release. I realise that moving to git is some work, but why do you link it to upgrading to another release? Using instructions like: https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar , you could move "sideways" to the same version but on git, in not too much time. Couldn't you? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From sdaugherty at gmail.com Fri Oct 25 12:32:11 2013 From: sdaugherty at gmail.com (Stephanie Daugherty) Date: Fri, 25 Oct 2013 08:32:11 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: Git should work well on older Linux distros, since that's where the toolchain originated and has been developed the longest. The official implementation is written in C, and is portable to Windows, Mac, Linux, and just about every other unix-like platform out there. It's generally installable from official packages or third party repositories even on older distros, so that shouldn't be much of a problem - any distro still recieving vendor support probably has git packages A statically linked binary is possible, but probably unnecessary for most users http://stackoverflow.com/questions/11570188/how-to-build-git-with-static-linking Further, bzr has plugins for mostly complete git interoperability: * http://doc.bazaar.canonical.com/migration/en/foreign/bzr-on-git-projects.html * On Fri, Oct 25, 2013 at 8:08 AM, Gervase Markham wrote: > On 24/10/13 21:09, Fr?d?ric Buclin wrote: > > for your information, we stopped using CVS and moved to bzr for GCC > > Bugzilla only *5 months* ago, see > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52239. It wasn't because I > > didn't want to move to bzr earlier, but because I *technically* > > couldn't. > > Reading that bug, it looks like the issue was that the server couldn't > run bzr because the Python version was too old. (There were also issues > with upgrading Bugzilla, but those are separate - a VCS change should > IMO be done between two copies of Bugzilla which are identical.) > > Do we know what dependencies git has, and whether it runs OK on older > Linux distros? Can someone produce a statically-linked git binary that > runs everywhere? > > > Now the migration is done, GCC Bugzilla is running 4.4.1, and > > I don't expect to have to move to git to upgrade to another 4.4.x > > release. > > I realise that moving to git is some work, but why do you link it to > upgrading to another release? Using instructions like: > https://wiki.mozilla.org/Bugzilla:Moving_From_CVS_To_Bazaar , you could > move "sideways" to the same version but on git, in not too much time. > Couldn't you? > > Gerv > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > > _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From denis.roy at eclipse.org Fri Oct 25 13:00:47 2013 From: denis.roy at eclipse.org (Denis Roy) Date: Fri, 25 Oct 2013 09:00:47 -0400 Subject: Bugzilla Development environment Message-ID: <526A6B7F.60200@eclipse.org> I'm just curious to know what the typical dev environment is for Bugzilla devs... What software and tools do you use? Apologies if this is listed somewhere. I checked https://wiki.mozilla.org/Bugzilla:Developers and couldn't find anything. Since Firefox now supports the Orion editor [1][2] and Orion supports Git & Github, you can see where I'm going with this... [1] https://bugzilla.mozilla.org/show_bug.cgi?id=660784 [2] http://eclipse.org/orion/ From lpsolit at gmail.com Fri Oct 25 14:12:05 2013 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Fri, 25 Oct 2013 16:12:05 +0200 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <526A7C35.1070001@gmail.com> Le 25. 10. 13 14:08, Gervase Markham a ?crit : > I realise that moving to git is some work, but why do you link it to > upgrading to another release? Because the problem to upgrade to 4.4 was that it was available on bzr only, while 4.0 was the last branch available on CVS. So let's say that 4.0.11 was only available on bzr for some reason, then I would have been unable to upgrade from 4.0.x to 4.0.y (y > x). If you decide to do that for e.g. Bugzilla 4.4 and for some reason git cannot be installed, then you would have the same problem, i.e. unable to upgrade from 4.4.x to 4.4.y. One could say I could use tarballs or diffs, but that's more work. LpSolit From sdaugherty at gmail.com Fri Oct 25 14:28:18 2013 From: sdaugherty at gmail.com (Stephanie Daugherty) Date: Fri, 25 Oct 2013 10:28:18 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <526A7C35.1070001@gmail.com> References: <5265541E.8080405@mozilla.com> <526A7C35.1070001@gmail.com> Message-ID: There seems to be sufficient bidirectional support between bzr and git to at least be able to maintain a workable mirror without the same level of overhead that continuing to support CVS requires.. On Fri, Oct 25, 2013 at 10:12 AM, Fr?d?ric Buclin wrote: > Le 25. 10. 13 14:08, Gervase Markham a ?crit : > > I realise that moving to git is some work, but why do you link it to > > upgrading to another release? > > Because the problem to upgrade to 4.4 was that it was available on bzr > only, while 4.0 was the last branch available on CVS. So let's say that > 4.0.11 was only available on bzr for some reason, then I would have been > unable to upgrade from 4.0.x to 4.0.y (y > x). If you decide to do that > for e.g. Bugzilla 4.4 and for some reason git cannot be installed, then > you would have the same problem, i.e. unable to upgrade from 4.4.x to > 4.4.y. One could say I could use tarballs or diffs, but that's more work. > > LpSolit > > - > To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cloos at jhcloos.com Fri Oct 25 19:51:36 2013 From: cloos at jhcloos.com (cloos at jhcloos.com) Date: Fri, 25 Oct 2013 19:51:36 +0000 Subject: Moving Bugzilla to git? References: <5265541E.8080405@mozilla.com> Message-ID: "Fr?d?ric Buclin" writes: > Because the problem to upgrade to 4.4 was that it was available on bzr > only, while 4.0 was the last branch available on CVS. With git and any of the web-based git portals (such as cgit, or sites like gitorious, github, bitbucket) one can always grab a given revision or tag in tar or zip format. So inaccessibility for those who do not or can not use git would not be a problem. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Oct 29 13:43:29 2013 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 29 Oct 2013 13:43:29 +0000 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: On 25/10/13 15:12, Fr?d?ric Buclin wrote: > Le 25. 10. 13 14:08, Gervase Markham a ?crit : >> I realise that moving to git is some work, but why do you link it to >> upgrading to another release? > > Because the problem to upgrade to 4.4 was that it was available on bzr > only, while 4.0 was the last branch available on CVS. So let's say that > 4.0.11 was only available on bzr for some reason, then I would have been > unable to upgrade from 4.0.x to 4.0.y (y > x). But you could upgrade from 4.0.x CVS to 4.0.x bzr, then upgrade to 4.0.y. > If you decide to do that > for e.g. Bugzilla 4.4 and for some reason git cannot be installed, then > you would have the same problem, i.e. unable to upgrade from 4.4.x to > 4.4.y. One could say I could use tarballs or diffs, but that's more work. It seems that the underlying problem with this scenario boils down to the "git cannot be installed" problem. As long as git can be installed on a server, then that server should have no problem with making this transition, even if they don't upgrade their Bugzilla at all during the process (and that would be the recommended way anyway). Stephanie's comments are helpful in determining whether we might have problems with people not being able to install git. It seems unlikely... Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Tue Oct 29 18:58:18 2013 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Tue, 29 Oct 2013 19:58:18 +0100 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <5270054A.7040907@gmail.com> Le 29. 10. 13 14:43, Gervase Markham a ?crit : > But you could upgrade from 4.0.x CVS to 4.0.x bzr, then upgrade to 4.0.y. No! As I said, it was not possible to install bzr on the server. > It seems that the underlying problem with this scenario boils down to > the "git cannot be installed" problem. As long as git can be installed > on a server, then that server should have no problem with making this > transition This clearly shows that you don't maintain any real Bugzilla installation. "Install git, move from bzr to git, then upgrade your Bugzilla to get security fixes" is extra work which not all admins are ready to do. This is maybe fine for developers, but certainly not for all admins. If you are happy with git, feel free to use it to maintain your Bugzilla installation, but this shouldn't affect installations already using bzr to get security fixes. LpSolit From gerv at mozilla.org Wed Oct 30 13:51:09 2013 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 30 Oct 2013 13:51:09 +0000 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <52710ECD.8080806@mozilla.org> On 29/10/13 18:58, Fr?d?ric Buclin wrote: > This clearly shows that you don't maintain any real Bugzilla > installation. Actually, I do. > "Install git, move from bzr to git, then upgrade your > Bugzilla to get security fixes" is extra work which not all admins are > ready to do. It would be wise for admins to do the "Install git, move from bzr to git" part before they needed to get a security fix... > This is maybe fine for developers, but certainly not for > all admins. If you are happy with git, feel free to use it to maintain > your Bugzilla installation, but this shouldn't affect installations > already using bzr to get security fixes. I guess this is one for justdave: "Is it reasonable to require Bugzilla administrators to switch SCM system on an occasion other than a release upgrade?" If the answer is yes, we can shut down bzr fairly soon. If the answer is no, we need to maintain it until all current branches are EOLed. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From shimono at gmail.com Wed Oct 30 14:15:35 2013 From: shimono at gmail.com (Atsushi Shimono) Date: Wed, 30 Oct 2013 23:15:35 +0900 Subject: -ja template (Re: [ANN] Release of Bugzilla 4.5.1, 4.4.1, 4.2.7, and 4.0.11) In-Reply-To: <525FFA9F.8000704@mozilla.com> References: <525FFA9F.8000704@mozilla.com> Message-ID: <52711487.6000102@gmail.com> hi, I've released -ja templates as follow.s http://bug-ja.org/releases/4.0/Bugzilla-ja-4.0.11-template.tar.bz2 http://bug-ja.org/releases/4.2/Bugzilla-ja-4.2.7-template.tar.bz2 http://bug-ja.org/releases/4.4/Bugzilla-ja-4.4.1-template.tar.bz2 http://bug-ja.org/releases/4.6/Bugzilla-ja-4.5.1-template.tar.bz2 (2013/10/17 23:56), David Lawrence wrote: > Today we are releasing 4.4.1, 4.2.7, 4.0.11, and the unstable > development snapshot 4.5.1. > > Initially, we released new tarballs and diffs for these releases > to the download site but found a new bug shortly after. New tarballs > and diffs have been uploaded to the site which we recommend everyone > update to if you downloaded the first version. To make sure you > have the fixed version, md5sum values are provided further down in > the announcement. > > All of today's releases contain security fixes. We recommend > all Bugzilla administrators to read the Security Advisory linked below. > > Bugzilla 4.4.1 is our latest stable release. It contains various > useful bug fixes, performance improvements and security fixes for > the 4.4 branch. > > Bugzilla 4.2.7 and 4.0.11 are security updates for the 4.2 > branch and the 4.0 branch, respectively. > > Note that 4.5.1 is an unstable development release and should not > be used in production environments. We are not yet feature-frozen at > this time so the features you see in 4.5.1 might not accurately > represent the behavior that 5.0 will have. > > Note that when Bugzilla 5.0 is released, the Bugzilla 4.0.x series > will reach end of life. If you are using that series, we encourage > you to upgrade to 4.4.1 now. > > > Download > -------- > Bugzilla is available at: > > http://www.bugzilla.org/download/ > > MD5SUMS > > 53d0bffc3055f7d5af1c754f177de4ad bugzilla-4.5.1.tar.gz > fd9d6dcc85bb359536be52e34ad20dfd bugzilla-4.4.1.tar.gz > ebf0a75d1037f09994660d3958fc66fb bugzilla-4.2.7.tar.gz > 48402a4a105de3f00962dca244cd7569 bugzilla-4.0.11.tar.gz > > > Security Advisory > ----------------- > There is a security advisory describing the security issues > fixed in these releases, at: > > http://www.bugzilla.org/security/4.0.10/ > > > Release Notes & Changes > ----------------------- > Before installing or upgrading, you should read the Release Notes for > the new version of Bugzilla: > > 4.4.1: http://www.bugzilla.org/releases/4.4.1/release-notes.html > 4.2.7: http://www.bugzilla.org/releases/4.2.7/release-notes.html > 4.0.11: http://www.bugzilla.org/releases/4.0.11/release-notes.html > > It is VERY IMPORTANT to read the Release Notes if you are > upgrading from one major version to another (like 3.6.x to 4.4.x). > > To see a list of all changes between your version of Bugzilla and > the current version of Bugzilla, you can use the chart at: > > http://www.bugzilla.org/status/changes.html > > > The Bugzilla Update > ------------------- > You can see the latest updates from the Bugzilla Project and > the status of Bugzilla development on The Bugzilla Update: > > http://bugzillaupdate.wordpress.com/ > > Also, you can follow the Bugzilla Project on Twitter for frequent > updates on new features being developed in Bugzilla, our current > release plans, and much more: > > http://twitter.com/#!/bugzilla > > > Report Bugs > ----------- > If you find a bug in Bugzilla, please report it! Instructions are > at this URL: > > http://www.bugzilla.org/developers/reporting_bugs.html > > > Support > ------- > You can ask questions for free on the mailing lists (or in IRC) > about Bugzilla, or you can hire a paid consultant to help you out: > > Free Support: http://www.bugzilla.org/support/ > Paid Support: http://www.bugzilla.org/support/consulting.html > > > About Bugzilla > -------------- > Bugzilla is a "Defect Tracking System" or "Bug-Tracking System." > Defect Tracking Systems allow individuals or groups of developers > to keep track of outstanding bugs in their product effectively. > Most commercial defect-tracking software vendors charge enormous > licensing fees. Despite being "free", Bugzilla has many features > its expensive counterparts lack. Consequently, Bugzilla has quickly > become a favorite of thousands of organizations across the globe, and > is widely regarded as one of the top defect-tracking systems available. > > See http://www.bugzilla.org/about/ for more details. > > - David Lawrence > Release Manager, Bugzilla Project > > _______________________________________________ > support-bugzilla mailing list > support-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/support-bugzilla > PLEASE put support-bugzilla at lists.mozilla.org in the To: field when you reply. > -- Atsushi Shimono - shimono at bug-ja.org - skype shimono_univ, twitter/FB: himorin Tel +81-50-5539-5179, +1-626-720-4274 / http://blog.himor.in/ Mozilla Evangelist; Mozilla Japanese Translation Group / Bugzilla UG in Japan HTML5-WEST.jp - Co-Founder of HTML5 Evangelism Group in west/Japan _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From sdaugherty at gmail.com Wed Oct 30 14:35:15 2013 From: sdaugherty at gmail.com (Stephanie Daugherty) Date: Wed, 30 Oct 2013 10:35:15 -0400 Subject: Moving Bugzilla to git? In-Reply-To: <52710ECD.8080806@mozilla.org> References: <5265541E.8080405@mozilla.com> <52710ECD.8080806@mozilla.org> Message-ID: The pain points of moving from cvs or svn to anything else largely don't exist for this conversion, because git, hg, and bzr are all at similar levels of functionality and interoperability to allow near interchangeability of tools, and common subsets of operations which can be performed across different repositories (push, pull, commit, merge, branch, tag, etc) using the cross-protocol support of each tool. (git can pretend a bzr repository is a git repository, bzr can pretent a git repository is a bzr repository, etc). My understanding is that the git-bzr integration is at a level sufficient to support a mirror suitable for nearly all upgrade/deployment scenarios, and the needs of many developers (history, tags and branches are 1:1 the same, submodules and certian metadata, like linkages to bug databases may not be). This support is also bidirectional, so it's technically possible to move in the other direction or even both directions at the same time, and to merge freely between the two systems, rather than being an all or nothing, one time conversion, This seems to be good enough that post-conversion, it would be possible to keep the bzr repositories up, while shifting development to git as of the time of transition, and continuing to mirror git to bzr without any technical limitations forcing an arbitrary cutoff point. On Wed, Oct 30, 2013 at 9:51 AM, Gervase Markham wrote: > On 29/10/13 18:58, Fr?d?ric Buclin wrote: > > This clearly shows that you don't maintain any real Bugzilla > > installation. > > Actually, I do. > > > "Install git, move from bzr to git, then upgrade your > > Bugzilla to get security fixes" is extra work which not all admins are > > ready to do. > > It would be wise for admins to do the "Install git, move from bzr to > git" part before they needed to get a security fix... > > > This is maybe fine for developers, but certainly not for > > all admins. If you are happy with git, feel free to use it to maintain > > your Bugzilla installation, but this shouldn't affect installations > > already using bzr to get security fixes. > > I guess this is one for justdave: > > "Is it reasonable to require Bugzilla administrators to switch SCM > system on an occasion other than a release upgrade?" > > If the answer is yes, we can shut down bzr fairly soon. If the answer is > no, we need to maintain it until all current branches are EOLed. > > Gerv > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > > _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From denis.roy at eclipse.org Wed Oct 30 16:52:49 2013 From: denis.roy at eclipse.org (Denis Roy) Date: Wed, 30 Oct 2013 17:52:49 +0100 Subject: Moving Bugzilla to git? In-Reply-To: <5270054A.7040907@gmail.com> References: <5265541E.8080405@mozilla.com> <5270054A.7040907@gmail.com> Message-ID: <52713961.1000501@eclipse.org> On 10/29/2013 07:58 PM, Fr?d?ric Buclin wrote: > This clearly shows that you don't maintain any real Bugzilla installation. I don't see how your statement is helpful. I maintain a real (big?) Bugzilla instance and I haven't upgraded BZ from any VCS in years. +1 to doing what it takes to enable and facilitate more code contributions to Bugzilla. From mcote at mozilla.com Wed Oct 30 17:05:04 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Wed, 30 Oct 2013 13:05:04 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> <52710ECD.8080806@mozilla.org> Message-ID: <52713C40.3020001@mozilla.com> I do not have the same understanding vis-?-vis bzr-git. I tried to use the bzr-git extension, and it failed when I tried to pull in changes from git. This was a git repo generated using a different tool, admittedly (bzr fast-export | git fast-import), but I exchanged some emails with bzr-git's author, Jelmer Vernooij, and he said that to keep an existing bzr branch in sync with a newly formed git repo is impossible at the moment: "This is essentially the 'roundtripping' support that we've been trying to achieve with bzr-git for a while. It's a nontrivial problem (since it requires all semantics from bzr to be preserved when pushing to git)." That said, as I mentioned before, it should be possible to create a script to apply diffs from git to bzr in a similar way that we do bzr-cvs mirroring right now. I have that script about half finished. So there is no technical problem in doing one-way mirroring, as far as I can tell. So to sum up this thread, I don't hear any opposition to making git the main VCS for Bugzilla and switching the existing Bazaar repo to read-only. The only point of contention appears to be how long we keep the Bazaar repos. This is partly a question for Mozilla's IT, since they are looking to retire older systems to remove some maintenance load. I don't think we need to solve it immediately, though. I will talk to the IT department about their plans. Also I want to reiterate that we do publish diffs with every release, so it's not like there is no way to get a security fix even if bzr is shut down and installing git is impossible, although pulling from bzr is of course more convenient. As for git versus GitHub, the standard practice at Mozilla is to have the primary repo exist on git.mozilla.org and create a one-way mirror to GitHub. This makes sense to me, since we will have more control over the repo. However, it also means that we wouldn't be able to merge pull requests from the GitHub UI, but since we'd keep using Bugzilla and its review tools, this doesn't really matter anyway. People can still fork the code and easily generate diffs for review. I will continue my work on the script and documentation. I've also started a wiki page (https://wiki.mozilla.org/Bugzilla:Migrating_to_git); I'll start filling it in with the results of this discussion and sketch out a plan. In the mean time, if you want to see the results of a migration, I just pushed a snapshot of Bugzilla trunk to my GitHub account: https://github.com/markrcote/bugzilla. I modified an existing translation script to paste the contents of the "bugs" commit property from Bazaar into the commit message, since git does not have commit properties. Mark On 10/30/2013, 10:35 AM, Stephanie Daugherty wrote: > The pain points of moving from cvs or svn to anything else largely don't > exist for this conversion, because git, hg, and bzr are all at similar > levels of functionality and interoperability to allow near > interchangeability of tools, and common subsets of operations which can be > performed across different repositories (push, pull, commit, merge, branch, > tag, etc) using the cross-protocol support of each tool. (git can pretend a > bzr repository is a git repository, bzr can pretent a git repository is a > bzr repository, etc). > > My understanding is that the git-bzr integration is at a level sufficient > to support a mirror suitable for nearly all upgrade/deployment scenarios, > and the needs of many developers (history, tags and branches are 1:1 the > same, submodules and certian metadata, like linkages to bug databases may > not be). This support is also bidirectional, so it's technically possible > to move in the other direction or even both directions at the same time, > and to merge freely between the two systems, rather than being an all or > nothing, one time conversion, > > This seems to be good enough that post-conversion, it would be possible to > keep the bzr repositories up, while shifting development to git as of the > time of transition, and continuing to mirror git to bzr without any > technical limitations forcing an arbitrary cutoff point. > > > > > On Wed, Oct 30, 2013 at 9:51 AM, Gervase Markham wrote: > >> On 29/10/13 18:58, Fr?d?ric Buclin wrote: >>> This clearly shows that you don't maintain any real Bugzilla >>> installation. >> Actually, I do. >> >>> "Install git, move from bzr to git, then upgrade your >>> Bugzilla to get security fixes" is extra work which not all admins are >>> ready to do. >> It would be wise for admins to do the "Install git, move from bzr to >> git" part before they needed to get a security fix... >> >>> This is maybe fine for developers, but certainly not for >>> all admins. If you are happy with git, feel free to use it to maintain >>> your Bugzilla installation, but this shouldn't affect installations >>> already using bzr to get security fixes. >> I guess this is one for justdave: >> >> "Is it reasonable to require Bugzilla administrators to switch SCM >> system on an occasion other than a release upgrade?" >> >> If the answer is yes, we can shut down bzr fairly soon. If the answer is >> no, we need to maintain it until all current branches are EOLed. >> >> Gerv >> _______________________________________________ >> dev-apps-bugzilla mailing list >> dev-apps-bugzilla at lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-apps-bugzilla >> - >> To view or change your list settings, click here: >> >> > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > From mcote at mozilla.com Wed Oct 30 17:20:18 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Wed, 30 Oct 2013 13:20:18 -0400 Subject: Moving Bugzilla to git? In-Reply-To: References: <0o-dnV5-gYoEwvjPnZ2dnUVZ_h-dnZ2d@mozilla.org> Message-ID: On 10/23/2013, 7:38 AM, Gervase Markham wrote: > Hi Mark, > > I support this move, although I have some comments on making it work well. Cool. Sorry for taking so long to respond here. :) > On 21/10/13 18:08, Mark C?t? wrote: >> I think we should move the Bugzilla code off of the Bazaar system hosted >> by Mozilla and onto git, and maybe even GitHub. > > I think we should master it (insofar as git has a master) on Mozilla's > git server (assuming it's up by now?) and mirror to github. That gives > better continuity in the face of problems on a service we don't control, > but also the exposure that github brings. Yup, agreed. As I mentioned in a previous email, it'll be a one-way mirror, but that's better than having nothing on GitHub. >> However, even with some advance warning, I don't think we can convert >> and then abandon Bazaar immediately due to Bugzilla's suggested upgrade >> path, which is to install a package and then pull updates directly from >> the Bazaar repository. If we had to do a security release, it doesn't >> seem right to require users to switch VCSs to get that fix. That said, I >> don't think we need to maintain Bazaar indefinitely, just for some grace >> period. I suggest 9 months, which would put that sometime mid-2014. I >> would, however, like to shut down CVS when we migrate to git, >> so that we don't have to maintain three VCSs at the same time. > > Are you planning only to move trunk to github, or also a number of branches? We might as well migrate everything, since some day the Bazaar server will go away, even if that turns out to be a couple years from now. > What is the current status of the CVS mirror? As far as I know, it is still up but read-only. > My point is: if some old installations are still stuck on CVS, can we > make it so they don't have to make _two_ VCS transitions to get to git? > In other words, can we make the lowest-numbered branch available via Git > be the same as the highest-numbered branch available via CVS? > > I can't work out what the highest-numbered branch available via CVS is; > trunk has the version number 4.5.1+, which I assume is because there's > some sort of mirroring going on. Yeah, for sure, assuming CVS is up to date with Bazaar there should be no problem here. I don't seem to have access to the CVS server right now, though, so I can't verify. Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From jochen.wiedmann at gmail.com Thu Oct 31 09:13:11 2013 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Thu, 31 Oct 2013 10:13:11 +0100 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: To me, the whole discussion boils down to "You need a VCS for getting security fixes." A quite unusual stance, I um unaware of *any* other project, which expects that. Question: Can we provide alternatives? On Tue, Oct 29, 2013 at 2:43 PM, Gervase Markham wrote: > On 25/10/13 15:12, Fr?d?ric Buclin wrote: > > Le 25. 10. 13 14:08, Gervase Markham a ?crit : > >> I realise that moving to git is some work, but why do you link it to > >> upgrading to another release? > > > > Because the problem to upgrade to 4.4 was that it was available on bzr > > only, while 4.0 was the last branch available on CVS. So let's say that > > 4.0.11 was only available on bzr for some reason, then I would have been > > unable to upgrade from 4.0.x to 4.0.y (y > x). > > But you could upgrade from 4.0.x CVS to 4.0.x bzr, then upgrade to 4.0.y. > > > If you decide to do that > > for e.g. Bugzilla 4.4 and for some reason git cannot be installed, then > > you would have the same problem, i.e. unable to upgrade from 4.4.x to > > 4.4.y. One could say I could use tarballs or diffs, but that's more work. > > It seems that the underlying problem with this scenario boils down to > the "git cannot be installed" problem. As long as git can be installed > on a server, then that server should have no problem with making this > transition, even if they don't upgrade their Bugzilla at all during the > process (and that would be the recommended way anyway). > > Stephanie's comments are helpful in determining whether we might have > problems with people not being able to install git. It seems unlikely... > > Gerv > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > > -- "That's what prayers are ... it's frightened people trying to make friends with the bully!" Terry Pratchett. The Last Hero -------------- next part -------------- An HTML attachment was scrubbed... URL: From glob at mozilla.com Thu Oct 31 14:21:25 2013 From: glob at mozilla.com (Byron Jones) Date: Thu, 31 Oct 2013 22:21:25 +0800 Subject: Moving Bugzilla to git? In-Reply-To: References: <5265541E.8080405@mozilla.com> Message-ID: <52726765.6050501@mozilla.com> Jochen Wiedmann wrote: > To me, the whole discussion boils down to "You need a VCS for getting > security fixes." > A quite unusual stance, I um unaware of *any* other project, which > expects that. Question: Can we provide alternatives? you do _not_ need a vcs to apply security fixes. you can download the diffs for each release and apply them. -- byron jones - :glob - bugzilla.mozilla.org team - -------------- next part -------------- An HTML attachment was scrubbed... URL: From wurblzap at gmail.com Wed Oct 30 16:02:20 2013 From: wurblzap at gmail.com (Marc Schumann) Date: Wed, 30 Oct 2013 17:02:20 +0100 Subject: -ja template (Re: [ANN] Release of Bugzilla 4.5.1, 4.4.1, 4.2.7, and 4.0.11) In-Reply-To: <52711487.6000102@gmail.com> References: <525FFA9F.8000704@mozilla.com> <52711487.6000102@gmail.com> Message-ID: Thanks! I updated the download page. 2013/10/30 Atsushi Shimono > hi, > > I've released -ja templates as follow.s > _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla