Bugzilla workflow customization update#
Bugzilla workflow customization full#
Bugzilla workflow customization software#

If you’re making a large change, make lots of small pull requests if possible (they can be on the same bug) as it makes it easier to review.

CyberShadow is a big help getting Harmony in shape to be run by itself.

Bugzilla workflow customization update#

J12:06 AM JBugzilla Update June 6 Project Meeting – new URLīelow are the minutes from today’s Bugzilla meeting along with a link to the video recording of the meeting. Watch for announcements on social media channels closer to that date whether it’ll happen then or not (it’s a US holiday)

Next meeting is scheduled for July 4th.

Dylan has Bugzilla mostly running in Mojolicious.

Contact Dave if you need something retrieved from it before July.

has been closed up – static page announcing that it’s closing will be in place until the end of July.Other possibilities are OSUOSL and Eclipse (Emmanual reminded us of their offer) The top condender for hosting right now is Linode.Bugzilla needs to exist as a separate legal entity from the Mozilla Foundation for purposes of contracting with a hosting company, so our current status is waiting on the legal work to get done to create a Bugzilla subsidiary of Mozilla Foundation.As noted at previous meetings Mozilla is downsizing and trying to find external hosting for the Bugzilla Project which they’ll still pay for, they just want to get out of the hosting bussiness.Short meeting this week because Dylan is traveling and either in an airport or on a plane right now.Other exciting developments include running as a standalone daemon with Mojolicious and the multitude of user experience enhancements by BugzillaUX in the pipeline make the future look bright!Īug12:12 AM JBugzilla Update Watch the June 6 Bugzilla Project Meeting After all, you need long-living bugs if you’re going to have a long-living bug system!Īnd that bug is finally about to get fixed.

I’m delighted to point out that one of these bugs is STILL open. I’m so very proud that it’s still going strong after these years.Ģ0 years ago from tomorrow (on August 27th, 1998) I filed several bugs against Bugzilla, known problems that I thought would want to get fixed.

Bugzilla workflow customization software#

20 years? Hardly any software lasts more than 5. I am in complete shock and awe that Bugzilla has lasted this long. Here’s a few words from the very first one: Over the last 20 years we’ve had about 300 contributors to the Bugzilla code.

Bugzilla workflow customization full#

Realistically we’re a few months away from having a full release though. Dylan has been making great progress with the recent merges from, though, and I’m hopeful that we’ll have something that people can at least try out in the really near future. I had really hoped to be announcing the release of Bugzilla 6 with this post, but we’re not quite there yet. The completion of the port to Perl was announced on September 15, 1998, and committed to CVS later that night.Ģ0 years later, Bugzilla is still alive and kicking, and about to get a major facelift that’s about 10 years overdue. Terry decided to port Bugzilla to Perl, with the hopes that more people would be able to contribute to it, since Perl seemed to be a more popular language. The initial installation of Bugzilla was deployed to the public on a server on April 6, 1998.Īfter a few months of testing and fixing on a public deployment, Bugzilla was finally released as open source via anonymous CVS and available for others to use on August 26, 1998. Bugzilla was originally written in TCL by Terry Weissman for use at to replace the in-house system then in use at Netscape. When first came online in 1998, one of the first products that was released was Bugzilla, a bug system implemented using freely available open source tools. The first two paragraphs lifted from our Bugzilla history: The open source release of Bugzilla turns 20 years old today!