Hi, +1 to release a bugfix version that fixes critical bugs asap.
But as ASF requires any consensus discussion should last 3 days, a tradeoff solution is, step 1, provide a bugfix solution first, and step 2, release the bugfix version 3 days later. In these 3 days, if some Bugfix PR wants to be released in this upcoming version, call reviewers in the mailing list and then we can promote the PR's priority to merge it in time. But, if the bugfix version is for fixing a critical bug, we will do not wait more after 3 days' discussion (which means the release train will launch on time). So, IMO, considering there is a critical bug, we can discuss which PRs should be released in v0.12.3, and begin to release v0.12.3 on Saturday. Welcome to show more suggestions. Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Eric Pai <ericpa...@hotmail.com> 于2021年9月16日周四 下午5:05写道： > > Hi, > > As it's a critical bug fix, a patch version is necessary. +1 for releasing > v0.12.3. > > Maybe we can publish a release schedule calendar in github or some other > pages __, thus everyone will know the whole roadmap and milestones. > > 在 2021/9/16 下午4:42，“Jialin Qiao”<qiaojia...@apache.org> 写入: > > Hi, > > Release big version at a fixed schedule is controllable. Bugfix version > release could be separated into two: > > Suppose we just released a version. > > (1) If someone fixes a non-critical bug in this version, we could start a > discussion: > > "how about release the next minor version 2 weeks later." > > This will make everyone comfortable to catch up with the release. > > (2) If someone fixes a critical bug in this version, we could discuss: > > "We just fix a critical bug, how about release now?" > > ________ > > On this occasion, this could be a critical bug > > > * IOTDB-1693 > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FIOTDB-1693&data=04%7C01%7C%7Cf0ab608957a84e09508508d978edf348%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637673785668847486%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VNoXQ0yDE8QgFpPz1uq%2FJcLcUQIL%2FjykU4kBmyjxm%2FY%3D&reserved=0> > fix IoTDB > restart does not truncate broken ChunkGroup bug > > The restart will leave some dirty data in TsFile, which causes the > TsFileSequenceRead to throw an exception. > > Therefore, release 0.12.3 is ok from me :) > > Thanks, > ————————————————— > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
