The current build is old which is why I must manually update it. Once this is done then it may become more worthwhile to spend time on since only extant issues will be displayed.
On Mon, Apr 1, 2019 at 8:47 AM Christopher Michael <[email protected]> wrote: > On 4/1/19 8:40 AM, Mike Blumenkrantz wrote: > > Hi, > > I'd like to get an idea of what critical items remain for the 1.22 release, > ideally for the purpose of doing the release sometime this week. My current > items: > > * https://git.enlightenment.org/core/efl.git > We're doing some work on this and I'm not considering it a release blocker > even though it would be nice to have functional CI again. > > * Coverity > It seems we are not using github integration for this which means I have to > manually update this soon to determine if there's anything worthwhile here. > Not a blocker. > > I took a look, and the last Coverity run was done on March 12. There are > 20 outstanding issues which are rated HIGH as Impact. I will provide some > patches today or tomorrow to help eliminate a few of these, but it would be > helpful if others could take a look also as some of these are in components > that I am not entirely familiar with. > > > Cheers, > > Chris > > > Is anyone working on any critical items which must go into the release? > This list of items should include either bug fixes or doc fixes only. > > > Thanks, > Mike > > _______________________________________________ > enlightenment-devel mailing > [email protected]https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
