Summary/Minutes from today's FESCo Meeting (2015-01-07)

[Vít Ondruch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 14.1.2015 v 00:24 Dennis Gilmore napsal(a):
> On Tue, 13 Jan 2015 15:58:51 -0700
> Kevin Fenzi <kevin at scrye.com> wrote:
>
> > On Tue, 13 Jan 2015 15:50:06 -0700
> > Stephen John Smoogen <smooge at gmail.com> wrote:
>
> >> You forgot "too many packages?" There are 15842 packages in Fedora
> >> 21 and 16230 in Rawhide. That is a lot of packages that have to be
> >> rebuilt possibly multiple times due to FTBFS, multiple
> >> architectures, etc.
> >>
> >> 2.5 weeks is 25200 minutes. That means a mass rebuild is doing 0.6
> >> packages a minute across 3 architectures. That is pretty darn fast
>
> > The Fedora 21 mass rebuild took about 40 hours. ;)
>
> > That's really not the reason for more time, its the fallout from that.
> > When the mass rebuild is tagged in, sometimes there's things broken in
> > the build root, those need humans to look at and fix. Then, there are
> > all the packages that didn't build for whatever reason, those need
> > humans to look at them and fix them up. The ones with broken deps need
> > fixing, etc.
>
> > So, while the mass rebuild itself is less than 2 days, it takes a
> > while to stablize things after that. If we branched right after the
> > mass rebuild we would have to then stablize both rawhide and f22.
>
> > It's hard to say how much time we really need there... it depends on
> > how much stuff got broken, how hard it is to fix and how much time
> > maintainers have to fix things.
>
> right. in the past the building took around a week or a bit more, we
> have gotten that down. which is why I said we could drop the 4 weeks to
> 3. the time consuming part is the cleanup and fixing of issues. that
> needs people. If everything is perfect a week could well be sufficient.
> Ideally we want secondary arches to be done in the window as well.
> just to make sure that there is no fallout on them requiring a second
> rebuild. which could also happen on primary. we have had ABI issues etc
> in the past on all arches.
>
> Dennis

What I would love to see is to leave out the packages which are build in
side tag from mass rebuild.

E.g. if I have side tag for Ruby, I rebuild every package in the side
tag in two weeks before mass rebuild, I can hardly see any justification
to build them once again (unless there lands gcc in the man time or
something like this). So if you could exclude the packages which are
already build in side tag from mass rebuild, it would help you with
following merge and it would give me additional time to rebuild Ruby
packages.

Is something like this feasible?



Vít
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUtjtgAAoJEAzgnueZF7h8FNAP/R+qxtq1XEJcK1MakXamiVhy
DDjjgOEgBaHchx2lVRKQbslq8K1Uk7X/gryLu/YD88z+4umoAyXFoD/6RTHQmJct
6YEFndsKToJqtVuQ2Mmx8PxjtruVvaZs37DOZ8bw+KP2QSC4CvWaOmGB4SN2xcSv
IPPAz1YHSV7TGnQWXDemVP7OHEfhkiPRkI+B4MXUGkwj3bgZOoFZFxOFCOfSs7nQ
2zFe9aCPktDsIBr99aO0BzICiCKsJRzZmxh+rplTR6uvvO2LzPBeEeiUY/nQh/Dh
Rp4Yl0xuM9wYXzG/ewzcqJ/1++Wz/EibsVhO3ZgrzLcajjHd0Ie421MB31YqW1EF
/Z06rTr9iaCudAkmiMO4jPvXr692XO6vHrTQL6THMbA0nK4SiI/lnu2Kkn5qXf5M
O26KgYZ8aXSgJiIcW/W9rPO2zq5FgR1EGJPdcuP7LNobfIUX+58tkjtnuhYOWuKB
6H3923VOHJws39PRIrd0Upoh+ZJkxobotsYUCgMplOJR+XKY8/7DaHr+J8eKNKOn
PeVsCiZR1E73wQqCTf01Aj5GaY/0Fumwb76cQW4tbvfVuFJD6qY3gr6PTSC2pkFo
LccTorT+zrAu0EI9tIKgb0MZ1ih+tQ7x8QZvm1rrxxh7RH6A+5qNlxEvla7S7WsJ
+YeUbwHbvjZlLFUHJUOu
=p/dY
-----END PGP SIGNATURE-----