I guess this is the only way to ensure documented code. +1
We need to put this rule somewhere, maybe in the Wiki? Cheers, -- Gianmarco On Tue, Oct 23, 2012 at 12:37 AM, Santhosh M S <santhosh_mut...@yahoo.com> wrote: > +1 > > > ________________________________ > From: Jonathan Coveney <jcove...@gmail.com> > To: dev@pig.apache.org; Olga Natkovich <onatkov...@yahoo.com> > Sent: Monday, October 22, 2012 5:09 PM > Subject: Re: PROPOSAL: how to handle release documentation going forward > > As someone who chronically under-documents, I think that this is a good > idea. +1 > > 2012/10/22 Olga Natkovich <onatkov...@yahoo.com> > >> Hi, >> >> Since we lost the dedicated document writer for Pig, would it make sense >> to require that going forward (0.12 and beyond) we require that >> documentation updates are included in the patch together with code changes >> and tests. I think that should work for most features/updates except >> perhaps big items that might require more than one JIRA to be completed >> before documentation changes make sense. >> >> Comments? >> >> Olga >>
