On Sat, Jan 13, 2018 at 3:21 PM, Neil C Smith <[email protected]> wrote:
> On Sat, 13 Jan 2018 at 13:39 Jan Lahoda <[email protected]> wrote: > > > I belive we could do convenience binaries for subsets, but not source > > releases for subsets. > > > > I wondered if this was related when I asked, but I'm confused by this. If > the code in the repository is capable of building source subsets of itself, > then what stops creating convenience source subsets available too? That > doesn't really conflict with having a canonical full repository source zip > for the tagging, voting and release phase? People could equally download > 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. So it is not quite clear to me that releasing "git content" and "convenient source subset" improves the current situation/proposal, where we basically release "source subsets". > the full source and build the required source subset from it themselves? > They can do that of course. The question is whether we expect that they will (this is particularly the case for platform, I assume). 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.) Jan > That does kind of presume we don't release subsets to a different schedule > I guess? But then maybe if we do that it's time to consider splitting > across multiple repositories anyway? > > Best wishes, > > Neil > > > > > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
