On 03/04/2013 08:11, damien clochard wrote:
> Among these questions, the 3 below are recurring :
>
> Which companies have access to the patch before the official release
> ? What does a company have to do to have access to this patch ? Who
> decides to allow this "early access" ?
While no-one seems to address these questions - here's my opinion,
1. An issue is found, a solution is developed and committed to source
code repository.
2. Source is downloaded and compiled by release build servers.
3. Official release binaries are made available to download.
Once 1 is complete an announcement of upcoming release can be made.
There is a delay till release as the release builds are being compiled.
After 1. is complete anyone can download and build their own fixed
version of postgresql.
If an announcement is made after 1 then there is a delay that anyone can
use to build their own update before the *official release*
If an announcement is made after 3 then anyone also following the
development can also release their own updates before the official
announcement.
That's a benefit of open source.
There is no preference given to special customers.
Those that care and pay attention can look after their customers as
they see fit.