On Tue, 4 Feb 2014 12:46:18 -0500, 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. I also would like (with Release 9 or 10) to write a description of Bloodhound and post it to a french technical website (though I'll write first in english and translate after). I find it useful for getting feedbacks as people there are quite knowledgeable. It can also attract more contributors. I will send the paper on the mailing-list for review. That way if there is anything wrong or incorrectly described, people can correct me. I hope that it won't kill the demo website with a slashdot effect. ;-) Best regards,
