Update releases
Folks,
Now that there's a (very minor) crypto fix and a new DST ruleset, when
can we get the next set of minor revs out the door?
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
On 1 July 2011 23:57, David Fetter <david@fetter.org> wrote:
Folks,
Now that there's a (very minor) crypto fix and a new DST ruleset, when
can we get the next set of minor revs out the door?
Do we know how many identified bugs are still outstanding? There's at
least the SSPI issue for which a patch has been submitted and requires
review, commit and back-patching.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Jul 01, 2011 at 11:59:55PM +0100, Thom Brown wrote:
On 1 July 2011 23:57, David Fetter <david@fetter.org> wrote:
Folks,
Now that there's a (very minor) crypto fix and a new DST ruleset, when
can we get the next set of minor revs out the door?Do we know how many identified bugs are still outstanding? There's at
least the SSPI issue for which a patch has been submitted and requires
review, commit and back-patching.
I'm thinking whatever such bugs are outstanding can wait until the
next minor rev, which is to say that the CVE involved with that crypto
fix should take precedence. I know it's minor, but a known-unfixed
access control bug looks very bad, no matter how trivial that bug is.
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate