Hello Jonathan. On 09.01.19 16:26, Jonathan Aquilina wrote: > I’m ready to step and take charge of this but I think we need a bit more > frequent minor release updates both for those in the community that want to > Be on the bleeding edge and those that want to help bug fix more incremental > stable releases.
Glad to hear. Happy to have you in the release team. How often do you think we should have minor releases? On y fix schedule or when enough patches have been in? We could look and see if we should do one for the 1.21.X line. That might be a good exercise to get started. You have an interest in working on this (with my help)? > Stefan do you have any documentation on how release plan works? You missed my answer to your other mail (next release)? Here are my notes how I did the releases: https://phab.enlightenment.org/w/release_procedure/ Pretty sure there are many things that are not clear to anyone but me. Feel free to edit the wiki and ask me. If you could get yourself comfortable with the steps involved that would already be a help. For example try to produce some release tarballs on your local machine and see if you run into troubles. regards Stefan Schmidt > Get Outlook for iOS<https://aka.ms/o0ukef> > > ________________________________ > From: Stefan Schmidt <ste...@datenfreihafen.org> > Sent: Wednesday, January 9, 2019 16:22 > To: e > Subject: [E-devel] 1.22 schedule proposal > > Hello. > > Its almost 5 months since we released 1.21 and I stepped down. > > When talking with people I got help offers on the release handling but > no-one stepped up to fully take a lead on this. I start to get the > feeling that this might need to be handled with a smoother transition of > knowledge and work. > > Jonathan and Mike both offered help and others also expressed that they > would be willing to do their share towards a release. I count on you to > make this work :-) > > To get back to time based releases we should get working on 1.22 soon > (and not block ourselves with $FEATURE not being ready right now) > > The 3 months based schedule has been putting to much load onto the > project with release stuff. At least that is my opinion. After 1.22 is > out we should think about increasing this. Maybe 4, 5 or even 6 months? > Up to discussion. > > After 5 full months of development I think we should allow two weeks > before we freeze to allow everybody to get their work in order. Fixes > will follow over the next weeks to get it ready. > > Here is my release schedule proposal to get us started. Comments? > > === Schedule === > 2018-08-17 Merge window for 1.22 opens > 2019-01-18 Notice about soon ending merge window > 2019-01-23 Merge window is over. Freeze in place. > * Only bug fixes from this point > * Alpha release tarball > * One month stabilization phase starts > 2019-01-30 Beta1 release tarball > * Only critical fixes from this point > 2019-02-06 Beta2 release tarball > 2019-02-13 EFL 1.22 is out > > regards > Stefan Schmidt > > > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
