On 21 May 2018 at 21:16, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > >> I don't think there should be anything in the source release that is >> not in the source repo. > > It reasonably common (from my review of 100’s of releases) that the build > process may modify and/or add some files (e.g config files). I wouldn’t > expect any code to change or be added.
It's also important that there is nothing in the release tar that is not in the source repo or which cannot be readily derived from it (though that is too broad an exception). I have seen release tars that include spurious files that happened to be present in the workspace. In one case a file held private information. Your original mail said: >>> Which is OK many project release are not 100% identical to what is in the >>> release tar what is important is that none of the source code has changed. This could be taken to mean that it does not matter what goes into the release tar other than the source files. I think it's important to be clear that the release tar should have minimal changes from the source repo, and what sort of changes are allowed. > Thanks, > Justin --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
