OK, the most important thing right now is that we put a source release together, without the JARs, and name that rc2 and then start a new vote thread on that.
Do we agree/disagree? Thanks, Gj On Sat, Jan 13, 2018 at 8:50 PM, Neil C Smith <[email protected]> wrote: > On Sat, 13 Jan 2018, 19:11 Jan Lahoda, <[email protected]> wrote: > >> My understanding of the ASF process is that any release (any file released >> under ASF) is subject of the same scrutiny. I.e. if we would release both >> full zips and subset zips, all of those would need to go through the voting >> process, be reviewed and approved in the same way. >> > > I guess we need clarity on this. To me, the full zip is the release, and > the full binaries, plus subset source and binaries are convenience > artefacts from the full zip's build process. In that sense I don't see a > fundamental difference between source and binary subsets - logically allow > both or neither? > > > And I just recalled: there is one important difference between the git >> content and the source zip: the DEPENDENCIES file. My understanding (which >> may be wrong) is that we need it, so if we wanted to just release git >> content, we would need to somehow have this in git. (And presumably have a >> check that would fail if it wouldn't match the actual source content.) >> > > Had that thought too. The check would be a good thing. And I guess the git > history of that file would then be useful - every PR adding a dependency > would have to touch it? > > Best wishes, > > Neil > >> -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
