On Mon, Apr 4, 2011 at 9:04 AM, Simon Nash <n...@apache.org> wrote: > ant elder wrote: >> >> On Mon, Apr 4, 2011 at 2:14 PM, Simon Nash <n...@apache.org> wrote: >> >>> Also in [1], I said that a new sample that doesn't yet meet the mandatory >>> release requirements should go in unreleased/ initially. AFAICT, the >>> store >>> sample does meet the mandatory release requirements, so I'm not sure why >>> it was moved to unreleased/. >>> >> >> Because without asking first there is no way of know if there is >> consensus with everyone to include something in trunk. I give up on >> this new approach to the samples, it is sucking away way to much time. >> Please from now on lets go back to trunk/samples working just the same >> as any other part of tuscany svn. >> >> ...ant >> >> > I think the process should work the other way round, i.e., that if > a sample is committed to trunk and it doesn't meet the mandatory > requirements (which we can discuss and hopefully agree), then it should > be moved to unreleased/ until it does meet the mandatory requirements. > Is this a workable approach? > > Simon > >
+1, and most like, if we have the requirements cleared agreed, it will be more like : could you please fix the violating items 1, 3 and 5 for sample X or move it to unreleased. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
