Sat Oct 29 05:58:38 PDT 2011
- Previous message: [Slony1-general] Re : Fwd: Re: [Slony1-hackers] Re : Re : Re : Re : Re : Slony 2.1.0 PDF Documentation available
- Next message: [Slony1-general] postgres/slony upgrade question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sounds good for 3.a/3.b Thanks David ________________________________ De : Steve Singer <ssinger at ca.afilias.info> À : Christopher Browne <cbbrowne at afilias.info> Cc : Slony General <slony1-general at lists.slony.info> Envoyé le : Vendredi 28 Octobre 2011 14h36 Objet : Re: [Slony1-general] Fwd: Re: [Slony1-hackers] Re : Re : Re : Re : Re : Slony 2.1.0 PDF Documentation available On 11-10-27 07:49 PM, Christopher Browne wrote: > ---------- Forwarded message ---------- > From: "Christopher Browne" <cbbrowne at afilias.info > <mailto:cbbrowne at afilias.info>> > Date: Oct 27, 2011 7:48 PM > Subject: Re: [Slony1-hackers] Re : Re : Re : Re : Re : Slony 2.1.0 PDF > Documentation available > To: "David TECHER" <davidtecher at yahoo.fr <mailto:davidtecher at yahoo.fr>> > > All the options have varying bits of new complexity / new apparatus, so > any choice involves a little more work. I think I like 3b too, as it > seems to have fewer "moving parts" than most of the others. > > Ideally 3b involves scripting dropping the PDF into the > less-processed-by-PHP area, as opposed to us needing to remember Yet > Another Deployment Rule. > > I suppose more work should go into the release script, which I'll > observe that I changed a bit when doing 2.1.0... > > Maybe that script should need a CVS repo location, and actually put the > build into place? The release script (tools/build_release.sh) is already in git I wouldn't want to store it in two locations. That script can be run to make a tag + tar files by anyone who clones the slony git repository. It doesn't require login credentials to www.slony.info and I wouldn't want to change that. Maybe we need a second script that handles the slony.info side of things. The nice thing about 3.a and 3.c are that it doens't require any new steps at deployment time. You just untar the -docs tarfile (which we already do) and the PDF is there. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20111029/9ac45d9b/attachment.htm
- Previous message: [Slony1-general] Re : Fwd: Re: [Slony1-hackers] Re : Re : Re : Re : Re : Slony 2.1.0 PDF Documentation available
- Next message: [Slony1-general] postgres/slony upgrade question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list