Re: [hibernate-dev] [HSEARCH][V6-POC] Bug tracking for the Search 6 POC

Thanks, we will do that. I may add some markers to the tickets though (component, label, ...): I just thought we will need to list tickets that must be solved before we merge the POC into the main repository. On Thu, 5 Apr 2018 at 16:12 Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > +1 to create issues in "main" project JIRA > > Since JIRA is an issue tracker, some people frown upon its usage as > planning tool. I also don't think it fits too well, especially when we > go too much in detail with upfront planning, but it's not too bad. > Preferrable to yet-another-tool. > > I don't think we need to "tag" them as POC-6, it's all the same project. > > Thanks, > Sanne > > > > > On 5 April 2018 at 08:07, Yoann Rodiere <yoann(a)hibernate.org&gt; wrote: > > Hello, > > > > With the Search 6 POC getting closer and closer to something we can > merge, > > and thus more and more complex, we are starting to see quite a lot of > TODOs > > piling up. > > I've been tracking most of them in a Google Doc > > < > https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM... > > > > so far, and it's fine for big architectural topics, but for small things > > it's clearly inadequate. > > > > What would you all think if we started to use the main Hibernate Search > > project to track the small TODOs we have in the Search 6 POC? We would > > probably have to add some JIRA Components that only make sense in > Search 6 > > ("indexing", ...), but beyond that I don't think this would cause much > > trouble. > > The tickets would all be Tasks targeting version 6, and we could tag > them > > with a new "POC-6.0" component if you think it's necessary. Examples of > > tasks would be: > > > > - Native sorts in the Lucene Sort DSL extension > > < > https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM... > > > > - Native predicates in the Lucene Predicate DSL extension > > < > https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM... > > > > - Rework the Lucene DSL implementations to fail fast when parameter > > conversion errors occur > > < > https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM... > > > > - Polish and test Stream indexing (add CompletableFuture returns in > > particular) > > - Decide wether to use absolute or relative object path in "nested" > > search predicates > > > > If this feels like too much garbage for the main bug tracker, we can > create > > a separate JIRA project instead. But then this will add to the trouble > > we'll have to go through when merging (commits referring to tickets from > > another project). > > > > Sanne, all, WDYT? > > -- > > Yoann Rodiere > > yoann(a)hibernate.org / yrodiere(a)redhat.com > > Software Engineer > > Hibernate NoORM team > > _______________________________________________ > > hibernate-dev mailing list > > hibernate-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > -- Yoann Rodiere yoann(a)hibernate.org / yrodiere(a)redhat.com Software Engineer Hibernate NoORM team