Hello. On 13.07.2018 03:10, Jonathan Aquilina wrote: > Hi Stefan, > > What know how does one need for this role?
Well, there are many different parts to it. The mechanical part of doing the tarballs is not that hard (parts are even scripted). The other part is to keep an eye on the bug reports, monitoring critical ones, pitching in with comments, testing etc. Running things like abi-checker and reviewing the reports to see how we do regarding API breaks. The more complicated part is that you would need to understand enough of the code base to follow up with the latest issues that block a release. It does not mean you have to fix them yourself but you would need to understand the severity and impact the issue would have. In general I would recommend to have developer with longer efl experience to handle the release. There are tasks that can be split of and helped with by all kind of folks though. If one takes the releases notes as an example. This have been taking a lot of my extra time on the release. If someone would got around look through the git log, pick bigger features, ask the authors to write up a short piece on it and massages it all into release notes this could be split of to people without a core developer background easily. regards Stefan Schmidt ------------------------------------------------------------------------------ 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
