Hello Liam, It is never too early to create a Launchpad bug. That said, we generally do not add a milestone target until a pullrequest branch is ready, as this limits distraction and prevents a lot of milestone churn. Occasionally exceptions are made in cases where there is high confidence that a branch will be ready in time for the milestone, so the milestone is added early to indicate intention.
Thanks, Dan Daniel Wells Library Programmer/Analyst Hekman Library, Calvin College 616.526.7133 From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Liam Whalen Sent: Thursday, January 16, 2014 1:08 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Reminder: Deadline is TODAY for 2.6 alpha targeting [RM2.6] Hi Dan, I have a few improvements to the staff client that I am still testing internally, but I plan to push them into 2.6 at some point. Would it be best to create launchpad bugs for them now? Liam Whalen BC Libraries Cooperative - Sitka Systems Specialist 855-383-5761 x1022 liam.wha...@bc.libraries.coop<mailto:liam.wha...@bc.libraries.coop> On Jan 16, 2014, at 9:31 AM, Dan Wells <d...@calvin.edu<mailto:d...@calvin.edu>> wrote: Hello all, Just a quick reminder that today is the last day to target bugs for inclusion in 2.6 alpha. As in past releases, new features will still be permitted until beta, which is scheduled for early February. That said, the sooner something is ready and targeted, the more likely it will be reviewed and included in 2.6, so please don't miss this opportunity to get some attention for your branch. Here is the current list of bug reports in the 2.6.0-alpha1 milestone which also have pullrequest tags: https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.milestone%3Alist=62053&field.tag=pullrequest&field.tags_combinator=ANY&search=Search&orderby=id&start=0 This is the list which I am asking reviewers focus on over the next few days, but as you can see, the list is relatively small. In contrast, here is a list of *all* un-committed pullrequests: https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.tag=pullrequest&field.tags_combinator=ANY&search=Search&orderby=-milestone&memo=75&start=0&direction=backwards I couldn't figure out a way to exclude the items already targeted at 2.6 (the first list), but I was able to sort them to the bottom. As you can see, we (at the time of this writing) have 70+ pullrequests which are either targeted only at old branches or not targeted at all. Many of these are stale and should probably be invalidated, but many others should rightly be targeted at 2.6. If you are able, please take some time today to review the second list, and apply the 2.6.0-alpha1 milestone (or invalidate) as you deem appropriate. As always, please reply to this thread if you have any questions or concerns. Thank you, Dan Daniel Wells Library Programmer/Analyst Hekman Library, Calvin College 616.526.7133
