Hi Adrien,

Thanks for informing but I think it still makes sense for us to release a
5.3.2 for users who have decided to be on or are already on 5.3.x.
5.4 might mean a complicated upgrade for those users.

On Tue, Jan 12, 2016 at 2:15 PM, Adrien Grand <[email protected]> wrote:

> That's fine with me, I just wanted to make sure that the fact that 5.4.1
> will go out soon does't change our considerations.
>
> Le mar. 12 janv. 2016 à 09:39, Shai Erera <[email protected]> a écrit :
>
>> I think that the reason for this release was to offer users who have just
>> upgraded to 5.3 those bug fixes, without requiring them to upgrade to 5.4.
>>
>> On Tue, Jan 12, 2016 at 10:37 AM Adrien Grand <[email protected]> wrote:
>>
>>> Hi Anshum,
>>>
>>> Just in case you didn't see the other thread called "5.4.1 release", we
>>> need to do a bugfix release to address a potential corruption that affects
>>> Lucene/Solr 5.4.0. Since this 5.4.1 release ought to contain all fixes that
>>> are also in 5.3.2, maybe it's not worth releasing 5.3.2 anymore? Sorry for
>>> only suggesting it now, I know you already spent time on this release but
>>> wanted to make sure that you were aware that we need to do a 5.4.1 soon as
>>> well.
>>>
>>> Le lun. 11 janv. 2016 à 21:38, Anshum Gupta <[email protected]> a
>>> écrit :
>>>
>>>> Please vote for the RC1 release candidate for Lucene/Solr 5.3.2
>>>>
>>>> The artifacts can be downloaded from:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.3.2-RC1-rev1723976
>>>>
>>>> You can run the smoke tester directly with this command:
>>>> python3 -u dev-tools/scripts/smokeTestRelease.py
>>>>
>>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.3.2-RC1-rev1723976
>>>>
>>>> Sorry for the super long delay but my internet connection required 4
>>>> attempts to commit the RC.
>>>> --
>>>> Anshum Gupta
>>>>
>>>


-- 
Anshum Gupta

Reply via email to