Hi,
I would like to apply for an exception for this freeze for a new release of Autocloud, and we will re-evaluate for F24-alpha. Autocloud is a new application in the infrastructure, and not yet consumed by any other service.
This release contains only one update [1] which is required so that next generation rel-eng tools can be written.
[1] https://github.com/kushaldas/autocloud/issues/17
Kushal
+1 for a blanket FBR for this release cycle, since it's not used anywhere. I think we could have marked them as unfrozen for now, but since we're already in freeze and we will use it for F24, blanket FBR +1.
With kind regards, Patrick Uiterwijk Fedora Infra
----- Original Message -----
Hi,
I would like to apply for an exception for this freeze for a new release of Autocloud, and we will re-evaluate for F24-alpha. Autocloud is a new application in the infrastructure, and not yet consumed by any other service.
This release contains only one update [1] which is required so that next generation rel-eng tools can be written.
[1] https://github.com/kushaldas/autocloud/issues/17
Kushal
Fedora Cloud Engineer CPython Core Developer CentOS Cloud SIG lead http://kushaldas.in _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/infrastructure@lists.fedoraproject.org
On Thu, Oct 15, 2015 at 01:23:42PM +0530, Kushal Das wrote:
Hi,
I would like to apply for an exception for this freeze for a new release of Autocloud, and we will re-evaluate for F24-alpha. Autocloud is a new application in the infrastructure, and not yet consumed by any other service.
This release contains only one update [1] which is required so that next generation rel-eng tools can be written.
+1 for me for a blanket freeze exception just for this freeze and because it's a new service that isn't consumed by anything currently.
Pierre
infrastructure@lists.fedoraproject.org