You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ratis.apache.org by 宋子阳 <sz...@163.com> on 2022/04/26 02:34:30 UTC
Timeline of Release 2.3.0
Hi,
We discovered that the last Ratis release (2.2.0) was 6 months back. Since then a number of fixes and exciting features are merged into Master. In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related to snapshot, which is fixed in current Ratis master. We are wondering what’s the community’s plan on releasing 2.3.0. Is there a timeline?
Thanks,
William Song
Re: Timeline of Release 2.3.0
Posted by Tsz Wo Sze <sz...@gmail.com>.
> Please do not recommend users use snapshot versions. That violates Apache
policy. ..
Owen, thanks a lot for the reminder! You are right that it is in the
Apache Release Policy [1].
William, please wait for the 2.3.0 release then. If there is a need, we
may also release 2.2.1. Please let us know.
Tsz-Wo
[1] https://www.apache.org/legal/release-policy.html#publication
On Tue, Apr 26, 2022 at 9:38 PM Owen O'Malley <ow...@gmail.com>
wrote:
> Please do not recommend users use snapshot versions. That violates Apache
> policy. Projects should make official releases on the versions people
> need. Releasing 2.3 is good, but I’d also suggest making a 2.2.1.
>
> .. Owen
>
> On Apr 25, 2022, at 22:25, Tsz Wo Sze <sz...@gmail.com> wrote:
>
>
> Hi William,
>
> Thanks for bringing this out. Yes, it is a good time to prepare the 2.3.0
> release. We should include both RATIS-1567 and RATIS-1563 in 2.3.0. Are
> there any other JIRAs we should include?
>
> > ... In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug
> related to snapshot, which is fixed in current Ratis master. ...
>
> The IoTDB project may consider using a Ratis snapshot for development.
> For example, the HDDS-4454 branch in Apache Ozone current uses Ratis
> 2.3.0-6742a4e-SNAPSHOT; see
> https://github.com/apache/ozone/blob/7c5356b4e6502b5ed7f98e5f70ee6acfac2a1997/pom.xml#L76
> . Note that 6742a4e is a commit id prefix. If there is a need, we can
> deploy a new snapshot anytime. Please let me know.
>
> Regards,
> Tsz-Wo
>
> On Tue, Apr 26, 2022 at 10:34 AM 宋子阳 <sz...@163.com> wrote:
>
>> Hi,
>> We discovered that the last Ratis release (2.2.0) was 6 months back.
>> Since then a number of fixes and exciting features are merged into Master.
>> In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related
>> to snapshot, which is fixed in current Ratis master. We are wondering
>> what’s the community’s plan on releasing 2.3.0. Is there a timeline?
>>
>> Thanks,
>> William Song
>>
>>
Re: Timeline of Release 2.3.0
Posted by Owen O'Malley <ow...@gmail.com>.
Please do not recommend users use snapshot versions. That violates Apache policy. Projects should make official releases on the versions people need. Releasing 2.3 is good, but I’d also suggest making a 2.2.1.
.. Owen
> On Apr 25, 2022, at 22:25, Tsz Wo Sze <sz...@gmail.com> wrote:
>
>
> Hi William,
>
> Thanks for bringing this out. Yes, it is a good time to prepare the 2.3.0 release. We should include both RATIS-1567 and RATIS-1563 in 2.3.0. Are there any other JIRAs we should include?
>
> > ... In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related to snapshot, which is fixed in current Ratis master. ...
>
> The IoTDB project may consider using a Ratis snapshot for development. For example, the HDDS-4454 branch in Apache Ozone current uses Ratis 2.3.0-6742a4e-SNAPSHOT; see https://github.com/apache/ozone/blob/7c5356b4e6502b5ed7f98e5f70ee6acfac2a1997/pom.xml#L76 . Note that 6742a4e is a commit id prefix. If there is a need, we can deploy a new snapshot anytime. Please let me know.
>
> Regards,
> Tsz-Wo
>
>> On Tue, Apr 26, 2022 at 10:34 AM 宋子阳 <sz...@163.com> wrote:
>> Hi,
>> We discovered that the last Ratis release (2.2.0) was 6 months back. Since then a number of fixes and exciting features are merged into Master. In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related to snapshot, which is fixed in current Ratis master. We are wondering what’s the community’s plan on releasing 2.3.0. Is there a timeline?
>>
>> Thanks,
>> William Song
>>
Re: Timeline of Release 2.3.0
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi William,
Just have sent an email to dev@ for the release discussion; see
https://lists.apache.org/thread/fdkg3gg8rfmz9t695zpw9ct41vftcjbp
Tsz-Wo
On Tue, Apr 26, 2022 at 1:25 PM Tsz Wo Sze <sz...@gmail.com> wrote:
> Hi William,
>
> Thanks for bringing this out. Yes, it is a good time to prepare the 2.3.0
> release. We should include both RATIS-1567 and RATIS-1563 in 2.3.0. Are
> there any other JIRAs we should include?
>
> > ... In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug
> related to snapshot, which is fixed in current Ratis master. ...
>
> The IoTDB project may consider using a Ratis snapshot for development.
> For example, the HDDS-4454 branch in Apache Ozone current uses Ratis
> 2.3.0-6742a4e-SNAPSHOT; see
> https://github.com/apache/ozone/blob/7c5356b4e6502b5ed7f98e5f70ee6acfac2a1997/pom.xml#L76
> . Note that 6742a4e is a commit id prefix. If there is a need, we can
> deploy a new snapshot anytime. Please let me know.
>
> Regards,
> Tsz-Wo
>
> On Tue, Apr 26, 2022 at 10:34 AM 宋子阳 <sz...@163.com> wrote:
>
>> Hi,
>> We discovered that the last Ratis release (2.2.0) was 6 months back.
>> Since then a number of fixes and exciting features are merged into Master.
>> In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related
>> to snapshot, which is fixed in current Ratis master. We are wondering
>> what’s the community’s plan on releasing 2.3.0. Is there a timeline?
>>
>> Thanks,
>> William Song
>>
>>
Re: Timeline of Release 2.3.0
Posted by 宋子阳 <sz...@163.com>.
Thanks! We are looking forward to 2.3.0, wish everything alright!
> 2022年4月26日 13:25，Tsz Wo Sze <sz...@gmail.com> 写道：
>
> Hi William,
>
> Thanks for bringing this out. Yes, it is a good time to prepare the 2.3.0 release. We should include both RATIS-1567 and RATIS-1563 in 2.3.0. Are there any other JIRAs we should include?
>
> > ... In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related to snapshot, which is fixed in current Ratis master. ...
>
> The IoTDB project may consider using a Ratis snapshot for development. For example, the HDDS-4454 branch in Apache Ozone current uses Ratis 2.3.0-6742a4e-SNAPSHOT; see https://github.com/apache/ozone/blob/7c5356b4e6502b5ed7f98e5f70ee6acfac2a1997/pom.xml#L76 <https://github.com/apache/ozone/blob/7c5356b4e6502b5ed7f98e5f70ee6acfac2a1997/pom.xml#L76> . Note that 6742a4e is a commit id prefix. If there is a need, we can deploy a new snapshot anytime. Please let me know.
>
> Regards,
> Tsz-Wo
>
> On Tue, Apr 26, 2022 at 10:34 AM 宋子阳 <szywilliam@163.com <ma...@163.com>> wrote:
> Hi,
> We discovered that the last Ratis release (2.2.0) was 6 months back. Since then a number of fixes and exciting features are merged into Master. In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related to snapshot, which is fixed in current Ratis master. We are wondering what’s the community’s plan on releasing 2.3.0. Is there a timeline?
>
> Thanks,
> William Song
>
Re: Timeline of Release 2.3.0
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi William,
Thanks for bringing this out. Yes, it is a good time to prepare the 2.3.0
release. We should include both RATIS-1567 and RATIS-1563 in 2.3.0. Are
there any other JIRAs we should include?
> ... In our project (IoTDB) which uses Ratis 2.2.0, we encountered a bug
related to snapshot, which is fixed in current Ratis master. ...
The IoTDB project may consider using a Ratis snapshot for development.
For example, the HDDS-4454 branch in Apache Ozone current uses Ratis
2.3.0-6742a4e-SNAPSHOT; see
https://github.com/apache/ozone/blob/7c5356b4e6502b5ed7f98e5f70ee6acfac2a1997/pom.xml#L76
. Note that 6742a4e is a commit id prefix. If there is a need, we can
deploy a new snapshot anytime. Please let me know.
Regards,
Tsz-Wo
On Tue, Apr 26, 2022 at 10:34 AM 宋子阳 <sz...@163.com> wrote:
> Hi,
> We discovered that the last Ratis release (2.2.0) was 6 months back. Since
> then a number of fixes and exciting features are merged into Master. In our
> project (IoTDB) which uses Ratis 2.2.0, we encountered a bug related to
> snapshot, which is fixed in current Ratis master. We are wondering what’s
> the community’s plan on releasing 2.3.0. Is there a timeline?
>
> Thanks,
> William Song
>
>