"Magnus Hagander" <magnus@hagander.net> writes:
>> If I remember correctly, after a few "where's this new release" snafus,
>> the order of the day now is to silently release the new version,
>> announcing it on -hackers only, until all the ftp mirrors have updated,
>> then to announce it publicly when all the copies have been made.
> correct. the wait is also for the official binary distributions to be packaged.
Yah. The actual process for the last few updates has involved wrapping
the "master source" tarballs on a Thursday evening with public
announcement the next Monday. This gives a couple of days for the RPM
and Windows packagers to do their thing, then another 24 hours or so
for the various mirrors to pick up the files before we announce. This
over-the-weekend schedule isn't set in concrete, but it seems to be
convenient for most of the packagers at the moment.
While there's no need to hide a simple bug-fix update, it's widely
considered important that security issues not become public before a fix
is available. This just-completed cycle was embarrassingly leaky, in
that there was a whole lot of unintended public evidence that a security
release was about to happen. We have all the policies and procedures in
place, but we seem to need a bit more practice at executing them...
regards, tom lane
