<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Sounds good for 3.a/3.b</span></div><div><br><span></span></div><div><span>Thanks David<br></span></div><div><br></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">De :</span></b> Steve Singer <ssinger@ca.afilias.info><br><b><span style="font-weight: bold;">À :</span></b> Christopher Browne <cbbrowne@afilias.info><br><b><span style="font-weight: bold;">Cc :</span></b> Slony General <slony1-general@lists.slony.info><br><b><span style="font-weight: bold;">Envoyé le :</span></b> Vendredi 28 Octobre 2011 14h36<br><b><span style="font-weight: bold;">Objet :</span></b> Re: [Slony1-general]
Fwd: Re: [Slony1-hackers] Re : Re : Re : Re : Re : Slony 2.1.0 PDF Documentation available<br></font><br>On 11-10-27 07:49 PM, Christopher Browne wrote:<br><br>> ---------- Forwarded message ----------<br>> From: "Christopher Browne" <<a ymailto="mailto:cbbrowne@afilias.info" href="mailto:cbbrowne@afilias.info">cbbrowne@afilias.info</a><br>> <mailto:<a ymailto="mailto:cbbrowne@afilias.info" href="mailto:cbbrowne@afilias.info">cbbrowne@afilias.info</a>>><br>> Date: Oct 27, 2011 7:48 PM<br>> Subject: Re: [Slony1-hackers] Re : Re : Re : Re : Re : Slony 2.1.0 PDF<br>> Documentation available<br>> To: "David TECHER" <<a ymailto="mailto:davidtecher@yahoo.fr" href="mailto:davidtecher@yahoo.fr">davidtecher@yahoo.fr</a> <mailto:<a ymailto="mailto:davidtecher@yahoo.fr" href="mailto:davidtecher@yahoo.fr">davidtecher@yahoo.fr</a>>><br>><br>> All the options have varying bits of new complexity / new apparatus,
so<br>> any choice involves a little more work. I think I like 3b too, as it<br>> seems to have fewer "moving parts" than most of the others.<br>><br>> Ideally 3b involves scripting dropping the PDF into the<br>> less-processed-by-PHP area, as opposed to us needing to remember Yet<br>> Another Deployment Rule.<br>><br>> I suppose more work should go into the release script, which I'll<br>> observe that I changed a bit when doing 2.1.0...<br>><br>> Maybe that script should need a CVS repo location, and actually put the<br>> build into place?<br><br>The release script (tools/build_release.sh) is already in git I wouldn't <br>want to store it in two locations.<br><br>That script can be run to make a tag + tar files by anyone who clones <br>the slony git repository. It doesn't require login credentials to <br>www.slony.info and I wouldn't want to change that.<br><br>Maybe we need a second script that handles the
slony.info side of <br>things. The nice thing about 3.a and 3.c are that it doens't require <br>any new steps at deployment time. You just untar the -docs tarfile <br>(which we already do) and the PDF is there.<br><br><br><br></div></div></div></body></html>