+1
On Thu, Feb 27, 2014 at 1:08 PM, Andrew Grieve <agri...@chromium.org> wrote: > My understanding from all of the discussion & from what Joe pointed out is > that we do need to vote. > It's not hard to put a copy on dist/ as well. > > > On Thu, Feb 27, 2014 at 12:03 PM, Joe Schaefer <joe_schae...@yahoo.com > >wrote: > > > I don't doubt there is some impedance mismatch between > > the different types of distributions and channels you guys > > use and what the policy calls for, but as the document says > > deviations need to be approved by the board. All I can say > > is that we've been down this road with other projects and > > ultimately all of them (maven was the most challenging) have > > complied with policy. > > > > > > > > > > On Thursday, February 27, 2014 12:00 PM, Josh Soref < > jso...@blackberry.com> > > wrote: > > > > Joe Schaefer wrote: > > > > > >> Well I wouldn't put it quite like that. Anything that > > >> meets the definition of a release *should* be on dist > > >> anyway. The definition I am referring to is here: > > >> > > >> http://www.apache.org/dev/release#what > > > > > >That¹s problematic. > > > > > >> Where do releases go? > > >> A release isn't 'released' until the contents are in the project's > > >>distribution directory, > > >> which is a subdirectory of www.apache.org/dist/. > > > > > >> In addition to the distribution directory, > > >> project that use Maven or a related build tool sometimes place their > > >>releases on > > >> repository.apache.org beside some convenience binaries. > > >> The distribution directory is required, while the repository system is > > >>an optional convenience. > > > > > >This implies that we¹re required to have plugman (or whatever) in dist/ > > >(before?) it lands in npm¹s repo. > > > > > > > > >Note: I¹m not advocating anything, just following to logical > conclusions. > > >Voting and releasing is a headache which I am currently leaving to > others. > > > > > > > > > > > > > > >
