

> -----Original Message-----
> From: Marc G. Fournier [mailto:scrappy@hub.org] 
> Sent: 18 December 2002 14:51
> To: Robert Treat
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] v7.3.1 tar ready ... please check it ...
> 
> 
> On Wed, 18 Dec 2002, Robert Treat wrote:
> 
> > Is this going to be announced to a wider press audience? Has anyone 
> > gone over the "list of things to do when we release" to make sure 
> > things like the websites getting updated or perhaps getting 
> rpm builds 
> > coordinated has been done?
> 
> No, we don't do that with minor releases ... nothing has 
> changed that needs to be announced, other then a few bugs fixed ...

Maybe we should? The more publicity the better etc...

Regards, Dave

Wed, 18 Dec 2002 14:53:28 -0000
"Dave Page" <dpage@vale-housing.co.uk>
Re: v7.3.1 tar ready ... please check it ...
On Wed, 18 Dec 2002, Dave Page wrote:

>
>
> > -----Original Message-----
> > From: Marc G. Fournier [mailto:scrappy@hub.org]
> > Sent: 18 December 2002 14:51
> > To: Robert Treat
> > Cc: pgsql-hackers@postgresql.org
> > Subject: Re: [HACKERS] v7.3.1 tar ready ... please check it ...
> >
> >
> > On Wed, 18 Dec 2002, Robert Treat wrote:
> >
> > > Is this going to be announced to a wider press audience? Has anyone
> > > gone over the "list of things to do when we release" to make sure
> > > things like the websites getting updated or perhaps getting
> > rpm builds
> > > coordinated has been done?
> >
> > No, we don't do that with minor releases ... nothing has
> > changed that needs to be announced, other then a few bugs fixed ...
>
> Maybe we should? The more publicity the better etc...

The problem is that there is nothing to announce ... "Hi, we fixed some
bugs"? :)  minor releases don't have any features added to them, so isn't
really news worthy ... :(

Wed, 18 Dec 2002 11:25:32 -0400 (AST)
"Marc G. Fournier" <scrappy@hub.org>
Re: v7.3.1 tar ready ... please check it ...
On Wed, 18 Dec 2002, Marc G. Fournier wrote:

> On Wed, 18 Dec 2002, Dave Page wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: Marc G. Fournier [mailto:scrappy@hub.org]
> > > Sent: 18 December 2002 14:51
> > > To: Robert Treat
> > > Cc: pgsql-hackers@postgresql.org
> > > Subject: Re: [HACKERS] v7.3.1 tar ready ... please check it ...
> > >
> > >
> > > On Wed, 18 Dec 2002, Robert Treat wrote:
> > >
> > > > Is this going to be announced to a wider press audience? Has anyone
> > > > gone over the "list of things to do when we release" to make sure
> > > > things like the websites getting updated or perhaps getting
> > > rpm builds
> > > > coordinated has been done?
> > >
> > > No, we don't do that with minor releases ... nothing has
> > > changed that needs to be announced, other then a few bugs fixed ...
> >
> > Maybe we should? The more publicity the better etc...
>
> The problem is that there is nothing to announce ... "Hi, we fixed some
> bugs"? :)  minor releases don't have any features added to them, so isn't
> really news worthy ... :(
>

I think changing major version of libpq is an important thing to be
mentioned.


> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83


Wed, 18 Dec 2002 18:45:52 +0300 (MSK)
Oleg Bartunov <oleg@sai.msu.su>
Re: v7.3.1 tar ready ... please check it ...
On Wed, 18 Dec 2002, Marc G. Fournier wrote:

> The problem is that there is nothing to announce ... "Hi, we fixed some
> bugs"? :)  minor releases don't have any features added to them, so isn't
> really news worthy ... :(

I don't know, if you're a postgresql user and you don't read these lists, 
you might find out about a bug in a release note and upgrade when you 
otherwise might not.

www.linuxtoday.com has weekly updates from many gnu / OSS projects which 
are far less interesting than our 7.3.1 release is.  I could see posting a 
minor upgrade release notice there and on other OSS news web site 
(freshmeat, slashdot, etc...)


Wed, 18 Dec 2002 08:54:51 -0700 (MST)
"scott.marlowe" <scott.marlowe@ihs.com>
Re: v7.3.1 tar ready ... please check it ...
On Wed, 18 Dec 2002, scott.marlowe wrote:

> On Wed, 18 Dec 2002, Marc G. Fournier wrote:
>
> > The problem is that there is nothing to announce ... "Hi, we fixed some
> > bugs"? :)  minor releases don't have any features added to them, so isn't
> > really news worthy ... :(
>
> I don't know, if you're a postgresql user and you don't read these lists,
> you might find out about a bug in a release note and upgrade when you
> otherwise might not.
>
> www.linuxtoday.com has weekly updates from many gnu / OSS projects which
> are far less interesting than our 7.3.1 release is.  I could see posting a
> minor upgrade release notice there and on other OSS news web site
> (freshmeat, slashdot, etc...)

Okay, that I agree on ... note that my press list contains alot more then
that, most of which wouldn't be appropriate for a minor release ... maybe
we need to setup a seperate 'minor release' list?

Please note, I have no problems sending it out to a bunch of email
addresses, I'm just questioning whether it makes sense to do so ...
freshmeat not withstanding, since I don't see it as much of an annoucne
site as a centralized list of OSS software ...



Wed, 18 Dec 2002 11:58:29 -0400 (AST)
"Marc G. Fournier" <scrappy@hub.org>
Re: v7.3.1 tar ready ... please check it ...
scott.marlowe wrote:
> On Wed, 18 Dec 2002, Marc G. Fournier wrote:
> 
> 
>>The problem is that there is nothing to announce ... "Hi, we fixed some
>>bugs"? :)  minor releases don't have any features added to them, so isn't
>>really news worthy ... :(
> 
> 
> I don't know, if you're a postgresql user and you don't read these lists, 
> you might find out about a bug in a release note and upgrade when you 
> otherwise might not.
> 
> www.linuxtoday.com has weekly updates from many gnu / OSS projects which 
> are far less interesting than our 7.3.1 release is.  I could see posting a 
> minor upgrade release notice there and on other OSS news web site 
> (freshmeat, slashdot, etc...)

At the very least the PostgreSQL website team should be loudly notified so we can confirm the needed links have been 
updated prior to the release announcement.

It probably wouldn't hurt to go through a proper release process, but determine which steps are optional or not needed 
for smaller releases.

:-)

Regards and best wishes,

Justin clift

-- 
"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


Thu, 19 Dec 2002 03:05:04 +1100
Justin Clift <justin@postgresql.org>
Re: v7.3.1 tar ready ... please check it ...
On 18 Dec 2002 at 8:54, scott.marlowe wrote:
> 
> www.linuxtoday.com has weekly updates from many gnu / OSS projects which 
> are far less interesting than our 7.3.1 release is.  I could see posting a 
> minor upgrade release notice there and on other OSS news web site 
> (freshmeat, slashdot, etc...)

I read linuxtoday and /. daily. Linuxtoday is OK but /. would be an almost 
waste of another 800 comments of postgresql v/s mysql.

Just a thought..

Bye
 Shridhar

--
Manly's Maxim:	Logic is a systematic method of coming to the wrong conclusion	
with confidence.


Wed, 18 Dec 2002 21:37:01 +0530
"Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
Re: v7.3.1 tar ready ... please check it ...
On Wed, 2002-12-18 at 08:53, Dave Page wrote:
> > -----Original Message-----
> > From: Marc G. Fournier [mailto:scrappy@hub.org] 
> > Sent: 18 December 2002 14:51
> > To: Robert Treat
> > Cc: pgsql-hackers@postgresql.org
> > Subject: Re: [HACKERS] v7.3.1 tar ready ... please check it ...
> > 
> > 
> > On Wed, 18 Dec 2002, Robert Treat wrote:
> > 
> > > Is this going to be announced to a wider press audience? Has anyone 
> > > gone over the "list of things to do when we release" to make sure 
> > > things like the websites getting updated or perhaps getting 
> > rpm builds 
> > > coordinated has been done?
> > 
> > No, we don't do that with minor releases ... nothing has 
> > changed that needs to be announced, other then a few bugs fixed ...
> 
> Maybe we should? The more publicity the better etc...
> 
> Regards, Dave
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

I agree it should be considered.  It helps build mind share, which I
think we can all agree is somewhat lacking for PostgreSQL compared to
MySQL.  It helps build the impression that PostgreSQL doesn't just sit
idle between major releases.  It allows a potential user base to see
"PostgreSQL" more frequently and build interest.  It let's people know
that PostgreSQL is constantly being improved.

Mind share is a powerful thing and as any advertiser will tell you,
press releases is one of the best ways to get the word out.

Greg


-- 
Greg Copeland <greg@copelandconsulting.net>
Copeland Computer Consulting


18 Dec 2002 10:15:12 -0600
Greg Copeland <greg@CopelandConsulting.Net>
Re: v7.3.1 tar ready ... please check it ...
"Marc G. Fournier" <scrappy@hub.org> writes:
> On Wed, 18 Dec 2002, Dave Page wrote:
>> Maybe we should? The more publicity the better etc...

> The problem is that there is nothing to announce ... "Hi, we fixed some
> bugs"? :)  minor releases don't have any features added to them, so isn't
> really news worthy ... :(

I think this is exactly the difference between "press release" and
"technical announcement" that Marc was getting beat up on just a couple
weeks ago.  A bug-fix-only update is not worthy of a press release.
It is worthy of a technical announcement --- which is exactly what Marc
plans to push out to pgsql-announce as soon as the FTP mirrors are up
to date.

			regards, tom lane

Wed, 18 Dec 2002 11:33:44 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: v7.3.1 tar ready ... please check it ... 
Oleg Bartunov wrote:
> > > > No, we don't do that with minor releases ... nothing has
> > > > changed that needs to be announced, other then a few bugs fixed ...
> > >
> > > Maybe we should? The more publicity the better etc...
> >
> > The problem is that there is nothing to announce ... "Hi, we fixed some
> > bugs"? :)  minor releases don't have any features added to them, so isn't
> > really news worthy ... :(
> >
> 
> I think changing major version of libpq is an important thing to be
> mentioned.

It is mentioned in the release notes text:

                         Migration to version 7.3.1
                                      
   A dump/restore is *not* required for those running 7.3. However, it
   should be noted that the main PostgreSQL interface library, libpq, has
   a new major version number for this release, which may require
   recompilation of client code in certain cases.

-- 
  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

Wed, 18 Dec 2002 14:33:54 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: v7.3.1 tar ready ... please check it ...
Peter Eisentraut wrote:
> Bruce Momjian writes:
> 
> >    A dump/restore is *not* required for those running 7.3. However, it
> >    should be noted that the main PostgreSQL interface library, libpq, has
> >    a new major version number for this release, which may require
> >    recompilation of client code in certain cases.
> 
> s/certain/all/

I was unclear on that.  If they install right over their existing
pgsql/lib directory, the old libpq will still be there, so a recompile
will not be required.

-- 
  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

Wed, 18 Dec 2002 14:52:40 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: v7.3.1 tar ready ... please check it ...
Bruce Momjian writes:

>    A dump/restore is *not* required for those running 7.3. However, it
>    should be noted that the main PostgreSQL interface library, libpq, has
>    a new major version number for this release, which may require
>    recompilation of client code in certain cases.

s/certain/all/

-- 
Peter Eisentraut   peter_e@gmx.net


Wed, 18 Dec 2002 20:59:16 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: v7.3.1 tar ready ... please check it ...
If it's all, perhaps we should reword as:

... has a new major version number for this release and will require
recompilation of client code.

Robert Treat

On Wed, 2002-12-18 at 14:59, Peter Eisentraut wrote:
> Bruce Momjian writes:
> 
> >    A dump/restore is *not* required for those running 7.3. However, it
> >    should be noted that the main PostgreSQL interface library, libpq, has
> >    a new major version number for this release, which may require
> >    recompilation of client code in certain cases.
> 
> s/certain/all/
> 




18 Dec 2002 15:11:47 -0500
Robert Treat <xzilla@users.sourceforge.net>
Re: v7.3.1 tar ready ... please check it ...
On Wed, 18 Dec 2002, Bruce Momjian wrote:

> Peter Eisentraut wrote:
> > Bruce Momjian writes:
> >
> > >    A dump/restore is *not* required for those running 7.3. However, it
> > >    should be noted that the main PostgreSQL interface library, libpq, has
> > >    a new major version number for this release, which may require
> > >    recompilation of client code in certain cases.
> >
> > s/certain/all/
>
> I was unclear on that.  If they install right over their existing
> pgsql/lib directory, the old libpq will still be there, so a recompile
> will not be required.
>

It's not always safe to install over existing previous installation.
I think special mention about recompiling DBD::Pg would be important


>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83


Wed, 18 Dec 2002 23:55:54 +0300 (MSK)
Oleg Bartunov <oleg@sai.msu.su>
Re: v7.3.1 tar ready ... please check it ...
Oleg Bartunov wrote:
> On Wed, 18 Dec 2002, Bruce Momjian wrote:
> 
> > Peter Eisentraut wrote:
> > > Bruce Momjian writes:
> > >
> > > >    A dump/restore is *not* required for those running 7.3. However, it
> > > >    should be noted that the main PostgreSQL interface library, libpq, has
> > > >    a new major version number for this release, which may require
> > > >    recompilation of client code in certain cases.
> > >
> > > s/certain/all/
> >
> > I was unclear on that.  If they install right over their existing
> > pgsql/lib directory, the old libpq will still be there, so a recompile
> > will not be required.
> >
> 
> It's not always safe to install over existing previous installation.

Uh, that's what we recommend right now.  How is it wrong?

> I think special mention about recompiling DBD::Pg would be important

Uh, we don't distribute DBD:Pg.

-- 
  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

Wed, 18 Dec 2002 16:25:23 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: v7.3.1 tar ready ... please check it ...
Bruce Momjian writes:

> I was unclear on that.  If they install right over their existing
> pgsql/lib directory, the old libpq will still be there, so a recompile
> will not be required.

That's kind of like saying, if you keep using PostgreSQL 7.2 then a
dump/restore will not be required. ;-)  Installing new code directly over
old one without deleting is an extremely bad strategy.

-- 
Peter Eisentraut   peter_e@gmx.net


Thu, 19 Dec 2002 00:41:51 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: v7.3.1 tar ready ... please check it ...
Peter Eisentraut wrote:
> Bruce Momjian writes:
> 
> > I was unclear on that.  If they install right over their existing
> > pgsql/lib directory, the old libpq will still be there, so a recompile
> > will not be required.
> 
> That's kind of like saying, if you keep using PostgreSQL 7.2 then a
> dump/restore will not be required. ;-)  Installing new code directly over
> old one without deleting is an extremely bad strategy.

Well, our release notes say:

	A dump/restore is *not* required for those running 7.3. 

and INSTALL says:

   4. Installing The Files
           Note: If you are upgrading an existing system and are going to
           install the new files over the old ones, then you should have
           backed up your data and shut down the old server by now, as
           explained in the Section called If You Are Upgrading above.

In fact, we are a unclear about exactly when you need a dump/reload and
when you don't.  Seems the INSTALL file should have a clearer setup for
folks upgrading from 7.3 to 7.3.1.

-- 
  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

Wed, 18 Dec 2002 18:44:27 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: v7.3.1 tar ready ... please check it ...
Shridhar Daithankar wrote:
> On 18 Dec 2002 at 8:54, scott.marlowe wrote:
> > 
> > www.linuxtoday.com has weekly updates from many gnu / OSS projects which 
> > are far less interesting than our 7.3.1 release is.  I could see posting a 
> > minor upgrade release notice there and on other OSS news web site 
> > (freshmeat, slashdot, etc...)
> 
> I read linuxtoday and /. daily. Linuxtoday is OK but /. would be an almost 
> waste of another 800 comments of postgresql v/s mysql.

That's okay, another 800 comments of PostgreSQL vs MySQL on Slashdot
would increase the load on Slashdot's MySQL server, thus making it
slower and illustrating the point that they should be using PostgreSQL
instead.  [ ducks ]

:-)


-- 
Kevin Brown					      kevin@sysexperts.com

Wed, 18 Dec 2002 20:25:44 -0800
Kevin Brown <kevin@sysexperts.com>
Re: v7.3.1 tar ready ... please check it ...
Bruce Momjian writes:

>            Note: If you are upgrading an existing system and are going to
>            install the new files over the old ones, then you should have
>            backed up your data and shut down the old server by now, as
>            explained in the Section called If You Are Upgrading above.
>
> In fact, we are a unclear about exactly when you need a dump/reload and
> when you don't.  Seems the INSTALL file should have a clearer setup for
> folks upgrading from 7.3 to 7.3.1.

There's a hidden "...backed up your data, if required, ..." in there that
only the author can see. ;-)  But I think the section called If You Are
Upgrading makes it rather clear when a backup is required.

-- 
Peter Eisentraut   peter_e@gmx.net


Fri, 20 Dec 2002 00:45:15 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: v7.3.1 tar ready ... please check it ...