From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | jd(at)commandprompt(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 8.4 release planning |
Date: | 2009-01-27 06:05:54 |
Message-ID: | 162867790901262205m2df345afp1cd0482d8ee7a989@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/1/27 Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>:
> On Tue, Jan 27, 2009 at 12:40 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> so it could be released. 8.5 should be implemented in shorted
>> cycle - only one commitfest, that is enough (+3 month) for well
>> completing SE and replication patches.
>
> we tried this before (8.2 to 8.3 i think), the idea was that the next
> release should be in 6 months... we release at least 6 months later...
>
> ATM that a new release cycle starts new patch will arrive and there
> will be no way to get the shorted release in time...
>
I remember it. Solution is - don't accept new patches for next commitfest.
Pavel
> --
> Atentamente,
> Jaime Casanova
> Soporte y capacitación de PostgreSQL
> Asesoría y desarrollo de sistemas
> Guayaquil - Ecuador
> Cel. +59387171157
>
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2009-01-27 06:09:19 | Re: Meridiem markers (was: [BUGS] Incorrect "invalid AM/PM string" error from to_timestamp) |
Previous Message | Jaime Casanova | 2009-01-27 05:58:28 | Re: 8.4 release planning |