Hmmmm, my off-the-cuff reaction is that this feels too early.

In the back of my mind I had the 7.6 release roughly coinciding with
8.0 to tie the 7x code line up in a bow. I suppose it doesn't really
matter if it is Solr 7.7 or later if we want something coincident with
8.0 though.
On Thu, Nov 1, 2018 at 1:38 PM Nicholas Knize <[email protected]> wrote:
>
> Hi all,
>
> To follow up from our discussion on the 8.0 thread, I would like to cut the 
> 7.6 branch on either Tuesday or Wednesday of next week. Since this implies 
> feature freeze I went ahead and had a look at some of the issues that are 
> labeled for 7.6.
>
> It looks like we only have one active issue listed as a blocker for Solr. The 
> upgrade notes in SOLR-12927
>
> For Lucene we have five active issues (each with a patch provided) listed as 
> blockers targeted for 7.6.
>
> If there are any other issues that need to land before cutting the branch, 
> and they are not already labeled, please either mark them as blockers 
> accordingly or let me know prior to cutting the branch next Tuesday or 
> Wednesday.
>
> Thank you!
>
> - Nick
> --
>
> Nicholas Knize, Ph.D., GISP
> Geospatial Software Guy  |  Elasticsearch
> Apache Lucene Committer
> [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to