From mkanat at bugzilla.org Sun Mar 4 19:10:30 2012 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 04 Mar 2012 11:10:30 -0800 Subject: Locking bugs temporarily? In-Reply-To: <4F4CC492.6010606@mozilla.org> References: <4F4CC492.6010606@mozilla.org> Message-ID: <4F53BE26.9020200@bugzilla.org> On 02/28/2012 04:12 AM, Gervase Markham wrote: > I could shrink the window still further by implementing some sort of > final-delta_ts_check-and-retry-if-its-changed logic, which I may end up > doing, but I was wondering if there was a good locking system I could > use to shut the window entirely. > > Given that the window inside Bugzilla isn't _totally_ shut, perhaps I'll > go with the above style solution. Yeah, I think in general you'll probably want to look at the sorts of solutions that distributed systems use to probabilistically avoid conflicts. -Max -- Max Kanat-Alexander Chief Architect, Community Lead, and Release Manager Bugzilla Project http://www.bugzilla.org/ From lpsolit at gmail.com Tue Mar 6 19:17:58 2012 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Tue, 06 Mar 2012 20:17:58 +0100 Subject: Using Text::Xslate as an alternative to Template::Toolkit? Message-ID: <4F5662E6.2070209@gmail.com> Hi all, I asked in the Template::Toolkit mailing-list how to make our templates faster. Besides telling me to use the TT cache, which we already do, and use PROCESS as much as possible instead of INCLUDE, which we already do, there were no really helpful solutions. But someone replied to me privately that there is one possible alternative to TT, which is the Text::Xslate module, available on CPAN: http://search.cpan.org/~gfuji/Text-Xslate/ This module has its own website, http://xslate.org/ which argues that Text::Xslate is 150 times faster than TT in persistent environment (for Bugzilla, this means when using mod_perl): http://xslate.org/benchmark.html In mod_cgi environment, this module is only 1.5 times faster than TT, based on their benchmarks. Of course, we don't want to rewrite all our templates, especially before knowing if it worths the effort, but the good news is that Text::Xslate supports most of the TT syntax and methods thanks to Text::Xslate::Syntax::TTerse and Text::Xslate::Bridge::TT2Like, see: http://search.cpan.org/~gfuji/Text-Xslate/lib/Text/Xslate/Syntax/TTerse.pm http://search.cpan.org/~dmaki/Text-Xslate-Bridge-TT2Like/lib/Text/Xslate/Bridge/TT2Like.pod The only drawback is that PROCESS and named BLOCK are not (yet) supported, which we use heavily. Let's hope that a future version of Text::Xslate will implement them. Does any of you have any experience with Text::Xslate, and know how mature and usable it is in real environments? And is the performance really as impressive as it seems to be in their benchmarks? Depending on how things go, we could propose it as an alternative to TT, e.g. through a parameter in localconfig. LpSolit From glob at mozilla.com Wed Mar 7 04:29:28 2012 From: glob at mozilla.com (Byron Jones) Date: Wed, 07 Mar 2012 12:29:28 +0800 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: <4F5662E6.2070209@gmail.com> References: <4F5662E6.2070209@gmail.com> Message-ID: <4F56E428.9060507@mozilla.com> Fr?d?ric Buclin wrote: > But someone replied to me privately that there is one possible > alternative to TT, which is the Text::Xslate module, available on CPAN: > > [...] > > In mod_cgi environment, this module is only 1.5 times faster than TT, > based on their benchmarks. for bugzilla with mod_cgi those gains will probably be lost by the overhead moose/mouse adds. for mod_perl, we don't currently cache anything between requests; it may be better to investigate retaining compiled templates across requests, as well as looking into a backend (backed by mod_perl or memcached) for caching generated html fragments between requests. -b -- byron - irc:glob - bugzilla.mozilla.org team - -------------- next part -------------- An HTML attachment was scrubbed... URL: From justdave at bugzilla.org Wed Mar 7 04:40:29 2012 From: justdave at bugzilla.org (David Miller) Date: Tue, 06 Mar 2012 23:40:29 -0500 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: <4F5662E6.2070209@gmail.com> References: <4F5662E6.2070209@gmail.com> Message-ID: <4F56E6BD.4070606@bugzilla.org> Fr?d?ric Buclin wrote on 3/6/12 2:17 PM: > Of course, we don't want to rewrite all our templates, especially before > knowing if it worths the effort, but the good news is that Text::Xslate > supports most of the TT syntax and methods thanks to > Text::Xslate::Syntax::TTerse and Text::Xslate::Bridge::TT2Like, see: And that then leads to the question: Does using the Template Toolkit compatibility modules negate the performance improvement? -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From lpsolit at gmail.com Wed Mar 7 19:23:41 2012 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Wed, 07 Mar 2012 20:23:41 +0100 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: <4F56E6BD.4070606@bugzilla.org> References: <4F5662E6.2070209@gmail.com> <4F56E6BD.4070606@bugzilla.org> Message-ID: <4F57B5BD.8010508@gmail.com> Le 07. 03. 12 05:40, David Miller a ?crit : > And that then leads to the question: Does using the Template Toolkit > compatibility modules negate the performance improvement? The templates are compiled by Text::Xslate, so the TT syntax is simply parsed into something Text::Xslate will understand. It doesn't depend on TT at all. So no performance penalty is expected. LpSolit From justdave at bugzilla.org Wed Mar 7 22:14:47 2012 From: justdave at bugzilla.org (David Miller) Date: Wed, 07 Mar 2012 17:14:47 -0500 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: <4F56E428.9060507@mozilla.com> References: <4F5662E6.2070209@gmail.com> <4F56E428.9060507@mozilla.com> Message-ID: <4F57DDD7.1000609@bugzilla.org> Byron Jones wrote on 3/6/12 11:29 PM: > Fr?d?ric Buclin wrote: >> But someone replied to me privately that there is one possible >> alternative to TT, which is the Text::Xslate module, available on CPAN: >> >> [...] >> >> In mod_cgi environment, this module is only 1.5 times faster than TT, >> based on their benchmarks. > for bugzilla with mod_cgi those gains will probably be lost by the > overhead moose/mouse adds. > > for mod_perl, we don't currently cache anything between requests; it may be better to investigate retaining compiled templates across requests, as well as looking into a backend (backed by mod_perl or memcached) for caching generated html fragments between requests. We do a lot of user-specific stuff... gotta wonder how much of the caching is negated by the amount of data we throw at the templates which changes for every user that looks at it... -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From dmarshal at yahoo-inc.com Wed Mar 7 22:43:28 2012 From: dmarshal at yahoo-inc.com (David Marshall) Date: Wed, 7 Mar 2012 14:43:28 -0800 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: <4F57DDD7.1000609@bugzilla.org> Message-ID: On 3/7/12 2:14 PM, "David Miller" wrote: > Byron Jones wrote on 3/6/12 11:29 PM: >> Fr?d?ric Buclin wrote: >>> But someone replied to me privately that there is one possible >>> alternative to TT, which is the Text::Xslate module, available on CPAN: >>> >>> [...] >>> >>> In mod_cgi environment, this module is only 1.5 times faster than TT, >>> based on their benchmarks. >> for bugzilla with mod_cgi those gains will probably be lost by the >> overhead moose/mouse adds. >> >> for mod_perl, we don't currently cache anything between requests; it may be >> better to investigate retaining compiled templates across requests, as well >> as looking into a backend (backed by mod_perl or memcached) for caching >> generated html fragments between requests. > > We do a lot of user-specific stuff... gotta wonder how much of the > caching is negated by the amount of data we throw at the templates which > changes for every user that looks at it... In our just-replaced version at Y! (a bastardized 2.22), we were using memcached for a number of things because of the scale involved. I'll be adding some of them back in as I observe what's going on with our shiny new 3.6. Our bugs table changes very frequently, so one thing we did was to add SQL_NO_CACHE to all of the queries that involved table bugs. We did want to use the query cache for most of the other tables, so we didn't want to disable query caching altogether. That's a very marginal performance improvement, but it's non-zero. We were using memcached to cache the rows from longdescs for a bug, keyed by bugs.delta_ts. I don't recall any specific performance metrics, but our hit rate was fairly good. I've thought about caching all of the HTML for show_bug.cgi (again based on bugs.delta_ts), but we put a "readable time" on bugs (i.e. "6 days ago"). One way to get around this would be to generate the HTML with tags that either are replaced before being sent to the browser or that are computed client-side. It should be noted that we currently don't employ any particular group security, so everyone basically gets the same page. From glob at mozilla.com Thu Mar 8 08:09:32 2012 From: glob at mozilla.com (Byron Jones) Date: Thu, 08 Mar 2012 16:09:32 +0800 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: <4F57DDD7.1000609@bugzilla.org> References: <4F5662E6.2070209@gmail.com> <4F56E428.9060507@mozilla.com> <4F57DDD7.1000609@bugzilla.org> Message-ID: <4F58693C.2080008@mozilla.com> David Miller wrote: > Byron Jones wrote on 3/6/12 11:29 PM: >> for mod_perl, we don't currently cache anything between requests; it may be better to investigate retaining compiled templates across requests, as well as looking into a backend (backed by mod_perl or memcached) for caching generated html fragments between requests. > We do a lot of user-specific stuff... gotta wonder how much of the > caching is negated by the amount of data we throw at the templates which > changes for every user that looks at it... we'd cache fragments of html, not the entire page. for example, comments are immutable, so if we were to store the html-ised form in memcache, we could avoid a db lookup, linkification, and template rendering. -- byron - irc:glob - bugzilla.mozilla.org team - -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkanat at bugzilla.org Mon Mar 12 06:55:06 2012 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 11 Mar 2012 23:55:06 -0700 Subject: Using Text::Xslate as an alternative to Template::Toolkit? In-Reply-To: References: Message-ID: <4F5D9DCA.3070806@bugzilla.org> On 03/07/2012 02:43 PM, David Marshall wrote: > I've thought about caching all of the HTML for show_bug.cgi (again based on > bugs.delta_ts), but we put a "readable time" on bugs (i.e. "6 days ago"). It's actually much more complex than that, too. See this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=594962 -Max -- Max Kanat-Alexander Chief Architect, Community Lead, and Release Manager Bugzilla Project http://www.bugzilla.org/ From raghukumar.c at tavant.com Wed Mar 14 06:21:11 2012 From: raghukumar.c at tavant.com (Raghu Kumar C) Date: Wed, 14 Mar 2012 06:21:11 +0000 Subject: No subject Message-ID: Hello, Can someone confirm that collectstats.pl is enabled(cron) on landfill bugzilla installations? I tried using it on the 3.6 branch, however I couldn't see anything. No error was thrown. Regards, Raghu Any comments or statements made in this email are not necessarily those of Tavant Technologies. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Tavant Technologies may be subject to our monitoring procedures. From gerv at mozilla.org Wed Mar 14 11:04:24 2012 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 14 Mar 2012 11:04:24 +0000 Subject: No subject In-Reply-To: References: Message-ID: On 14/03/12 06:21, Raghu Kumar C wrote: > Can someone confirm that collectstats.pl is enabled(cron) on landfill > bugzilla installations? I tried using it on the 3.6 branch, however I > couldn't see anything. No error was thrown. [gerv at landfill bugzilla-3.6-branch]$ ls data/mining/ [gerv at landfill bugzilla-3.6-branch] It appears not to be enabled. It is for some installs, e.g. bugzilla-tip, but not all. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From raghukumar.c at tavant.com Wed Mar 14 13:56:11 2012 From: raghukumar.c at tavant.com (Raghu Kumar C) Date: Wed, 14 Mar 2012 13:56:11 +0000 Subject: No subject In-Reply-To: References: Message-ID: Thank you, Gerv. I will check that out. ~raghu -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Gervase Markham Sent: 14 March 2012 16:34 To: dev-apps-bugzilla at lists.mozilla.org Subject: Re: On 14/03/12 06:21, Raghu Kumar C wrote: > Can someone confirm that collectstats.pl is enabled(cron) on landfill > bugzilla installations? I tried using it on the 3.6 branch, however I > couldn't see anything. No error was thrown. [gerv at landfill bugzilla-3.6-branch]$ ls data/mining/ [gerv at landfill bugzilla-3.6-branch] It appears not to be enabled. It is for some installs, e.g. bugzilla-tip, but not all. 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: Any comments or statements made in this email are not necessarily those of Tavant Technologies. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Tavant Technologies may be subject to our monitoring procedures. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mkanat at bugzilla.org Wed Mar 28 19:05:43 2012 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 28 Mar 2012 12:05:43 -0700 Subject: I wrote a book. Message-ID: <4F736107.5020908@bugzilla.org> Hey Bugzilla developers. You may have noticed that I haven't been around quite as much as I used to be. Well, it's true that part of that is because I got this great job at Google which I really love, and I've been working a lot there. But also, I've been spending a lot of my time *not* at work on something completely different: I wrote a book. During my years on the Bugzilla Project, many (or perhaps all) of you may have noticed that I'm very intense when it comes to code quality--I really care a lot about the architecture of a system, and I have some pretty strong ideas about code complexity. I've spent perhaps more time refactoring Bugzilla (and helping others refactor) than any other work I've done on it. Well, for many of the years I was doing this, what I was also doing was testing and refining a series of principles about software development as a whole. I could try out an idea, apply it to the Bugzilla codebase, and see how things went over time in an actual software project that was broadly-used but needed a lot of code improvements. I learned what works and what doesn't. Then I took these ideas out for broader testing in numerous ways, and what I eventually came up with was a series of laws for software development. I compiled these laws and a series of other software development guidelines into a book that I called "Code Simplicity: The Science of Software Development." One of the hardest parts was finding a simple logical sequence to explain everything in, simplifying all the information so that it could be understood easily, and determining the exact phrasing for each piece of critical text in the book. All told, that process took almost three years. Then I looked around and wondered, "Has anybody written this book already?" After all, had there been some other work in the field that was equivalent, I would have just gotten behind that and promoted it, instead. But much to my surprise, nothing equivalent already existed. There are some books that give some good tips on development or about specific languages, but *nothing* that covered the basic principles of software development as a whole. Then, last Fall, we shopped the book around to various publishers, and much to my excitement, O'Reilly said that they were highly interested and would love to publish my book. Several months later, and here we are--the book has been published and is available for all e-readers and in print form from most major online book retailers. In fact, if you want to get it, it's on sale until April 4 at oreilly.com for 50% off, which is a hugely good deal: http://shop.oreilly.com/product/0636920022251.do So why am I writing to the Bugzilla developers about this? Well, first, because I want to thank you. In fact, you're one of the few groups of people explicitly thanked in the Acknowledgments section of the book, because your contributions to Bugzilla and your discussions with me over the years really helped me shape the content of first my blog and then the book as it is today. But also, I wrote the book because I wanted to be able to pass on a series of principles, the ideas that I was operating off of when I was helping to improve the quality of the Bugzilla codebase. I want to see these sorts of improvements happen everywhere and have them be driven by everybody. I want to give back to the Bugzilla community as a whole, not just with short snippets of emails, a few Wiki pages here and there, or some blog posts, but with complete work of all the fundamental ideas. So here you have it. If I had numerous free copies, I would actually send one to many of you. But I don't, and so the best that I can do is to let you guys know about the existence of the book while it's on sale at such a hugely good price. It is my dear hope that it helps you in some way not just as individual programmers, but as the Bugzilla community as a whole. -Max -- Max Kanat-Alexander Chief Architect, Community Lead, and Release Manager Bugzilla Project http://www.bugzilla.org/ From lpsolit at gmail.com Thu Mar 29 21:21:21 2012 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 29 Mar 2012 23:21:21 +0200 Subject: Bugzilla 4.5 will require Perl 5.10.1 Message-ID: <4F74D251.6040209@gmail.com> Hi all, This is just a quick note to let you know that once we branch for Bugzilla 4.4 in May, I will commit a patch which will make Bugzilla 4.5 and newer to require Perl 5.10.1 as a minimum. This means Bugzilla won't support Perl 5.8.x anymore. So Bugzilla 4.4 will be the last release to support the oldish Perl 5.8.x. This new requirement is tracked in bug 655477: https://bugzilla.mozilla.org/show_bug.cgi?id=655477 LpSolit From ahdevans at gmail.com Thu Mar 29 21:51:05 2012 From: ahdevans at gmail.com (Aaron Evans) Date: Thu, 29 Mar 2012 16:51:05 -0500 Subject: I wrote a book. In-Reply-To: <4F736107.5020908@bugzilla.org> References: <4F736107.5020908@bugzilla.org> Message-ID: <4F74D949.5050709@gmail.com> Awesome Max! I loved reading your blog posts on the Code Simplicity and appreciate your leadership on Bugzilla. I ordered mine. -Aaron @fijiaaron On 3/28/2012 2:05 PM, Max Kanat-Alexander wrote: > Hey Bugzilla developers. You may have noticed that I haven't been > around quite as much as I used to be. Well, it's true that part of that > is because I got this great job at Google which I really love, and I've > been working a lot there. But also, I've been spending a lot of my time > *not* at work on something completely different: I wrote a book. > > During my years on the Bugzilla Project, many (or perhaps all) of you > may have noticed that I'm very intense when it comes to code quality--I > really care a lot about the architecture of a system, and I have some > pretty strong ideas about code complexity. I've spent perhaps more time > refactoring Bugzilla (and helping others refactor) than any other work > I've done on it. Well, for many of the years I was doing this, what I > was also doing was testing and refining a series of principles about > software development as a whole. I could try out an idea, apply it to > the Bugzilla codebase, and see how things went over time in an actual > software project that was broadly-used but needed a lot of code > improvements. I learned what works and what doesn't. Then I took these > ideas out for broader testing in numerous ways, and what I eventually > came up with was a series of laws for software development. > > I compiled these laws and a series of other software development > guidelines into a book that I called "Code Simplicity: The Science of > Software Development." One of the hardest parts was finding a simple > logical sequence to explain everything in, simplifying all the > information so that it could be understood easily, and determining the > exact phrasing for each piece of critical text in the book. All told, > that process took almost three years. > > Then I looked around and wondered, "Has anybody written this book > already?" After all, had there been some other work in the field that > was equivalent, I would have just gotten behind that and promoted it, > instead. But much to my surprise, nothing equivalent already existed. > There are some books that give some good tips on development or about > specific languages, but *nothing* that covered the basic principles of > software development as a whole. > > Then, last Fall, we shopped the book around to various publishers, and > much to my excitement, O'Reilly said that they were highly interested > and would love to publish my book. Several months later, and here we > are--the book has been published and is available for all e-readers and > in print form from most major online book retailers. In fact, if you > want to get it, it's on sale until April 4 at oreilly.com for 50% off, > which is a hugely good deal: > > http://shop.oreilly.com/product/0636920022251.do > > So why am I writing to the Bugzilla developers about this? Well, first, > because I want to thank you. In fact, you're one of the few groups of > people explicitly thanked in the Acknowledgments section of the book, > because your contributions to Bugzilla and your discussions with me over > the years really helped me shape the content of first my blog and then > the book as it is today. But also, I wrote the book because I wanted to > be able to pass on a series of principles, the ideas that I was > operating off of when I was helping to improve the quality of the > Bugzilla codebase. I want to see these sorts of improvements happen > everywhere and have them be driven by everybody. I want to give back to > the Bugzilla community as a whole, not just with short snippets of > emails, a few Wiki pages here and there, or some blog posts, but with > complete work of all the fundamental ideas. > > So here you have it. If I had numerous free copies, I would actually > send one to many of you. But I don't, and so the best that I can do is > to let you guys know about the existence of the book while it's on sale > at such a hugely good price. It is my dear hope that it helps you in > some way not just as individual programmers, but as the Bugzilla > community as a whole. > > -Max From mkanat at bugzilla.org Fri Mar 30 05:29:23 2012 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 29 Mar 2012 22:29:23 -0700 Subject: I wrote a book. In-Reply-To: <4F74D949.5050709@gmail.com> References: <4F736107.5020908@bugzilla.org> <4F74D949.5050709@gmail.com> Message-ID: <4F7544B3.3090105@bugzilla.org> Thanks! :-D -Max On 03/29/2012 02:51 PM, Aaron Evans wrote: > Awesome Max! > I loved reading your blog posts on the Code Simplicity and appreciate > your leadership on Bugzilla. > I ordered mine. > > -Aaron > @fijiaaron > > On 3/28/2012 2:05 PM, Max Kanat-Alexander wrote: >> Hey Bugzilla developers. You may have noticed that I haven't been >> around quite as much as I used to be. Well, it's true that part of that >> is because I got this great job at Google which I really love, and I've >> been working a lot there. But also, I've been spending a lot of my time >> *not* at work on something completely different: I wrote a book. >> >> During my years on the Bugzilla Project, many (or perhaps all) of you >> may have noticed that I'm very intense when it comes to code quality--I >> really care a lot about the architecture of a system, and I have some >> pretty strong ideas about code complexity. I've spent perhaps more time >> refactoring Bugzilla (and helping others refactor) than any other work >> I've done on it. Well, for many of the years I was doing this, what I >> was also doing was testing and refining a series of principles about >> software development as a whole. I could try out an idea, apply it to >> the Bugzilla codebase, and see how things went over time in an actual >> software project that was broadly-used but needed a lot of code >> improvements. I learned what works and what doesn't. Then I took these >> ideas out for broader testing in numerous ways, and what I eventually >> came up with was a series of laws for software development. >> >> I compiled these laws and a series of other software development >> guidelines into a book that I called "Code Simplicity: The Science of >> Software Development." One of the hardest parts was finding a simple >> logical sequence to explain everything in, simplifying all the >> information so that it could be understood easily, and determining the >> exact phrasing for each piece of critical text in the book. All told, >> that process took almost three years. >> >> Then I looked around and wondered, "Has anybody written this book >> already?" After all, had there been some other work in the field that >> was equivalent, I would have just gotten behind that and promoted it, >> instead. But much to my surprise, nothing equivalent already existed. >> There are some books that give some good tips on development or about >> specific languages, but *nothing* that covered the basic principles of >> software development as a whole. >> >> Then, last Fall, we shopped the book around to various publishers, >> and >> much to my excitement, O'Reilly said that they were highly interested >> and would love to publish my book. Several months later, and here we >> are--the book has been published and is available for all e-readers and >> in print form from most major online book retailers. In fact, if you >> want to get it, it's on sale until April 4 at oreilly.com for 50% off, >> which is a hugely good deal: >> >> http://shop.oreilly.com/product/0636920022251.do >> >> So why am I writing to the Bugzilla developers about this? Well, >> first, >> because I want to thank you. In fact, you're one of the few groups of >> people explicitly thanked in the Acknowledgments section of the book, >> because your contributions to Bugzilla and your discussions with me over >> the years really helped me shape the content of first my blog and then >> the book as it is today. But also, I wrote the book because I wanted to >> be able to pass on a series of principles, the ideas that I was >> operating off of when I was helping to improve the quality of the >> Bugzilla codebase. I want to see these sorts of improvements happen >> everywhere and have them be driven by everybody. I want to give back to >> the Bugzilla community as a whole, not just with short snippets of >> emails, a few Wiki pages here and there, or some blog posts, but with >> complete work of all the fundamental ideas. >> >> So here you have it. If I had numerous free copies, I would actually >> send one to many of you. But I don't, and so the best that I can do is >> to let you guys know about the existence of the book while it's on sale >> at such a hugely good price. It is my dear hope that it helps you in >> some way not just as individual programmers, but as the Bugzilla >> community as a whole. >> >> -Max > > - > To view or change your list settings, click here: > -- Max Kanat-Alexander Chief Architect, Community Lead, and Release Manager Bugzilla Project http://www.bugzilla.org/