On Fri, Dec 21, 2012 at 11:24 AM, Joe Brockmeier <[email protected]> wrote: > On Fri, Dec 21, 2012, at 09:44 AM, Chip Childers wrote: >> Hi all, >> >> I just filed CLOUDSTACK-699 for the 4.0.1-incubating, which is >> basically noting that we have the 4.0.0-incubating release number all >> over the place in the 4.0 branch. >> >> The main question I have is for the folks that know publican best: >> >> Can we have a single variable that sets the version number that's >> referenced in the documentation? > > Sort of, yes. > >> Where we want the documentation to reflect a point in time statement >> (like in the release notes), we wouldn't use it. But doc titles, file >> names, etc... should probably pull from that variable. > > Hmmm. What do you mean by file names? Any actual Publican files wouldn't > be altered by a version variable, but the doc files generated by > Publican should have that number.
I mean file names in the content body of the documents. For example: In docs/en-US/build-deb.xml, the .deb files that you would expect to see after packaging are listed. They include 4.0.0-incubating, not 4.0.1-incubating. We could either edit all of the content to avoid being specific about version number in this way, or use a variable to solve the issue with one place to change it. > Best, > > jzb > -- > Joe Brockmeier > [email protected] > Twitter: @jzb > http://www.dissociatedpress.net/ >
