Chris Browne cbbrowne at lists.slony.info
Thu Jun 21 15:14:23 PDT 2007
Update of /home/cvsd/slony1/slony1-www/content
In directory main.slony.info:/tmp/cvs-serv13607/content

Modified Files:
	frontpage.txt news.txt 
Log Message:
Released 1.2.10-pre2


Index: frontpage.txt
===================================================================
RCS file: /home/cvsd/slony1/slony1-www/content/frontpage.txt,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** frontpage.txt	18 Jun 2007 17:25:46 -0000	1.13
--- frontpage.txt	21 Jun 2007 22:14:21 -0000	1.14
***************
*** 1,19 ****
  ---
! Slony-I 1.2.10 pre-release tarball uploaded
! http://lists.slony.info/downloads/1.2/source/slony1-1.2.10-pre.tar.bz2
! 2007-06-13
  Chris Browne
  
! I have uploaded a tarball for 1.2.10 as it stands now.  It still has a
! <a href="http://main.slony.info/documentation/logshipping.html"> log
! shipping</a> issue; that shouldn't prevent people from doing compile
! testing on extra platforms or other verification not directly related
! to log shipping.
  
  <P> Please <i>do not</i> release binaries based on this tarball; that
  could lead to the regrettable situation of people downloading
  something that isn't the true final release of 1.2.10.  The license
! permits such things, but please wait until the final release of 1.2.10
! is tagged and available...
  ---
  Slony-I Release approaching readiness - 1.2.10
--- 1,21 ----
  ---
! Slony-I 1.2.10 pre-release tarball #2 uploaded
! http://lists.slony.info/downloads/1.2/source/slony1-1.2.10-pre2.tar.bz2
! 2007-06-21
  Chris Browne
  
! I have uploaded a tarball for 1.2.10 based on the fixes that have come
! in this week to <a href=
! "http://main.slony.info/documentation/logshipping.html"> log shipping
! </a>.
! 
! <P> I have run tests of this build on Debian/Unstable on the IA-32
! architecture against each of PostgreSQL 7.4, 8.0, 8.1, 8.2, and a
! recent copy of CVS HEAD (e.g. - 8.3).
  
  <P> Please <i>do not</i> release binaries based on this tarball; that
  could lead to the regrettable situation of people downloading
  something that isn't the true final release of 1.2.10.  The license
! permits such things, but <i>please</i> wait until we call this final...
  ---
  Slony-I Release approaching readiness - 1.2.10
***************
*** 83,89 ****
  <li> Fixes to log shipping test
  
- <li> Change to tools/slony1_dump.sh (used to generate log shipping dump);
-   change quoting of "\\\backslashes\\\" to get rid of warning
- 
  <li> Win32 fix for MinGW+gcc
  
--- 85,88 ----
***************
*** 94,97 ****
--- 93,101 ----
  not the origin of the set.
  
+ <li> For logshipping we need to use the internally tracked ssy_seqno for
+   SYNC events as well.
+ 
+   <P> This allows "run_test.sh testlogship" to run successfully!
+ 
  </ol>
  ---

Index: news.txt
===================================================================
RCS file: /home/cvsd/slony1/slony1-www/content/news.txt,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -d -r1.23 -r1.24
*** news.txt	12 Jun 2007 18:28:21 -0000	1.23
--- news.txt	21 Jun 2007 22:14:21 -0000	1.24
***************
*** 10,13 ****
--- 10,32 ----
  <!-- Please keep this item at the top of the news list -->
  ---
+ Slony-I 1.2.10 pre-release tarball #2 uploaded
+ http://lists.slony.info/downloads/1.2/source/slony1-1.2.10-pre2.tar.bz2
+ 2007-06-21
+ Chris Browne
+ 
+ I have uploaded a tarball for 1.2.10 based on the fixes that have come
+ in this week to <a href=
+ "http://main.slony.info/documentation/logshipping.html"> log shipping
+ </a>.
+ 
+ <P> I have run tests of this build on Debian/Unstable on the IA-32
+ architecture against each of PostgreSQL 7.4, 8.0, 8.1, 8.2, and a
+ recent copy of CVS HEAD (e.g. - 8.3).
+ 
+ <P> Please <i>do not</i> release binaries based on this tarball; that
+ could lead to the regrettable situation of people downloading
+ something that isn't the true final release of 1.2.10.  The license
+ permits such things, but <i>please</i> wait until we call this final...
+ ---
  Version 1.2.10 - log shipping problem to solve
  http://lists.slony.info/pipermail/slony1-bugs/2007-June/000017.html



More information about the Slony1-commit mailing list