On Wed, Mar 5, 2014 at 2:01 PM, Olemis Lang <[email protected]> wrote:
> On 3/5/14, Ryan Ollos <[email protected]> wrote: > > On Tue, Mar 4, 2014 at 6:59 PM, Ryan Ollos <[email protected]> > wrote: > [...] > >> > >> 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. > >> > > afaict ... good ! > > > > > 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. > > > > I'll spend some time on this tomorrow . > > > 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 > > > > Maybe it will be useful to include those explanations in milestone > descriptions . I just do not have necessary privileges to do so . Good idea. I will add the descriptions.
