Personally, maybe at least one per month for public. We should perform better than declared and expected.
After we graduate, we are all flexible to do as you want. Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Xuanwo <[email protected]>于2023年10月17日 周二17:15写道： > > How long would we take for every release due to this process? > > From our recent experiences, we've spent roughly a week on voting. Should > we exclude voting time from our schedule? > > For example: The OpenDAL community will release updates from the main > branch every three weeks. However, the actual usage time hinges on when the > vote is passed, or it may not occur at all if the vote doesn't succeed. > > On Tue, Oct 17, 2023, at 17:06, Sheng Wu wrote: > > Just a reminder, are we sure we are ready for this release cycle? As an > > incubator project, we are relying on IPMC vote. How long would we take > for > > every release due to this process? > > > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Twitter, wusheng1108 > > > > > > Xuanwo <[email protected]>于2023年10月17日 周二16:47写道： > > > >> Hi, all opendal community members > >> > >> OpenDAL's release process is now stable, with several successful > releases > >> under our belt. It seems appropriate to consider our release policy. > >> > >> OpenDAL currently adheres to a bi-weekly release schedule, launching a > new > >> version every two weeks. If there are breaking changes, we increment the > >> minor version; if not, we simply update the patch version. After > entering > >> the ASF incubator, we've allotted an additional week for voting. > >> > >> Please note, hot patches are not included in the release schedule. We > can > >> initiate a new release whenever our committer deems it necessary. Our > >> release schedule assures users that we will launch a new version every > >> three weeks. > >> > >> Should we document this release schedule? > >> > >> Xuanwo > >> > > -- > Xuanwo >
