You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@creadur.apache.org by "P. Ottlinger" <po...@apache.org> on 2015/02/23 22:50:42 UTC

Re: GSOC-Branch - ready to merge into trunk? - RAT-195

Fellow devs,

I've created RAT-195 as a task to perform commits on.

Am 31.07.2014 um 22:18 schrieb P. Ottlinger:
> Since all tests hopefully run on the branch I assume no functionality
> broken, but will check carefully upon merge/commit.

OVERVIEW
I browsed the rather old branch and do not really see a lot of use in
autogenerated Javadoc comments such as

/**
* Returns the foo for parameter a
*/
private Foo getFoo(Parameter a) {
....
}

In such cases I'd rather have no Javadoc - any objections to merging in
this way (and leaving out these mass automatically generated not really
helpful Javadoc)?


MERGING/COMMIT-strategy
Would you mind me merging in these changes piece by piece instead of one
big bang commit?

It does not seem to me that a lot of development is going on at the
moment, thus a stepwise commit seems fine to me.

Cheers,
Phil