Hm.. so previously we release the trunk docs with the 0.98 releases? this seems strange. I would think 0.98 docs would be generated from the 0.98 release branch's branch.
It seems reasonable if in our post-git releases we have the source for the docs in the source tarballs but not the build docs. The built docs however, are in the ready-to-use release tarballs and correspond to the release. Is this the case now? Doing this becomes more important because the docs will likely change due to deployment changes with potentially different rules of thumb etc for 0.98->1.0 vs what will be 2.0 releases. Jon. On Tue, Jul 29, 2014 at 5:23 PM, Andrew Purtell <[email protected]> wrote: > ... And the reason for doing it that way is, AFAIK, a source release > artifact should correspond exactly to a SCM revision. With SVN a tag was a > branch was a tag, with git I think to commit back a copy of docs from trunk > to branch, I'd need to create a branch for the release and push it? > Thoughts? > > > On Tue, Jul 29, 2014 at 5:20 PM, Andrew Purtell <[email protected]> > wrote: > > > Thanks. That's my fault. 0.98.2 was the last release made using SVN. I > > would create a branch in SVN for the release tag and commit the copy of > > docs back from trunk to the branch, then build the source tarball from > > there. Now I think the source tarball is lacking latest docs but the > binary > > tarballs will have them, because first I build the source tarball from a > > git checkout, then munge POMs and copy back docs, then generate binary > > artifacts. > > > > > > On Tue, Jul 29, 2014 at 1:09 PM, Esteban Gutierrez <[email protected] > > > > wrote: > > > >> Hi all, > >> > >> Is not a big deal but while doing some internal housekeeping I noticed > >> that > >> in 0.98.3 and and 0.98.4 don't have the latest docs that have been > >> included > >> in previous releases. In previous 0.98 point releases the docs were a > copy > >> from trunk, but for 0.98.3 and 0.98.4 the docs are the vanilla docs. > >> > >> cheers, > >> esteban. > >> > >> -- > >> Cloudera, Inc. > >> > > > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > -- // Jonathan Hsieh (shay) // HBase Tech Lead, Software Engineer, Cloudera // [email protected] // @jmhsieh
