Thanks Alex, sure, it could be like that. I will support any proposal that will signal to the community, that they won't wait for a binary release for another year.
Best regards, Tibor Dňa pi 10. 1. 2025, 18:26 Alex Porcelli <a...@porcelli.me> napísal(a): > Tibor, > > -1 for the current state of the proposal. However I fully support a > release schedule, the difference is that with a release schedule you > have blocker milestones, and those should be related to improvements > toward graduation. > > My draft alternative schedule proposal would be something like (it > would require a proper planning, but just to share the concept): > > Feb: 10.1.0, no milestone... just fix/improve already identified > issues in the release process. > after ~6-8 weeks: 10.2.0 remove EMF source code > (https://github.com/apache/incubator-kie-issues/issues/1709) > after ~6-8 weeks: 10.3.0 remove open font > (https://github.com/apache/incubator-kie-issues/issues/1712) > (...) > > (...) > > > On Fri, Jan 10, 2025 at 9:35 AM Tibor Zimányi <tzima...@apache.org> wrote: > > > > Hi everyone, > > > > I personally think that after our first release, the most important topic > > right now is to make sure we don't wait another year for another release. > > Therefore I think it is important to define the release cadence that we > > will follow and define a workflow, that we will follow in regular time > > intervals, based on the agreed cadence. If you would agree, we should > first > > make sure we have regular releases again and then we could open more > broad > > and impactful discussions about repositories structure, etc. Otherwise we > > risk being blocked for another year by these discussions. So here is my > > proposal for the release cadence: > > > > - Release should be done each month. > > - There should be a vote about a person responsible for these monthly > > releases. We need to have a specific person that makes sure the release > > workflow is progressing. The person doesn't need to do the actual work, > > however should make sure the release process is being done in a timely > > manner. > > - The person responsible for the release, makes sure the documented > > standard release process is followed. > > > > This is a very rough proposal. I am open for feedback or other > proposals. I > > just think we should stabilize releases before we dive into more broad > > discussions that could take months. > > > > Best regards, > > Tibor > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > For additional commands, e-mail: dev-h...@kie.apache.org > >
