+1, I like it :) Probably should only check the changes in the first release section though - I know I don’t want to go back and fix up thousands of issues.
Steve On Feb 21, 2014, at 10:05 AM, Robert Muir <[email protected]> wrote: > > On Fri, Feb 21, 2014 at 6:31 AM, Martijn v Groningen > <[email protected]> wrote: > > Only spotted a small docs typo in the Lucene CHANGES.txt, the second issue > under "Changes in Runtime Behavior" should be LUCENE-5399 instead of > LUCENE-4399. > > A crazy idea: The smoketester knows which release its testing, its > theoretically possible that when validating CHANGES it could use the JIRA > REST api to check that Fix-Version is consistent with that for each change. > > This might catch problems like this automatically (e.g. it would complain > that LUCENE-4399 has no Fix-Version 4.7). --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
