+1 to build a RC on Thursday this week. Thanks Nick.
On Tue, Nov 27, 2018 at 5:56 PM Nicholas Knize <[email protected]> wrote:
>
> Hello all. A quick update on 7.6. It looks like all blockers have been 
> resolved. Let me know if I missed any and if there aren't any objections I'll 
> plan to build a 7.6 RC on Thursday of this week.
>
> Thanks!
>
>
>
> On Wed, Nov 21, 2018 at 1:34 PM Cassandra Targett <[email protected]> 
> wrote:
>>
>> Doc changes are still fine, Andrzej. I still have a couple things to do for 
>> the Ref Guide also.
>>
>> On Wed, Nov 21, 2018 at 12:09 PM Andrzej Białecki <[email protected]> wrote:
>>>
>>> Hi Nicholas,
>>>
>>> If it’s ok I would like to merge a small fix to the Ref Guide, spotted by 
>>> Christine in SOLR-9856.
>>>
>>> On 1 Nov 2018, at 21:38, 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]
>>>
>>>
>>>
>>>
>>> —
>>>
>>> Andrzej Białecki
>>>
> --
>
> Nicholas Knize, Ph.D., GISP
> Geospatial Software Guy  |  Elasticsearch
> Apache Lucene Committer
> [email protected]



-- 
Adrien

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

Reply via email to