Hi Ab, How quickly are we talking about? If you suggest, we could wait, depending upon the impact, and the time required to fix it.
Anshum On Thu, Aug 10, 2017 at 12:28 PM Andrzej Białecki < [email protected]> wrote: > I just discovered SOLR-11221, which basically breaks JMX monitoring. We > could either release with “known issues” and then quickly do 7.0.1, or wait > until it’s fixed. > > On 10 Aug 2017, at 18:55, Mark Miller <[email protected]> wrote: > > I'll generate a test report for the 7.0 branch tonight so we can evaluate > that for an rc as well. > > - Mark > > On Mon, Aug 7, 2017 at 1:32 PM Anshum Gupta <[email protected]> > wrote: > >> Good news! >> >> I don't see any 'blockers' for 7.0 anymore, which means, after giving >> Jenkins a couple of days, I'll cut out an RC. I intend to do this on >> Wednesday/Thursday, unless a blocker comes up, which I hope shouldn't be >> the case. >> >> Anshum >> >> >> On Tue, Jul 25, 2017 at 4:02 PM Steve Rowe <[email protected]> wrote: >> >>> I worked through the list of issues with the "numeric-tries-to-points” >>> label and marked those as 7.0 Blocker that seemed reasonable, on the >>> assumption that we should at a minimum give clear error messages for points >>> non-compatibility. >>> >>> If others don’t agree with the Blocker assessments I’ve made, I’m >>> willing to discuss on the issues. >>> >>> I plan on starting to work on the remaining 7.0 blockers now. I would >>> welcome assistance in clearing them up. >>> >>> Here’s a JIRA query to see just the remaining 7.0 blockers, of which >>> there are currently 12: >>> >>> < >>> https://issues.apache.org/jira/issues/?jql=project+in+(SOLR,LUCENE)+AND+fixVersion=7.0+AND+priority=Blocker+AND+resolution=Unresolved >>> > >>> >>> -- >>> Steve >>> www.lucidworks.com >>> >>> > On Jul 25, 2017, at 2:41 PM, Anshum Gupta <[email protected]> >>> wrote: >>> > >>> > I will *try* to get to it, but can't confirm. If someone else has a >>> spare cycle and can take it up before I get to it, please do. >>> > >>> > -Anshum >>> > >>> > On Tue, Jul 25, 2017 at 10:44 AM Cassandra Targett < >>> [email protected]> wrote: >>> > I believe the only remaining blocker to SOLR-10803 (to mark all Trie* >>> > fields as deprecated) is SOLR-11023, which Hoss was working on. As he >>> > noted last night, he is off for vacation for the next 2 weeks. Is >>> > anyone else available to work on it so 7.0 isn't stalled for 2+ more >>> > weeks? >>> > >>> > Now would also be a good time to look over any other bugs with >>> > PointFields and make a case if any should be considered blockers for >>> > 7.0. I think they all share a label: >>> > >>> https://issues.apache.org/jira/issues/?jql=status%20%3D%20Open%20AND%20labels%20%3D%20numeric-tries-to-points >>> > >>> > On Tue, Jul 11, 2017 at 4:59 PM, Chris Hostetter >>> > <[email protected]> wrote: >>> > > >>> > > : So, my overall point is that if A) we agree that we want to >>> deprecate >>> > > : Trie* numeric fields, and B) we want to hold up the 7.0 release >>> until >>> > > : that's done, it's more than just updating the example schemas if we >>> > > : want to ensure a quality app for users. We still need to fix the >>> tests >>> > > : and also fix bugs that are going to be really painful for users. >>> And >>> > > : to get all that done soon, we definitely need some more volunteers. >>> > > >>> > > I've beefed up the description of SOLR-10807 with tips on how people >>> can >>> > > help out... >>> > > >>> > > https://issues.apache.org/jira/browse/SOLR-10807 >>> > > >>> > > >>> > > >>> > > -Hoss >>> > > http://www.lucidworks.com/ >>> > > >>> > > --------------------------------------------------------------------- >>> > > To unsubscribe, e-mail: [email protected] >>> > > For additional commands, e-mail: [email protected] >>> > > >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: [email protected] >>> > For additional commands, e-mail: [email protected] >>> > >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> -- > - Mark > about.me/markrmiller > > >
