On Tue, Mar 4, 2014 at 6:59 PM, Ryan Ollos <[email protected]> wrote:
> On Mon, Mar 3, 2014 at 1:01 AM, Ryan Ollos <[email protected]>wrote: > >> On Thu, Jan 9, 2014 at 12:36 AM, Ryan Ollos <[email protected]>wrote: >> >>> Now that work is completed for the Trac 0.12.6/1.0.2/1.1.2 milestones, >>> I'm looking at the Bloodhound Release 8 milestone and it seems that we have >>> a large number of issues that have been fixed, but also a large number of >>> potential blockers. >>> >>> For the Release 8 milestone I have 11 tickets assigned to me, which I >>> intend to work over the next week. It would be helpful if others could go >>> through the tickets associated with Release 8 and decide if they are >>> blockers that can be resolved in the next week or two, and if not, move >>> them to Release 9. >>> >>> I had hoped Release 9 would be the one in which we can integrate fixes >>> from the Trac 1.0.2 release, but depending on when that release happens and >>> how ambitious we are with creating another Bloodhound release, integration >>> of the changes from Trac 1.0.2 may need to wait until the Bloodhound >>> Release 10. >>> >>> - Ryan >>> >> >> You may notice that I've moved many of the tickets into the "next 0.x" >> milestone. I did this because I feel that having too many tickets in the >> upcoming milestones has been a problem. We need the milestones to represent >> a goal we can work towards, so that we get the releases out at regular >> intervals. The "next 0.x" milestone therefore is a placeholder for issues >> that probably need to be resolved before we can get to Release 1.0. >> >> What I've left in the "Release 9" milestone are tickets that will be >> resolved when I merge in Trac 1.0.2. Here is how I propose to proceed: >> * Leave tickets in "next 0.x" or "Unscheduled" at least until you start >> working on them. >> * Aim for releasing at 4 week intervals. "Release 9" is scheduled for >> end of March and "Release 10" for end of April. >> >> As for "Release 8", I have a few more changes to commit later today. >> After those are resolved I'll make the branch that we can start testing >> against to make sure there are no major issues. >> >> - Ryan >> > > I apologize to those that are subscribed to commits@ for all of the noise > today. I hope that the result will be a clearer picture of what we need to > fix to get to the 1.0 release. > I've completed a review of all of the tickets going back to about #250 or so. Earlier tickets still need to be reviewed, but since many of them are stale by now, I think Olemis or Gary could do this better and faster than I can, so I kindly ask for their help. Please comment if you see any tickets that you think I haven't targeted to the correct milestone. We have 60+ that look like they need to be fixed before we can get to 1.0, not counting the "Trac 1.0.2" tickets that I've already assigned to Release 9. https://issues.apache.org/bloodhound/milestone/next%200.x Tickets that don't need to be fixed for Release 1.0 (according to my best judgement), I've put in the "Unscheduled" milestone. https://issues.apache.org/bloodhound/milestone/Unscheduled I needed a placeholder for Bloodhound tickets that depend on a Trac ticket that will be fixed in a 1.1.x release, and so we probably won't integrate the changes until Trac 1.2 is release. The "next 1.x" milestone was created for this purpose: https://issues.apache.org/bloodhound/milestone/next%201.x
