Just a reminder, the goal is to create the release branch for 3.2 end of next week and then produce a release candidate. I don't see many open tickets that target 3.2.0, so it looks like we are on track.
Thanks, Thomas On Tue, Sep 22, 2015 at 9:05 AM, Thomas Weise <[email protected]> wrote: > Chris, > > Thanks for taking up the license header work. > > I had a quick look at the patch. > > We will need to fine tune the exclusions. For example, the repository > README.md should not have the license header? > > Would you be willing to submit the changes as a pull request against the > devel-3 branch? It will simplify review and merge. It would be great to > get it in before branching off 3.2, i.e ideally within a week. > > BTW there is a JIRA to improve the contributor guidelines: https://malhar. > atlassian.net/browse/APEX-137 > > Thanks, > Thomas > > > > > On Fri, Sep 18, 2015 at 12:50 PM, Chetan Narsude <[email protected]> > wrote: > >> How did you update those files to have the license included in them? >> >> There is a license-maven-plugin which we used before to apply license to >> all the interesting files using >> >> mvn license:format >> >> Is there a recommended alternative for automatically formatting licenses >> across hoards of file? >> >> Separately: should we encourage the patches or pull requests on Github? >> >> -- >> Chetan >> >> >> >> On Fri, Sep 18, 2015 at 9:32 AM, Chris Nauroth <[email protected]> >> wrote: >> >> > An additional consideration is the license header in each source file. >> > >> > >> http://incubator.apache.org/guides/releasemanagement.html#release-legal-aud >> > it >> > >> > >> > I had started a patch to do this in Core, hoping to make it my first >> > actual source level contribution to the project. :-) I just attached >> the >> > work in progress to Apache JIRA APEXCORE-1. >> > >> > https://issues.apache.org/jira/browse/APEXCORE-1 >> > >> > >> > (Please note that this issue might get wiped and need to get recreated >> > when infra does the migration from Atlassian JIRA.) >> > >> > The patch adds the standard Apache RAT plugin to the build process and >> > updates numerous files to add the license header, in response to the >> > warnings I saw from RAT. >> > >> > I think the big piece remaining is updating each .java file. Right now, >> > they show a copyright by DataTorrent, Inc. instead of referencing ASF. >> > For some reason, the RAT plugin isn't warning on these, but they would >> > need to get updated. >> > >> > Then, of course, the whole exercise would need to get repeated in >> Malhar. >> > >> > --Chris Nauroth >> > >> > >> > >> > >> > On 9/18/15, 8:25 AM, "Thomas Weise" <[email protected]> wrote: >> > >> > >Aniruddha, >> > > >> > >Thanks, and feel free to create tickets for items you would like to >> work >> > >on. >> > > >> > >One area that is not directly related but will have great impact are >> the >> > >pull request checks. >> > > >> > >Thomas >> > > >> > >On Fri, Sep 18, 2015 at 12:32 AM, Aniruddha Thombare < >> > >[email protected]> wrote: >> > > >> > >> Hi, >> > >> >> > >> I would like to help Thomas in RM process. >> > >> >> > >> >> > >> Thanks, >> > >> >> > >> >> > >> Aniruddha >> > >> >> > >> On Fri, Sep 18, 2015 at 10:45 AM, Thomas Weise < >> [email protected]> >> > >> wrote: >> > >> >> > >> > We would like to make 3.2.0 the first release after incubation. >> > >> > >> > >> > Target is to branch for 3.2 at the end of this month (September) >> and >> > >>then >> > >> > exercise the ASF compliant release process to get the release out >> by >> > >>end >> > >> of >> > >> > October latest. >> > >> > >> > >> > I would like to volunteer as RM for this release. I found the >> > >>guidelines >> > >> > here: >> > >> > >> > >> > http://incubator.apache.org/guides/releasemanagement.html >> > >> > >> > >> > Where would the mentors see the bar for this initial release? >> Anything >> > >> > beyond the check list to watch out for, advice for prioritization? >> > >> > >> > >> > Thanks, >> > >> > Thomas >> > >> > >> > >> >> > >> > >> > >
