Hi, "checkstyle mark a build as failure" is currently done in the "build.quality" profile. So we can use this as default profile and if somebody want a "fast" build he can use the "build.fast" profile.
Hence, I agree (+1) with "checkstyle mark a build as failure" and I agree (+1) with the code clean up at Wednesday (18th). Kind regards, Michael On 13.09.13 15:33, "Amend, Christian" <[email protected]> wrote: >Hi, > >I agree with both points (Release and CleanUp). > >I would suggest that we make our checkstyle mark a build as failure when >checkstyle issues are found. To give developers time to clean up a bit I >would do this on Wednesday 18th September. > >WDYT? > >Best Regards, >Christian > >-----Original Message----- >From: Bolz, Michael [mailto:[email protected]] >Sent: Freitag, 13. September 2013 08:25 >To: [email protected] >Subject: Re: Jira / Release > >Hi, > >I agree with making a first release (+1). >However, I think we should run a "code clean up" to get rid of the >Checkstyle/PMD issue before this release. >Therefore I created an issue >(https://issues.apache.org/jira/browse/OLINGO-17). > >In addition we could remove the documentation tasks from the >"FixForVersion" list (or move them to next version). >IMHO documentation/tutorials/howtos are really important, but should not >necessarily coupled with a fix version. > >Kind regards, >Michael > > > >On 12.09.13 10:17, "Klevenz, Stephan" <[email protected]> wrote: > >>The project is established in meantime and we should think about to make >>a first release. We still have coding activities and discussions. >> >>Can we agree on to create Jira issues for tracking coding activities? At >>least for major ones or for things that need to be done for a first >>release should be tagged with a release version: >> >>https://issues.apache.org/jira/browse/OLINGO/fixforversion/12324804 >> >>If all issues are done then we can think about to make a release. >> >>WDYT? >> >>Stephan >
