Yes, I like this approach and already try to do that. I also would like to suggest that we try to update the docs to be a good reference. Looking at this: http://incubator.apache.org/guides/releasemanagement.html ...it makes me headache.
I found it always very difficult to discuss changes to such documents. I think we would need a good approach to efficiently maintain these kind of documents. On Mon, Jan 21, 2013 at 7:54 PM, Benson Margulies <bimargul...@gmail.com> wrote: > I'd like to float the following idea: > > Any time anyone offers a critique of a podling release (or other > behavior), include a URL to the documentation that should have told > them how to do the job. > > If you can't find any document, then say so. If there is one, and you > don't think it's clear, cite it and say so. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- http://www.grobmeier.de https://www.timeandbill.de --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
