If it can help, it's really very little work for me to send the hammer SRPM to our Koji build system. I think the real work will come if people starting asking for jewel builds on el6 and other old platforms. In that case, if a reputable organisation offers to maintain the builds (+ deps), then IMHO ceph.com should just link to them. Copying to ceph.com might give a false sense of security in this case. -- Dan On Mon, Feb 29, 2016 at 5:10 PM, Loic Dachary <loic@xxxxxxxxxxx> wrote: > I've created a pad at http://pad.ceph.com/p/development-releases for the next CDM ( see http://tracker.ceph.com/projects/ceph/wiki/Planning for details). > > On 29/02/2016 22:49, Nathan Cutler wrote: >> The basic idea is to copy the packages that are build by gitbuilders or by the buildpackage teuthology task in a central place. Because these packages are built, for development versions as well as stable versions[2]. And they are tested via teuthology. The packages that are published on http://ceph.com/ are rebuilt from scratch, using the process that Alfredo described. This is fine for the supported platforms and for the stable releases. But for the development releases and the platforms that are no longer supported but still built by gibuilders, we could just copy the packages over. > > -- > Loïc Dachary, Artisan Logiciel Libre -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
