We discussed this briefly in an email here, Andy ran that one JDiff manually too. I thought it'd be a good idea if you can run this against various revisions, hence my little helper script. But I do agree, we should add this so that we have this between releases as well for everyone to check.
How would you check if you have incompatible changes though? By hand, browsing the JDiff report? On Tue, May 10, 2011 at 6:00 PM, Todd Lipcon <[email protected]> wrote: > Hey Lars, > > Think we could introduce this into the release process? I think there's a > HowToRelease wiki. If you can update that with instructions, we can use that > to help test that point releases don't make incompatible changes. > > -Todd > > On Tue, May 10, 2011 at 5:35 AM, Lars George <[email protected]> wrote: > >> Hi, >> >> I am chasing commits to somehow be able to keep the book current (as >> much as possible) before the final deadline. I wired a small script >> together that is useful to create a JDiff report between two >> revisions: >> >> https://github.com/larsgeorge/hbase-book/blob/master/bin/jdiff-hbase.sh >> >> Run it with two revisions to compare those, or only one to compare it >> against trunk. It checks out those revisions, builds the JavaDocs and >> runs JDiff. Might be helpful to others. >> >> Lars >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera >
