On 23.01.2016 04:07 PM, Mike DePaulo wrote: > Currently, Jenkins is building for the following versions of Fedora: > 19 > 20 > 21 > 22 > Rawhide (24) > > However, 19, 20 and 21 have all reached end-of-life. Fedora 21's EOL > was 2015-12-01. > > Unless there are any objections, I will disable builds for Fedora 19, > 20 and 21 next weekend.
We've been discussing this on a previous dev meeting. While these versions reached EOL, carrying them as long they do not break (and dropping them IF they break) causes no harm. On the pro side, if we were to disable them, we'd save about 30 minutes build time for each version. So far, these old versions haven't caused me a lot of pain and FC19 is actually a bit special, too, being the FC version EPEL6 was based upon. Sure, we could disable these builds, but does it help us any? Back then, I opted to keep them and the other seemed to be on board, because they are not causing additional maintenance or anything else. If you feel strongly about it, bring the discussion up again (mailing list shall be good enough, I guess, but other people might object...) I don't care one way or the other personally, keeping them vs. disabling them makes no difference for me. > I will also enable builds for 23 at that time. > > Enabling builds for 23 will probably consist of copying over > /etc/mock/*.cfg files from a working Fedora ( or EPEL) RPM because the > "mock" package in Debian is out-of-date and does not provide them. > This is how Mike#1 and I enabled builds for F21 and F22 in the 1st > place.[1] [2] NACK, please let me handle this. I've already replaced all mock config files once - because the Debian package only shipped outdated ones - with those from the mock upstream repository. Further, the config files need to be copied and other changes applied as well, so it's not a trivial replacement process. Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list [email protected] http://lists.x2go.org/listinfo/x2go-dev
