Re: Ready to branch 7.2/7.3 ? - Mailing list pgsql-hackers

From Greg Copeland
Subject Re: Ready to branch 7.2/7.3 ?
Date
Msg-id 1014061088.20383.24.camel@mouse.copelandconsulting.net
Whole thread Raw
In response to Re: Ready to branch 7.2/7.3 ?  ("Marc G. Fournier" <scrappy@hub.org>)
List pgsql-hackers
I guess I jumped the gun in my previous message as I hadn't read this
one yet.  I completely agree with Marc on this topic.  What is the logic
for simply not snap-shoting what really is 7.2 and move on with 7.3
while allowing 7.2.x to occur on the branch for migration on a later
day?

Has this been problematic in the past?

Greg


On Fri, 2002-02-15 at 22:56, Marc G. Fournier wrote:
>
> We're planning on ... this is a 'sore point' that I've been arguing for
> several releases yet ... I still feel the branch should be made *on
> release date* and not several weeks later ... I think this is the first
> release where we will do the branch prior to the minor being released, so,
> I guess, as time goes on, we'll get closer to what I've wanted for ages :)
>
>
>
> On Sat, 16 Feb 2002, Justin Clift wrote:
>
> > "Marc G. Fournier" wrote:
> > >
> > > On Fri, 15 Feb 2002, Bruce Momjian wrote:
> > >
> > > > Tom Lane wrote:
> > > > > "Marc G. Fournier" <scrappy@hub.org> writes:
> > > > > > Okay, if the ecpg is the only issue, does everyone feel comfortable with a
> > > > > > branch going in this evening?  I'll do a v7.2.1 tar-ball up Sunday night
> > > > > > based on the branch, with an announce going out on Monday?
> > > > >
> > > > > I don't think it's time for 7.2.1 quite yet; we should probably wait
> > > > > another week or two to see what comes in.  I just want to branch now...
> > > >
> > > > Agreed.  Let's get everything we can into 7.2.1.  We normally don't push
> > > > out a minor this quickly unless we have a major thing to fix, which we
> > > > don't.
> > >
> > > Right, and we never branch until we're ready for the first minor ... so
> > > ...
> >
> > Hang on here.  It sounds like we're following previous methodology to
> > our (possible) slight detriment here.
> >
> > At present, we need 7.3 to start, so that people can begin working on
> > it.
> >
> > We also need to have the 7.2 branch, so stuff for the to-be 7.2.x can be
> > included there where appropriate.
> >
> > So, lets get it branched, because that's what needs to be done here and
> > now, in this instance.
> >
> > Then people with a burn to do 7.3 stuff can do so, and things can be
> > added to 7.2.x where needed.
> >
> > :-)
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> >
> >
> > >
> > > ---------------------------(end of broadcast)---------------------------
> > > TIP 6: Have you searched our list archives?
> > >
> > > http://archives.postgresql.org
> >
> > --
> > "My grandfather once told me that there are two kinds of people: those
> > who work and those who take the credit. He told me to try to be in the
> > first group; there was less competition there."
> >    - Indira Gandhi
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly


pgsql-hackers by date:

Previous
From: Greg Copeland
Date:
Subject: Re: Ready to branch 7.2/7.3 ?
Next
From: "Rod Taylor"
Date:
Subject: Re: Serious 7.2 issue (non quiet string truncation)