On Fri, Feb 7, 2014 at 7:10 AM, Saint Germain <[email protected]> wrote:
> On 7 February 2014 12:03, Ryan Ollos <[email protected]> wrote: > >> > On Thu, Jan 9, 2014 at 3: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 > >> > > > >> > > >> > It's clear now that I've missed the previous deadline that I was > >> > aiming for, due to getting focused on various issues. Let's target > >> > this Friday for creating a stable branch that will be used for the > >> > release. We can then start testing and integrating minor fixes if > >> > necessary, with the aim of producing a release several days later. > >> > > >> > Since we have two new committers on board, let's make sure to > >> > communicate which tickets and features we intend to include in the > >> > release. I'll be reviewing tickets today and will follow-up with my > >> > own list. If there's something in particular that you think should be > >> > included, but you won't have time to integrate the changes before > >> > Friday, please propose an alternative date (such as end of the > >> > weekend). > >> > > >> > >> Hello Ryan, > >> > >> For me I only wish to commit 2 tickets (#694 "i18n" and #741 "whoosh") > >> if that is fine with you. > >> > > > > That sounds good. Do you think you can commit the work by the end of the > > weekend? > > > > Hello Ryan ! > > I will commit at the latest saturday. I would like to give Olemis some > time to review my latest patch (but there are not many changes so I > think it is correct). > With #694 closed, I guess it is time to move towards a release. There are a few action items that we could get closure on by Wednesday, - The patch in #750 is requesting review - I've been working on #695, #756 and #757 and plan to close those out - I plan to review Antony's latest patch in #727 and hopefully that can be integrated If you see anything else that looks critical please mention the ticket here. I'll do some ticket triage once i.a.o is back.
