On 1/24/15, Ryan J Ollos <[email protected]> wrote: > So that we have a goal to work towards, Release 9 has been created with a > moderate number (currently 10) of tickets, and the goal of releasing on 01 > March. >
Nice ! > Most of the tickets fit the following criteria: > 1. High priority issues reported by the community (#813, #840, #845, #846) Would be nice to fix these , yes > 2. In-progress tickets that were not complete for Release 8 (#695) I could test this , though test cases have been proposed afaicr ... > 3. Minor cosmetic issues that should be easy to fix (#634, #842) > ... and try to take a look into these as well . > I hope devs will feel free to pick up and work any of these tickets, I'll try to follow your call on this subject . Nonetheless considering the *apparent* synchronization of Trac + BH releases , would it be worthy to upgrade the version of Trac distributed with BH and keep them in sync ? > as > well as target any other important issues to the milestone. > It will be good > to keep the scope of the milestone fairly small though, so that we can > achieve the goal of releasing on March 1. > yes , I do think that contributors will be much more motivated if the project releases early and is constantly moving towards next milestone . Nevertheless scheduling for April (i.e. one month after Trac's) might help with testing BH core after merging latest Trac release , in case that's something worth doing for Release 9 . We could also merge Trac core twice a year (i.e. six month time window) p.s. I'm planning to attend PyCon this year too so I'm also hoping to meet you (and others interested on Trac + BH development) there during sprints . -- Regards, Olemis - @olemislc Apache(tm) Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
