[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[scl.org] Minutes from CentOS SCLo SIG sync-up meeting on #centos-devel (2016-01-27)



* tags for new collections ruby, ror, python and maven created:
https://bugs.centos.org/view.php?id=10256

* we agreed to use scl-httpd24-mod_auth_mellon for the mod_auth_mellon, extending httpd24 SCL (related to https://www.redhat.com/archives/sclorg/2016-January/msg00068.html)
  we should write this up as there will be more extended SCLs for sure
  #action alphacc extend cbs doc about sclo SIG tags

* hhorak to update the "Gaining Access to SCLs" section and link the "Available Collections" to the SCLo page (https://wiki.centos.org/AdditionalResources/Repositories/SCL)

* hhorak to update http://wiki.centos.org/SpecialInterestGroup/SCLo, mentioning sclorg-distgit repos as interim solution

* status of CI tests: seems to mostly be there now
  link https://ci.centos.org/view/SCLo/
  just sclo-vagrant1 is failing

* sclo-ror42 is built into -candidate tags for el6/7

* newer gcc for gcc-go in virt7-docker* repos -- virt7-docker should be able to inherit devtoolset-4 repos

* we need some workflow for the testing => release; it will technically the same than testing, tag the package, as request for repo to be populated, so it is more about policy RemiFedora will write up something like we have in Fedora -- if no problem found, then a week or two for testing the period should probably start by announcing the packages' availability on the centos-devel + sclorg ML (centos-announce is meant for end user announcements only)

Honza


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]