> 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 <[email protected]> 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 <[email protected]> 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 宋子阳 <[email protected]> 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 >> >>
