Re: How to coordinate web team for security releases?
От | Stefan Kaltenbrunner |
---|---|
Тема | Re: How to coordinate web team for security releases? |
Дата | |
Msg-id | 45C78CB7.9090403@kaltenbrunner.cc обсуждение исходный текст |
Ответ на | Re: How to coordinate web team for security releases? (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-www |
Josh Berkus wrote: > Stefan, > >> well not that is closely related to the -www issue but the fix/patch >> will end up on anoncvs/viewcvs days before the release too (and will get >> published including the Security: tag and the commit message there and >> distributed to the buildfarm boxes at least). >> So to keep it really under the hood would probably be quite difficult to >> do. > > Actually, we were discussing mechanisms to change that on -core. Suggestions > are welcome. Mostly we just want to keep a tight lid on security expoloit > information until the day of release. yeah I understand the reasoning - but given the rather distributed nature of the postgresql infrastructure I guess it might be very difficult if not impossible to get down to less then 72 or 48 hours. One needs that time to commit the patch and probably wait for at least one round of buildfarm results, tag all the affected branches and build the tarballs and finally all the packagers need to build at least the most important binary packages. Stefan
В списке pgsql-www по дате отправления: