Hi Dierks! On Wed, Nov 16, 2011 at 12:39 AM, BJ Dierkes <[email protected]> wrote: > I just wanted to comment on this release. Please let me know if I'm just way > out of left field or what have you as I've been absent the last few months > and am just now trying to get back on top of the RPM builds. >
That is much appreciated, let us know when you have something we can test! (...and put in the manual.) > This blog entry mentions a number of changes, however the release in > LaunchPad has zero references to bugs/blueprints/etc. I'm curious, are we > moving away from managing releases in LaunchPad, or is this simply due to a > lack of having a 'project manager' to triage bugs, and ensure they are linked > to releases, included in milestones, etc? On that same note… I've seen a few > bugs here and there that I think have already been fixed but have had no > comments and are still left open. > Usually the information in the release blog post has been copied also to the launchpad page. In this case that just wasn't done. However, as far as I can see we do not follow a practice of mapping bugs to any particular release. This is probably partially due to there not being a person who would spend a lot of time triaging and managing the bugs. For instance I have fixed several bugs that I never reported in Launchpad at all, I just created a patch and called the branch "drizzle-fix-blablabla" and of course write something meaninful in the commit message. Similarly someone may post a bug and someone else might independently fix that bug without knowing that such a bug is open in lp. > I'm not trying to give anyone a hard time, just something I've noticed am > interested to hear feedback on. My primary concern is, in the packaging > world (Fedora/EPEL/Etc) we often link to the upstream vendors release notes > when upgrading the actual source version. When a new release is out, with no > links to bugs/blueprints/etc it can be a bit disconcerting for users > upgrading. > In this case the blog post is the release note, in previous releases there have been a few lines in LP. Unfortunately there is not a bug-by-bug record maintained with each release. That information could mostly be digged out of the commit log, but at the moment nobody is doing that. (Volunteer, as always, are of course welcome...) As you can see, even responding to email can take days, but we try to answer most of them if given enough time. What was not written anywhere yet is a "release note -like" description of the major differences with any of the Drizzle 7.1 releases compared to 7.0. henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
