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
