I tend to agree with the last comments. 3 months is a good compromise considering the current project status.
Yeser On 2025/01/14 11:12:37 Enrique Gonzalez Martinez wrote: > Agreed that one month that might be overkilling as keeping in mind > Dev + Code Freeze + Test (RC1...RCn) + Release > It is way too much. This will lead to project resources starvation as > we will spend more releasing that doing stuff. > Any feature in the backend can take easily 1 month (any interesting > stuff) best case scenario, so at least 2 months release would be the > minimum. > > Cheers :) > > El mar, 14 ene 2025 a las 12:04, Toni Rikkola (<trikk...@redhat.com>) > escribió: > > > > Every 3 months would likely be a good starting point. If automation ends up > > being high enough, then once a month should not be an issue. > > > > With everything that is missing for graduation I suspect we have to freeze > > the code base every now and then, not ideal, but the easiest path to get > > things done. This will slow down the PR streams making once a month > > releases less effective. > > > > Toni > > > > On Tue, Jan 14, 2025 at 12:14 PM Jozef Marko <jozef.ma...@ibm.com.invalid> > > wrote: > > > > > Hi, my personal opinion or experience is that 1 month cadence will not > > > work. A people that are members of the Apache KIE community work also on > > > other tasks. On tasks not related to the community release. I agree good > > > software should have often releases. One month is too brave goal in my > > > opinion. The window to do a release should be longer from my point of > > > view. > > > > > > > > > Jozef Marko > > > > > > Software Developer > > > > > > jozef.ma...@ibm.com > > > > > > > > > > > > ________________________________ > > > From: Tibor Zimányi <tzima...@apache.org> > > > Sent: Friday, January 10, 2025 3:35 PM > > > To: dev@kie.apache.org <dev@kie.apache.org> > > > Subject: [EXTERNAL] [PROPOSAL] Release cadence stabilization > > > > > > 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 > > > > > > > -- > Saludos, Enrique González Martínez :) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > For additional commands, e-mail: dev-h...@kie.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org For additional commands, e-mail: dev-h...@kie.apache.org
