2010/11/18 Stéphane Charette <stephanecharette@...>
> I'm in a bit of bind due to lots of travel recently, release deadlines at
> work, and some other stuff happening on the side that is taking up all that
> was left of my little free time. I need to shift a few things around.
> Things to note:
> 1) I haven't written a blog entry for 3.2.5. I need to get some Real Life
> (tm) work done and it already is past midnight, so I need to bail on the
> blog entry. Can someone write something up? Just so when people hit the
> web site they're not greeted with "Gramps 3.2.4!" but instead something
> about 3.2.5?
> 2) I apologize in advance if the NEWS file and the key highlights on the
> wiki + e-mail do not 100% accurately reflect what is in 3.2.5. It often is
> hard to go through the changelog file and pick out the relevant items that
> need to be highlighted, but tonight I had to rush through the process and I
> worry I may have missed something or misunderstood the importance of a fix.
> (Hint: Being an experienced developer myself, I don't need super-detailed
> descriptions, but on the other hand if your only commit comment is "fixed
> bug #1234" I don't normally take the time to look up the specifics of every
> checkin or bug number.)
> 3) Sorry I was not only a bit late in getting 3.2.5 out the door, but it
> turns out I first interpreted the request for a release around "11/12" as
> meaning December 11 versus November 12! Oops! At least we're all working
> with the same calendar in mind. :)
> As usual, and to repeat the release e-mail, special thanks to all
> contributors, translators, testers, users, and mailing list participants.
> Best regards,
> Stéphane Charette
The blog post is up now.
For all developers, when doing a fix, the bug number and the bug title
should be in the commit message. so something like ''fix #1234: bla bla bla"