Okay, here's the Status Update. justdave--any thoughts? Want to write a Dave's Corner?

Comment on attachment 240966 [details] v1 ><p>Bugzilla development has been <em>extremely</em> active lately, and we're > happy that we're receiving so many contributions. As usual, though, we need > more reviewers! To become a reviewer, you first have to be a consistent > contributor, and then we have to trust your judgement. You can see more > details at the > <a href="http://www.bugzilla.org/docs/reviewer-list.html#become">List of > Reviewers</a>.</p> I don't like this section about reviewers. I don't think such stuff should be in this document. ><p>As usual, we'd like to remind all Bugzilla administrators that to assist > them in keeping up-to-date with release announcements and security > advisories, we provide an ultra-low-volume administrator mailing list Also, those already using Bugzilla 2.23.2 can be notified by Bugzilla directly thanks to the upgrade_notification parameter.

> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=mod_perl">tracking > bug</a> and its > <a >href="https://bugzilla.mozilla.org/showdependencytree.cgi?id=87406&hide_resolved=1">dependency why use id=mod_perl && id=mod_perl ? note that these cause error if new repos become live before release: > INCLUDE "inc/header.html.tmpl" >[% INCLUDE "inc/footer.html.tmpl" %]

Comment on attachment 240966 [details] v1 > <li>2.23.3 is one of our most important development releases ever, containing > the two &quot;holy grails&quot; of Bugzilla development, custom fields > and mod_perl support. (Of course, the release is only a development > snapshot, so don't use it in production! It hasn't received the same > level of QA as the other releases!)</li> I love the "holy grail" comment. ;) > <li>You can now disable Bugzilla's sending of email to a particular > user.</li> Couldn't we already do this? You mean there's a UI for it now? (you used to have to edit the data/nomail file by hand) > <li>When you build the documentation, the Bugzilla POD documentation > will be available as <kbd>docs/html/api/</kbd> in your installation.</li> An HTML version of the POD documentation? Should we <abrev title=""> on POD to explain what it is? > <li><kbd>UserInGroup</kbd> has been removed. You should use > <kbd>Bugzilla-&gt;user&gt;in_group</kbd> instead.</li> This needs a hyphen after user... right now this looks like Bugzilla->user>in_group ><h2>Upcoming EOL for Bugzilla 2.18</h2> > ><p>Users of Bugzilla 2.18 should be aware that it will reach End-Of-Life > with the final release of Bugzilla 3.0. Once Bugzilla 3.0 is released, > no new patches will be released for Bugzilla 2.18, even for security > issues.</p> > ><p>We recommend that all Bugzilla 2.18 users upgrade to 2.22.1 at their > earliest convenience.</p> Should we say 2.22.1 (or 3.0 when it comes out) ? ><h2>Bugzilla Meetings</h2> > ><p>Come to our <a href="http://wiki.mozilla.org/Bugzilla:Meetings">meetings</a> >every other week! Anybody is welcome to attend who is interested in helping >out with the Bugzilla Project, or just anybody who wants to put in their >two cents on how development should go.</p> > ><p>You can learn more about the meetings at the > <a href="http://wiki.mozilla.org/Bugzilla:Meetings">wiki page about > Bugzilla Meetings</a>.</p> This last paragraph just sounds funny to me. Not sure why. The sole purpose of this paragraph seems to be to point out the wiki page, and we already linked to it in the previous paragraph, so is this last paragraph even necessary?

Okay, I fixed all of justdave's and Maki's comments, and set the update on the staging site. I left the last paragraph--it's there because you can't see the source code. People might not realize that "meetings" is a link to info about the meetings, but they'll definitely recognize the other link.