On Sun, 5 May 2002, Lamar Owen wrote: > On Sunday 05 May 2002 02:46 pm, Jack Bates wrote: > > CVSROOT=:pserver:[EMAIL PROTECTED]:/projects/cvsroot > > > Still no tag for 7.2.1. > > > Could I (again) request that a tag be set for the current public release > > of this product? > > Why? ...
Aside from being a near-universal "best practice", it makes it easier for someone to analyze whether local patches to 7.2.1 conflict with work that the team has committed. This makes it easier for patches to be massaged and submitted to the maintainers successfully even if the patch is not originally written for CVS head. Not everyone wants to develop on the bleeding edge all the time. Code that has passed local acceptance testing needs to be supported carefully at its existing release level, if at all possible. There was a tag for the 7.1.2 release, which was my previous baseline. A bunch of BETAs leading to 7.2 are tagged. Why not the current public release? I'm not here to bully and I apologize if my tone irritated. I'm a seasoned software engineer, and I'm happy to help out a bit in areas where I am qualified to do so. I submitted a patch last week for an obscure SSL issue in libpq and I'm looking at enabling, generally, non-blocking client IO over SSL in that library. BTW - I _LOVE_ 7.2's non-locking VACUUM ANALYZE - many, many thanks! Recent murmurings about propogating "deadness" of tuples to reduce index scan time are quite interesting to me, as is point-in-time recovery. Even without these features, PostgreSQL works _very_ well and quite predictably for me. I beat on this DBMS very hard, and I have not been able to break 7.2[.1] (nor 7.1.2, previously). Real good stuff. Cheers. -- Jack Bates Portland, OR, USA http://www.floatingdoghead.net Got privacy? My PGP key: http://www.floatingdoghead.net/pubkey.txt ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
