On Fri, 2009-09-18 at 10:22 -0700, Josh Berkus wrote:
> Bruce,
>
> >> CF17/15 to 8/14
> >> Alpha1 by 8/20
> >> CF29/15 to 10/14
> >> Alpha2 by 10/20
> >> CF311/15 to 12/14
> >> Alpha3 by 11/20
> >> CF41/15 to 2/14
> >> Alpha4 by 2/20
> >> Beta1 est
Josh Berkus wrote:
> Bruce,
>
> >> CF17/15 to 8/14
> >> Alpha1 by 8/20
> >> CF29/15 to 10/14
> >> Alpha2 by 10/20
> >> CF311/15 to 12/14
> >> Alpha3 by 11/20
> >> CF41/15 to 2/14
> >> Alpha4 by 2/20
> >> Beta1 est. 3/1 to 3/7
> >> Release June, dep
Bruce,
>> CF1 7/15 to 8/14
>> Alpha1 by 8/20
>> CF2 9/15 to 10/14
>> Alpha2 by 10/20
>> CF3 11/15 to 12/14
>> Alpha3 by 11/20
>> CF4 1/15 to 2/14
>> Alpha4 by 2/20
>> Beta1est. 3/1 to 3/7
>> Release June, depending on bugs
>
> I think that June release date is reali
Josh Berkus wrote:
> Hackers,
>
> Per discussions on two other threads on this list which have apparently
> reached consensus, we will be going with the following schedule:
>
> CF1 7/15 to 8/14
> Alpha1by 8/20
> CF2 9/15 to 10/14
> Alpha2by 10/20
> CF3 11/15 to 12/14
> Alpha
On Wed, Sep 2, 2009 at 10:22 PM, Josh Berkus wrote:
> Robert,
>
>> A. Update the status of patches on the wiki (because the patch authors
>> and reviewers often didn't).
>> B. Poke reviewers or patch authors who didn't respond in a timely
>> fashion and/or move to "Returned with Feedback".
>> C. As
Robert,
> A. Update the status of patches on the wiki (because the patch authors
> and reviewers often didn't).
> B. Poke reviewers or patch authors who didn't respond in a timely
> fashion and/or move to "Returned with Feedback".
> C. Assign new patches to reviewers who requested them.
> D. Send
On Wed, Sep 2, 2009 at 9:31 PM, Josh Berkus wrote:
> Robert,
>
>> I would like to propose an additional stipulation on CF4 - namely,
>> that we will reject out of hand any large patches that were not
>> submitted to CF3. For the sake of definiteness, let's say that a
>> large patch is anything whe
Robert,
> I would like to propose an additional stipulation on CF4 - namely,
> that we will reject out of hand any large patches that were not
> submitted to CF3. For the sake of definiteness, let's say that a
> large patch is anything whether diffstat run against the unified diff
> shows lines a
On Wed, Sep 2, 2009 at 7:42 PM, Josh Berkus wrote:
> Hackers,
>
> Per discussions on two other threads on this list which have apparently
> reached consensus, we will be going with the following schedule:
>
> CF1 7/15 to 8/14
> Alpha1 by 8/20
> CF2 9/15 to 10/14
> Alpha2 by 10/20
> CF3
On Sep 2, 2009, at 4:42 PM, Josh Berkus wrote:
CF3 11/15 to 12/14
Alpha3 by 11/20
12/20?
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hackers,
Per discussions on two other threads on this list which have apparently
reached consensus, we will be going with the following schedule:
CF1 7/15 to 8/14
Alpha1 by 8/20
CF2 9/15 to 10/14
Alpha2 by 10/20
CF3 11/15 to 12/14
Alpha3 by 11/20
CF4 1/15 to 2/14
Alpha4 by 2/2
11 matches
Mail list logo
