Обсуждение: PostgreSQL release schedule
Hi, Does anyone know if there is a publicly available release schedule for upcoming versions of PostgreSQL along with proposed new functionality? In a month or so I'm going to start on updating an app from Pg7.1 and would like to know if should start writing for Pg8.0 or if 8.1 is around the corner and if it has any features that would benefit the app. Thanks, James
On Tue, 2005-05-24 at 08:37, James Croft wrote: > Hi, > > Does anyone know if there is a publicly available release schedule for > upcoming versions of PostgreSQL along with proposed new functionality? > > In a month or so I'm going to start on updating an app from Pg7.1 and > would like to know if should start writing for Pg8.0 or if 8.1 is around > the corner and if it has any features that would benefit the app. The closest thing to a "roadmap" would be the TODO list. See: http://www.postgresql.org/docs/faqs.TODO.html The TODO list isn't necessarily tied to anyone's timeline though, so there may be things in there that are year old and may not get implemented soon, if ever. The average time between releases has historically been about 1 year, plus a few months here and there. That time is likely to get longer, not shorter, as PostgreSQL matures and features being added touch more of the code base, hence require more time to code and to test. I'd go for 8.0. It's quite stable now, and 8.1 will take as long as it needs to take to come out, which could be anything, but will likely be no earlier than the end of the year. I believe there was talk about an 8.1 coming out to replace the caching algorithm, but I believe the change was implemented in 8.0.3 or something like that, so there's no need to push out an 8.1 release.
Scott Marlowe wrote: > I'd go for 8.0. It's quite stable now, and 8.1 will take as long as it > needs to take to come out, which could be anything, but will likely be > no earlier than the end of the year. > > I believe there was talk about an 8.1 coming out to replace the caching > algorithm, but I believe the change was implemented in 8.0.3 or > something like that, so there's no need to push out an 8.1 release. Thanks Scott.
On Tue, 24 May 2005, James Croft wrote: > Scott Marlowe wrote: >> I'd go for 8.0. It's quite stable now, and 8.1 will take as long as it >> needs to take to come out, which could be anything, but will likely be >> no earlier than the end of the year. >> >> I believe there was talk about an 8.1 coming out to replace the caching >> algorithm, but I believe the change was implemented in 8.0.3 or >> something like that, so there's no need to push out an 8.1 release. > > Thanks Scott. Estimate right now for going beta on 8.1 is July 1st ... aiming for a Sep/Oct release ... if you've been around long enough, you'll know how fluid our 'estimates' tend to be, but that is our current goal ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
On Tue, May 24, 2005 at 19:31:28 -0300, "Marc G. Fournier" <scrappy@postgresql.org> wrote: > On Tue, 24 May 2005, James Croft wrote: > > >Scott Marlowe wrote: > >>I'd go for 8.0. It's quite stable now, and 8.1 will take as long as it > >>needs to take to come out, which could be anything, but will likely be > >>no earlier than the end of the year. > >> > >>I believe there was talk about an 8.1 coming out to replace the caching > >>algorithm, but I believe the change was implemented in 8.0.3 or > >>something like that, so there's no need to push out an 8.1 release. > > > >Thanks Scott. > > Estimate right now for going beta on 8.1 is July 1st ... aiming for a Isn't that feature freeze? Typically there has been a month between feature freeze and the first official beta. > Sep/Oct release ... if you've been around long enough, you'll know how > fluid our 'estimates' tend to be, but that is our current goal ... With a July 1 feature freeze, Nov/Dec is a much better estimate of when there might be an 8.1 release. Even that is on the optimistic side.
On Tue, 24 May 2005, Bruno Wolff III wrote: > On Tue, May 24, 2005 at 19:31:28 -0300, > "Marc G. Fournier" <scrappy@postgresql.org> wrote: >> On Tue, 24 May 2005, James Croft wrote: >> >>> Scott Marlowe wrote: >>>> I'd go for 8.0. It's quite stable now, and 8.1 will take as long as it >>>> needs to take to come out, which could be anything, but will likely be >>>> no earlier than the end of the year. >>>> >>>> I believe there was talk about an 8.1 coming out to replace the caching >>>> algorithm, but I believe the change was implemented in 8.0.3 or >>>> something like that, so there's no need to push out an 8.1 release. >>> >>> Thanks Scott. >> >> Estimate right now for going beta on 8.1 is July 1st ... aiming for a > > Isn't that feature freeze? Typically there has been a month between > feature freeze and the first official beta. True, sorry, you are correct in that the aim is a Feature Freeze for July 1st, Beta for Aug 1st, and Release for Sep/Oct ... Again, that will vary, as we all know ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Bruno Wolff III <bruno@wolff.to> writes:
> "Marc G. Fournier" <scrappy@postgresql.org> wrote:
>> Estimate right now for going beta on 8.1 is July 1st ... aiming for a
> Isn't that feature freeze? Typically there has been a month between
> feature freeze and the first official beta.
Right, the only definite target at the moment is feature freeze 7/1.
We'll go beta as soon thereafter as any obvious issues have been shaken
out. After that, the traditional policy for beta->final is "we release
when it's ready".
> With a July 1 feature freeze, Nov/Dec is a much better estimate of when
> there might be an 8.1 release. Even that is on the optimistic side.
I'd like to think it's not optimistic --- but yeah, Thanksgiving-ish is
a reasonable bet. If beta goes really well it could be a month or so
earlier, but then again it could be later too.
regards, tom lane
On Tuesday 24 May 2005 23:49, Tom Lane wrote:
> Bruno Wolff III <bruno@wolff.to> writes:
> > "Marc G. Fournier" <scrappy@postgresql.org> wrote:
> >> Estimate right now for going beta on 8.1 is July 1st ... aiming for a
> >
> > Isn't that feature freeze? Typically there has been a month between
> > feature freeze and the first official beta.
>
> Right, the only definite target at the moment is feature freeze 7/1.
> We'll go beta as soon thereafter as any obvious issues have been shaken
> out.
> <snip>
> I'd like to think it's not optimistic --- but yeah, Thanksgiving-ish is
> a reasonable bet.
Perhaps we should add a couple of lines to the TODO stating that feature
freeze is planned for july 1 and give estimated times for phases to follow?
This could help people to determine how feasible working on given items might
be for the current or a future development branches
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
On Wed, 25 May 2005, Robert Treat wrote: > On Tuesday 24 May 2005 23:49, Tom Lane wrote: >> Bruno Wolff III <bruno@wolff.to> writes: >>> "Marc G. Fournier" <scrappy@postgresql.org> wrote: >>>> Estimate right now for going beta on 8.1 is July 1st ... aiming for a >>> >>> Isn't that feature freeze? Typically there has been a month between >>> feature freeze and the first official beta. >> >> Right, the only definite target at the moment is feature freeze 7/1. >> We'll go beta as soon thereafter as any obvious issues have been shaken >> out. >> <snip> >> I'd like to think it's not optimistic --- but yeah, Thanksgiving-ish is >> a reasonable bet. > > Perhaps we should add a couple of lines to the TODO stating that feature > freeze is planned for july 1 and give estimated times for phases to > follow? This could help people to determine how feasible working on > given items might be for the current or a future development branches I'd almost think taht this shuld be much more prominently put in a section on the main page of the web site, actually ... make it nice and visible instead of buried on a sub page ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote: > > I'd almost think taht this shuld be much more prominently put in a > section on the main page of the web site, actually ... make it nice and > visible instead of buried on a sub page ... > I agree it would be good to have a link on the main page. Possibly near "What's new in current_version" to have a link to 'coming up in our next release' or something similar. Just my $0.02, I know where the todo page is now. :)
Robert Treat wrote: > On Tuesday 24 May 2005 23:49, Tom Lane wrote: > > Bruno Wolff III <bruno@wolff.to> writes: > > > "Marc G. Fournier" <scrappy@postgresql.org> wrote: > > >> Estimate right now for going beta on 8.1 is July 1st ... aiming for a > > > > > > Isn't that feature freeze? Typically there has been a month between > > > feature freeze and the first official beta. > > > > Right, the only definite target at the moment is feature freeze 7/1. > > We'll go beta as soon thereafter as any obvious issues have been shaken > > out. > > <snip> > > I'd like to think it's not optimistic --- but yeah, Thanksgiving-ish is > > a reasonable bet. > > Perhaps we should add a couple of lines to the TODO stating that feature > freeze is planned for july 1 and give estimated times for phases to follow? > This could help people to determine how feasible working on given items might > be for the current or a future development branches I am thinking that should be the web site or a news item, rather than the TODO list itself. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073