Bruce Momjian said:
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Tom Lane wrote:
If this were an ordinary devel cycle then I'd be fine with it
running a year, but I think we really do need to plan for a shorter
than normal cycle so we can clean up 8.0 kinks in a
YES! Yes yes yes! I try to plan my time, and the feature freeze data is very
important in that planning.
This is also important for people considering sponsoring developers.
Also, regardless of the issues Tom raised, 18 months is too long a release
cycle, IMNSHO. If you do that and you take
Tom,
Well, if you take the summer-vacation argument seriously, then nothing
will get done between May and September anyway, so we may as well freeze
in May ;-)
I'd be happy with saying June 1.
Hey, you and Bruce are the ones who'll get stuck with all the code checking if
nobody else is
Josh Berkus josh@agliodbs.com writes:
I thought we were trying to get away from a midsummer feature freeze, due to
the general lack of personnel in that season?
...
So I'd advocate either freezing in May, or in September.
Well, if you take the summer-vacation argument seriously, then nothing
On Fri, 25 Feb 2005, Josh Berkus wrote:
Also, what do you think of Simon's plan for a 2-stage feature freeze?
Maybe not so far apart ... maybe a month apart?
I missed that ... could you re-summarize?
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL
On Fri, 25 Feb 2005, Tom Lane wrote:
Josh Berkus josh@agliodbs.com writes:
I thought we were trying to get away from a midsummer feature freeze, due to
the general lack of personnel in that season?
...
So I'd advocate either freezing in May, or in September.
Well, if you take the summer-vacation
Josh Berkus josh@agliodbs.com writes:
Also, what do you think of Simon's plan for a 2-stage feature freeze? Maybe
not so far apart ... maybe a month apart?
I didn't feel a need for it. It's true that the closer we get to
feature freeze, the smaller the patch you should expect to drop on us
Marc,
I missed that ... could you re-summarize?
Sure, Simon proposed that we have a feature freeze for major features (like
bitmapped indexes and 2PC) before the feature freeze for minor
features (like new system views). The reason being that the major features
need a lot more code
Marc G. Fournier [EMAIL PROTECTED] writes:
Josh Berkus josh@agliodbs.com writes:
I thought we were trying to get away from a midsummer feature freeze, due to
the general lack of personnel in that season?
I concur with Josh on this ... that kinda wastes the 'two months of
summer' when ppl
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Josh Berkus josh@agliodbs.com writes:
I thought we were trying to get away from a midsummer feature freeze, due
to
the general lack of personnel in that season?
I concur with Josh on this ... that kinda wastes the 'two months
Bruce Momjian pgman@candle.pha.pa.us writes:
Tom Lane wrote:
If this were an ordinary devel cycle then I'd be fine with it running a
year, but I think we really do need to plan for a shorter than normal
cycle so we can clean up 8.0 kinks in a reasonably timely fashion.
Let's see how much 8.0
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Tom Lane wrote:
If this were an ordinary devel cycle then I'd be fine with it running a
year, but I think we really do need to plan for a shorter than normal
cycle so we can clean up 8.0 kinks in a reasonably timely fashion.
Please could we have a development schedule page on the web site...?
The information it should contain would be like this (and others)
Current Development Release: (Coordinator: Bruce Momjian)
8.0:Beta1, released 2 August 2004
Beta2, deadline 2 September 2004
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Please could we have a development schedule page on the web site...?
You haven't been around here long, have you? There is no schedule.
The page would spend most of its time looking like
Current Development Release: (Coordinator: Bruce Momjian)
Tom Lane
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Please could we have a development schedule page on the web site...?
You haven't been around here long, have you?
Gee, Tom, you noticed? What gave it away? :)
(I wasn't in a legal position to contribute before late 2003 - binding IP
On Friday 13 August 2004 19:37, Tom Lane wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Please could we have a development schedule page on the web site...?
You haven't been around here long, have you? There is no schedule.
The page would spend most of its time looking like
Current
Robert Treat [EMAIL PROTECTED] writes:
Not sure how much more useful this is, but generally the first RC goes out
once all the open items are dealt with. Also doc freeze is generally
expected at RC1 time (though errors in the docs are still acceptable fixes
for subsequent RC's)
Actually
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I see this: there is no PUBLISHED schedule, there probably is no AGREED
schedule, but everybody's working to some reasonable working assumptions
which mean that there is in fact an IMPLICIT schedule. (Whether or not that
changes over time)
Well, if
18 matches
Mail list logo
