Thanks for your interest in the release process. If you are interested in continuing to provide meaningful contributions for releases, you may consider joining the release team, as advertised and discussed in previous mailing list threads. We're always happy to have more help!
On the topic of showstopper issues, we had many, many mails related to the remaining issues that you cited over a period of months. We discussed them repeatedly on IRC, and we have easily-accessible sidebar queries for all patch submissions and urgent tasks. At some point, one has to assume that either people are aware of the remaining issues (and [lack of] work being done on them) or they are not interested. I don't believe that any further mails related to the 1.21 release could have benefited the release process, nor do I believe there was any action that should have been taken by Stefan which would have added any value to the eventual release. Getting this release out the door was heroic enough after how much time has passed since 1.20. On Tue, Aug 21, 2018 at 11:57 AM Christophe Sadoine <ch...@indefini.org> wrote: > On Wed, 22 Aug 2018 at 00:21, Stefan Schmidt <ste...@datenfreihafen.org> > wrote: > > > > Hello. > > > > On 08/21/2018 04:27 PM, Christophe Sadoine wrote: > > > On Sat, 18 Aug 2018 at 08:29, Stefan Schmidt < > ste...@datenfreihafen.org> wrote: > > >> > > >> After 12 months of development work we are proud to announce the > release of > > >> version 1.21 of the Enlightenment Foundation Libraries. In these 12 > > >> months we got > > >> almost 5000 commits from 96 authors. Great job everyone! Some > highlights > > >> are listed below. > > > > > > Congratulations on the release. > > > One point though, there were showstoppers for efl 1.21 in phab. > > > T7295,T7292,T7153 and they are still tagged to efl 1.21 as showstopper > > > issues. > > > Are showstoppers not supposed to block a release? > > > > They are. At some point though there have to be made a call to get > > something out or wait forever (1.21 took already over 12 months) Yes, > > that sometimes means we release with known issues. > > > > We are following up with stable updates after a major release to fix up > > what was not done or popped out after the release. I have been spending > > yesterday and today with fixing some problems that have been reported. > > > > > if yes then these tickets should have been resolved or set to another > > > status if people think they shouldn't block a release. > > > > Previously I demoted such issues to high. That also raised complains. We > > could do that though if it would set your mind at peace. > > > > More importantly though we should look to get them fixed and backported > > for a 1.21.1 release. > > > > Mike just committed two patches referencing the genlist issues. Might be > > worth trying to see if they are fixing the issue reported. > > > > For the DnD one Marcel already replied in the ticket > > > > > if no then can we get at least a warning when the release is done, for > example : > > > "the release has crashes with genlist, do not update to 1.21 if you > > > use these apis..." > > > > This often enough depends on a lot on the use cases and would not be > > valid for all users. Having a known issue section in release notes might > > be an option. If someone can summarise the issue to make it clear who > > should be concerned and who not. > > > > Given the release handling was mostly a one man show over the last many > > years I would say you can go ahead and put the blame on my. My credo was > > always to try getting a really good release out, but also be realistic > > that there will always be bugs and getting something out is sometimes > > better than to wait forever. Not everybody is happy with this approach, > > but I can take the blame for it. > > > > The good thing though is that this was my last release. Everybody, > > including you, can step up, join the release team and propose and work > > on changes to the procedure to make it perfect. There is plenty of room > > for improvements with the grumpy old release manager out of the way. :-) > > Don't worry no one's blaming anyone for anything :) > There were emails that said the release will probably be next week, > but given that there were showstoppers I wasn't really expecting it > when it dropped. > Maybe a mail like "ok there is no work on these issues, so we are > going to release anyway, is everybody fine with it?" would have been > nice. (or maybe there was and I missed it) > Good job for all the releases! > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
