Brian, does this applies for PaaS Sig too ? Asking as i may have few rpms ready to be pushed next week to mirror.c.o assuming no bad news from testing side. If it does apply to us to then i'm okay with, i'd only ask how long the freeze normally takes ? cheers. On Thu, Nov 1, 2018 at 3:29 PM Brian Stinson <brian at bstinson.com> wrote: > Hi Folks, > > As is usual, we freeze the SIG Sign + Push process as part of preparing > for a point release. > > This helps us once CR is ready (it isn't yet, though) so that we can > seed it quickly in CBS to build against. > > The Point-release Freeze does not affect content moving from the testing > tags in CBS to buildlogs.c.o, that will continue to show up as it is > built. Do note: since we do want to give testers and developers an > opportunity to build and test against an upcoming point-release before > it goes GA, content coming from buildlogs.centos.org may require > enabling the CR repo once it's ready. > > Any new requests for sign+push (adding new tags to mirror.c.o) during > Point-release Freeze will be held until the point release goes GA. > > If there are any questions, please let us know and discuss here on the > list. > > Cheers! > > -- > Brian Stinson > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20181101/9cb82f98/attachment-0008.html>