v7.3.1 Bundled and Released ... 
Author Message
 v7.3.1 Bundled and Released ...

Quote:
Greg Copeland writes:
> Just a reminder, there still doesn't appear to be a 7.3.1 tag.

There is a long tradition of systematically failing to tag releases in
this project.  Don't expect it to improve.

--

---------------------------(end of broadcast)---------------------------



Wed, 22 Jun 2005 18:20:35 GMT
 v7.3.1 Bundled and Released ...

Quote:

> Greg Copeland writes:

> > Just a reminder, there still doesn't appear to be a 7.3.1 tag.

> There is a long tradition of systematically failing to tag releases in
> this project.  Don't expect it to improve.

It was I who suggested that a release team would be a good idea.  I think
that was soundly rejected.  I still think it's a good idea.  If only to
ensure that things are properly tagged, the right annoucements go out at
the right times, that a code freeze goes into effect, etc. These concepts
are not new.  A release is an important step in the life cycle.

I volunteered to document the release procedure as it resides only within
lore and a couple of heads.  I have yet to start.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org



Wed, 22 Jun 2005 19:44:33 GMT
 v7.3.1 Bundled and Released ...

Quote:


>> There is a long tradition of systematically failing to tag releases in
>> this project.  Don't expect it to improve.
> It was I who suggested that a release team would be a good idea.

We *have* a release team.  Your problem is that Marc, who is the man who
would need to do this, doesn't appear to consider it an important thing
to do.  Try to convince him to put it on his checklist.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command



Thu, 23 Jun 2005 00:08:17 GMT
 v7.3.1 Bundled and Released ...

Quote:

> Greg Copeland writes:

> > Just a reminder, there still doesn't appear to be a 7.3.1 tag.

> There is a long tradition of systematically failing to tag releases in
> this project.  Don't expect it to improve.

Well, I thought I remembered from the "release team" thread that it was
said there was a "punch list" of things that are done prior to actually
releasing.  If not, it certainly seems like we need one.  If there is
one, tagging absolutely needs to be on it.  If we have one and this is
already on the list, seems we need to be eating our own food.  ;)

--

Copeland Computer Consulting

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



Thu, 23 Jun 2005 02:13:42 GMT
 v7.3.1 Bundled and Released ...
msg resent because I incorrectly copied/pasted some addresses.  
Sorry.


Quote:


> >> There is a long tradition of systematically failing to tag releases
> >> in this project.  Don't expect it to improve.

> > It was I who suggested that a release team would be a good idea.

> We *have* a release team.

I have a suggestion.  Let us document who is the release team and who
is responsible for each step of the release.  Perhaps that is the
problem: a lack of process.

I'll add that to my list of things I've promised to do.
--
Dan Langille : http://www.langille.org/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org



Thu, 23 Jun 2005 04:56:13 GMT
 v7.3.1 Bundled and Released ...
msg resent because I incorrectly copied/pasted some addresses.  Sorry.


Quote:


> >> There is a long tradition of systematically failing to tag releases
> >> in this project.  Don't expect it to improve.

> > It was I who suggested that a release team would be a good idea.

> We *have* a release team.  Your problem is that Marc, who is the man
> who would need to do this, doesn't appear to consider it an important
> thing to do.  Try to convince him to put it on his checklist.

Marc?  Is this true?  You don't consider it important to tag the
release?  I'm quite sure that's not the case and that Marc does
consider it important.  It's just something which he forgot to do.

A recent post by Greg Copeland implies this item is on his checklist.

IMHO, it is vital that the tree is properly tagged for each release.  
AFAIK, a tag can be laid with with respect to timestamp value.  So
why don't we just do it?
--
Dan Langille : http://www.langille.org/

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



Thu, 23 Jun 2005 04:56:33 GMT
 v7.3.1 Bundled and Released ...

Quote:



> >> There is a long tradition of systematically failing to tag releases in
> >> this project.  Don't expect it to improve.

> > It was I who suggested that a release team would be a good idea.

> We *have* a release team.  Your problem is that Marc, who is the man who
> would need to do this, doesn't appear to consider it an important thing
> to do.  Try to convince him to put it on his checklist.

I never considered tag'ng for minor releases as having any importance,
since the tarball's themselves provide the 'tag' ... branches give us the
ability to back-patch, but tag's don't provide us anything ... do they?

That said, I can back-tag the whole source tree for past releases if ppl
do think it is important, its just a matter of knowing the 'timestamp' to
base it on, which I can do based on the dates of the tar files ...

Its not like tag'ng is hard to do ...

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command



Thu, 23 Jun 2005 09:04:47 GMT
 v7.3.1 Bundled and Released ...

--On Saturday, January 04, 2003 21:04:32 -0400 "Marc G. Fournier"

Quote:




>> >> There is a long tradition of systematically failing to tag releases in
>> >> this project.  Don't expect it to improve.

>> > It was I who suggested that a release team would be a good idea.

>> We *have* a release team.  Your problem is that Marc, who is the man who
>> would need to do this, doesn't appear to consider it an important thing
>> to do.  Try to convince him to put it on his checklist.

> I never considered tag'ng for minor releases as having any importance,
> since the tarball's themselves provide the 'tag' ... branches give us the
> ability to back-patch, but tag's don't provide us anything ... do they?

> That said, I can back-tag the whole source tree for past releases if ppl
> do think it is important, its just a matter of knowing the 'timestamp' to
> base it on, which I can do based on the dates of the tar files ...

It's useful for those using the CVS files to RECREATE a version based on
the TAG
to checkout something (without pulling the whole tarball).

LER

Quote:

> Its not like tag'ng is hard to do ...

> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command


--
Larry Rosenman                     http://www.lerctr.org/~ler

US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html



Thu, 23 Jun 2005 09:09:02 GMT
 v7.3.1 Bundled and Released ...

Quote:
> I never considered tag'ng for minor releases as having any importance,
> since the tarball's themselves provide the 'tag' ... branches give us the
> ability to back-patch, but tag's don't provide us anything ... do they?

Well, a tag makes it feasible for someone else to recreate the tarball,
given access to the CVS server.  Dunno how important that is in the real
world --- but I have seen requests before for us to tag release points.

Any other arguments out there?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command



Thu, 23 Jun 2005 09:11:07 GMT
 v7.3.1 Bundled and Released ...

Quote:

> Any other arguments out there?

Per-release tags make it easier to see quickly if some code has
changed in -current or not.  As the CVS tree is available via anoymous
CVS (I think?), CVSup, and via the web so there are many potential
users who are not active developers and who probably run releases
rather than -current.

Regards,

Giles

---------------------------(end of broadcast)---------------------------



Thu, 23 Jun 2005 11:06:42 GMT
 v7.3.1 Bundled and Released ...

Quote:


> > I never considered tag'ng for minor releases as having any importance,
> > since the tarball's themselves provide the 'tag' ... branches give us the
> > ability to back-patch, but tag's don't provide us anything ... do they?

> Well, a tag makes it feasible for someone else to recreate the tarball,
> given access to the CVS server.  Dunno how important that is in the real
> world --- but I have seen requests before for us to tag release points.

FWIW, in the real world, a release doesn't happen if it's not taqged.

---------------------------(end of broadcast)---------------------------



Thu, 23 Jun 2005 20:41:47 GMT
 v7.3.1 Bundled and Released ...

Quote:



> > > I never considered tag'ng for minor releases as having any importance,
> > > since the tarball's themselves provide the 'tag' ... branches give us the
> > > ability to back-patch, but tag's don't provide us anything ... do they?

> > Well, a tag makes it feasible for someone else to recreate the tarball,
> > given access to the CVS server.  Dunno how important that is in the real
> > world --- but I have seen requests before for us to tag release points.

> FWIW, in the real world, a release doesn't happen if it's not taqged.

Agreed!  Any tarballs, rpms, etc., should be made from the tagged
source.  Period.  If rpm's are made from a tarball that is made from
tagged source, that's fine.  Nonetheless, any official release (major or
minor) should always be made from the resulting tagged source.  This
does two things.  First, it validates that everything has been properly
tagged.  Two, it ensures that there are not any localized files or
changes which might become part of a tarball/release which are not
officially part of the repository.

I can't stress enough that a release should never happen unless source
has been tagged.  Releases should ALWAYS be made from a checkout based
on tags.

--

Copeland Computer Consulting

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org



Thu, 23 Jun 2005 22:53:46 GMT
 v7.3.1 Bundled and Released ...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quote:
> Well, a tag makes it feasible for someone else to recreate the tarball,
> given access to the CVS server.  Dunno how important that is in the real
> world --- but I have seen requests before for us to tag release points.

> Any other arguments out there?

FWIW, I use the tags often in some scripts that rely on the output
of 'cvs status -v'. Seeing REL7_3_STABLE at the top of the
"Existing Tags" list is a bit disconcerting when you know that
it's not true. My scripts assume that the latest release should
always be tagged.


PGP Key: 0x14964AC8 200208

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+GE1NvJuQZxSWSsgRAh/1AKCPEKQeQ3OnKzbeSl5DXstnwwiFPQCfQ2mn
KplkOouzodJqZvQNN2tk8Fk=
=OaZY
-----END PGP SIGNATURE-----

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html



Thu, 23 Jun 2005 23:21:13 GMT
 v7.3.1 Bundled and Released ...

Quote:
> -----Original Message-----

> Sent: 05 January 2003 01:10
> To: Marc G. Fournier
> Cc: Dan Langille; Peter Eisentraut; Greg Copeland; Bruce=20
> Momjian; PostgresSQL Hackers Mailing List
> Subject: Re: [GENERAL] [HACKERS] v7.3.1 Bundled and Released ...=20
>=20
>=20

> > I never considered tag'ng for minor releases as having any=20
> importance,=20
> > since the tarball's themselves provide the 'tag' ...=20
> branches give us=20
> > the ability to back-patch, but tag's don't provide us=20
> anything ... do=20
> > they?
>=20
> Well, a tag makes it feasible for someone else to recreate=20
> the tarball, given access to the CVS server.  Dunno how=20
> important that is in the real world --- but I have seen=20
> requests before for us to tag release points.
>=20
> Any other arguments out there?

I've often found tags useful when ppl have reported bugs that have
occured between version - A quick way to see the changes that might have
introduced the new bug when browsing though a web interface.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command



Fri, 24 Jun 2005 00:53:00 GMT
 
 [ 14 post ] 

 Relevant Pages 

1. v7.3.1 Bundled and Released ...

2. v7.3.1 Bundled and Released ...

3. v7.3.1 Bundled and Released ...

4. v7.3.1 Bundled and Released ...

5. PostgreSQL v7.1.3 bundled and uploaded to central FTP Server

6. v7.2.4 bundled ...

7. v7.2.4 bundled ...

8. PostgreSQL v7.1BETA3 Bundled and Available ...

9. v7.2.4 bundled ...

10. PostgreSQL v7.1.3 bundled and uploaded to central FTP Server

11. [RELEASE ANNOUNCEMENT] v7.0.3 *Final* now Available

12. [HACKERS] PostgreSQL v7.2 Final Release


 
Powered by phpBB® Forum Software