That’s why it would be great to have Justin write up a “This is how I test a release” page somewhere that explains how he goes about it. Mentors and release managers should be able to generate the same data sets and try to interpret it in the same way early in the release process. You still may not catch everything Justin will, but hopefully you will catch enough that any issues found can be rolled to the next release.
-Alex On 7/17/15, 12:28 AM, "Cédric Champeau" <cedric.champ...@gmail.com> wrote: >Thanks Justin. We had read that document, but even reading the "binary >section", it wasn't clear that source and binary L&N had to be >different. I would suggest to update the page to make it clear that >"These additional dependencies must be accounted for in LICENSE and >NOTICE." doesn't mean that the LICENSE and NOTICE files need to be >updated to include those additional dependencies, but that *separate* >L&N files *must* be issued including these additional dependencies. > >2015-07-17 1:02 GMT+02:00 Justin Mclean <justinmcl...@me.com>: >> Hi, >> >>> +1 ! And adding such a tool into rat or whatever would be extremely >>> helpful, too... >> >> The “tools” I use generally make a bit of noise and require some >>interpretation / filtering so I’m not sure they could be automated >>cleanly. One thing rat might be able to do that I don’t think it >>currently does is detect files containing more than one license header. >> >> Best advice I can give is follow this guide [1] and use it when >>reviewing releases. >> >> Thanks, >> Justin >> >> 1. http://www.apache.org/dev/licensing-howto.html >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org >
