=== georgeowell_ is now known as georgeowell
[09:00] <darkxst> jbicha covered under the MRE?
[09:02] <jbicha> darkxst: https://irclogs.ubuntu.com/2017/05/16/%23ubuntu-devel.html#t09:16 (until 15:16)
[09:03] <jbicha> the important part is that the SRUs were accepted
[09:03] <darkxst> I meant the kde plasma one
[09:03] <jbicha> darkxst: you don't object to us closing gnome-shell/trusty bugs, right?
[09:04] <darkxst> from a quick glance I would have queried the first one on the basis of the test case ;)
[09:04] <darkxst> so long as they are not rejecting them ;)
[09:05] <darkxst> what is the EOL for trusty? April or July?
[09:05] <jbicha> April, https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
[09:07] <darkxst> regardless we are not going to be fixing trusty bugs now
[09:07] <darkxst> so yes I am fine with closing trusty bugs
[09:09] <darkxst> technicaly gnome updates should be covered under MRE also and not need proper SRU's?
[09:10] <jbicha> I think KDE or Kubuntu has some kind of CI/automated testing that GNOME doesn't have?
[09:10] <darkxst> or did they can the MRE's in my absence
[09:10] <jbicha> but yes, Laney was arguing that GNOME used to have a micro-release exception until SRU policy was rewritten
[09:11] <darkxst> CI testing is great for build failures not general user testing
[09:11] <darkxst> autopilot never really succeeded totally in the UI testing side
[09:11] <darkxst> and its useless on gnome-shell anyway!
[09:12] <jbicha> https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
[09:12] <jbicha> (changed in 2015)
[09:13] <darkxst> GNOME passes most of those except the last one
[09:14] <darkxst> autopkgtest coverage is minimal and only maybe a dozen packages have tests
[09:14] <darkxst> I have to pop out for dinner, will be back in a couple of hours
[09:15] <jbicha> I think most of GNOME does not really have tests?
[09:15] <darkxst> GNOME seem to be back tracking on the "installed tests" that enable autopkgtests
[09:16] <darkxst> yeh its a mixed bag when it comes to build time tests, some have very good coverage
[09:16] <darkxst> a lot have average/questionable coverage
[09:16] <darkxst> and some have minimal
[09:17] <darkxst> but certainly build time test coverage is much higher than what autopkgtests can do.
[09:17] <darkxst> anyway gtg, will be back
[09:17] <jbicha> ok, thanks
[11:34] <darkxst> jbicha, back