On Monday, October 31, 2016 9:54:37 AM CET Kevin Fenzi wrote: > > Note that this is not security-only. That's the reason for > > 'prepared-rpms' prefix, e.g. if we had something like that in Fedora, > > we could test/use this feature several times a year as we are > > informed by PostgreSQL upstream about upcoming releases, we have > > tarball in advance ... but now it is shame we are not able to > > announce updates immediately with upstream. We are not allowed to > > share the tarballs with upstream before announcement, of course. > > So whats the lag here there? they announce and it's an hour or two > until you have finished builds and submitted updates? Is an hour or two > really worth all this... complexity? It's ~1 hour in the best case, but that requires one of package maintainers is up&running during release time.. which is not very comfortable. Also the maintainer needs to be ready for failures, fix mistakes, etc. Considering we have several days time window for "production" package preparation, it is unnecessary rush post mortem. Whether is it worth implementing? Dunno. If the case I described is that rare across Fedora package set then I wish this became more standard. Pavel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
