Thanks for the catch, Colm. It looks like a mess and we should bring those backends back.
Regards, Kai -----Original Message----- From: Colm O hEigeartaigh [mailto:[email protected]] Sent: Friday, May 05, 2017 7:45 PM To: Zheng, Kai <[email protected]> Cc: [email protected]; Li, Jiajia <[email protected]> Subject: Re: Kerby 1.0 GA Hi Kai, I'll call a vote today if I get some feedback on the email I sent about the backends - Jiajia committed a merge which commented out most of the backends. Colm. On Fri, May 5, 2017 at 12:41 PM, Zheng, Kai <[email protected]> wrote: > Sounds great. Thanks Colm! Do we need to vote before we have release > artifacts or after that? Hope we can make it soon and won't block the > Hadoop 3.0 Alpha3 releasing. > > Regards, > Kai > > -----Original Message----- > From: Colm O hEigeartaigh [mailto:[email protected]] > Sent: Friday, May 05, 2017 4:38 PM > To: Zheng, Kai <[email protected]> > Cc: Li, Jiajia <[email protected]>; [email protected] > Subject: Re: Kerby 1.0 GA > > If it's all the same, I'd prefer to use "1.0.0" as this is the more > common convention at Apache. Yes, no problem at all with minor > releases. We could release 1.0.1 or 1.1.0 etc. > > Colm. > > On Fri, May 5, 2017 at 1:52 AM, Zheng, Kai <[email protected]> wrote: > > > Thanks Colm for the taking! > > > > > > > > I thought both work for me meaning the same thing. If changing the > > POMs to point to 1.0.0-GA could be easier, maybe we could use it? > > > > > > > > By the way, after this major release, we could release often, given > > important bug fixes or features. I noticed left issues are all > > targeted to 2.0.0, we could have 1.1.0 version for some of the left > issues. > > > > > > > > Regards, > > > > Kai > > > > > > > > *From:* Colm O hEigeartaigh [mailto:[email protected]] > > *Sent:* Thursday, May 04, 2017 10:22 PM > > *To:* Li, Jiajia <[email protected]> > > *Cc:* [email protected]; Zheng, Kai <[email protected]> > > > > *Subject:* Re: Kerby 1.0 GA > > > > > > > > Any thoughts on what the release version should be? We're using > > 1.0.0-GA in JIRA, but I'm thinking just "1.0.0" for the poms. > > > > Colm. > > > > > > > > On Thu, May 4, 2017 at 3:20 PM, Colm O hEigeartaigh > > <[email protected]> > > wrote: > > > > Yes, I will take care of the release today. > > > > Colm. > > > > > > > > On Thu, May 4, 2017 at 2:16 PM, Li, Jiajia <[email protected]> wrote: > > > > Hi Colm, > > > > I've removed the open JIRAs to a future release. > > Our network is very bad for dong the release process, so could take > > the release work? > > 1.0.0 GA will used in the next Hadoop release version > > 3.0.0-alpha3(May 15), so we should finish the release before it. > > > > Thanks > > Jiajia > > > > -----Original Message----- > > From: Colm O hEigeartaigh [mailto:[email protected]] > > Sent: Thursday, May 4, 2017 7:33 PM > > To: Zheng, Kai <[email protected]> > > Cc: [email protected] > > Subject: Re: Kerby 1.0 GA > > > > OK, I've merged a bunch of fixes and I'm now done for the 1.0.0-GA > release. > > I see there are still a few open JIRAs. When do you anticipate > > calling the vote? > > > > Colm. > > > > On Wed, May 3, 2017 at 1:01 PM, Colm O hEigeartaigh > > <[email protected]> > > wrote: > > > > > There are a lot of open issues (including one "in progress") for > > > the 1.0.0-GA release in JIRA: > > > > > > https://issues.apache.org/jira/browse/DIRKRB/fixforversion/1233277 > > > 5 > > > > > > It would be a good idea to go through the issues and decide which > > > will be fixed for the GA release, and which should be moved to a > > > future > > release. > > > > > > Colm. > > > > > > On Sun, Apr 30, 2017 at 1:11 AM, Zheng, Kai <[email protected]> > wrote: > > > > > >> This makes sense. The GA should clean such kinds of codes. > > >> > > >> Regards, > > >> Kai > > >> > > >> -----Original Message----- > > >> From: Colm O hEigeartaigh [mailto:[email protected]] > > >> Sent: Wednesday, April 26, 2017 6:38 PM > > >> To: [email protected] > > >> Subject: Re: Kerby 1.0 GA > > >> > > >> One improvement I'd like to see before the 1.0 GA release is to > > >> improve the exception handling. There are many examples of catch > > >> statements that just have a printStackTrace() leading to NPEs > > >> down the line. Apart from that, +1 from me on the release: > > >> > > >> find . -name "*.java" -path "*/main/*" | xargs grep > > >> "printStackTrace()" | wc -l > > >> 30 > > >> > > >> Colm. > > >> > > >> On Wed, Apr 26, 2017 at 3:31 AM, Zheng, Kai <[email protected]> > > wrote: > > >> > > >> > Sounds cool! Thanks Jiajia for taking this step forward. > > >> > > > >> > Regards, > > >> > Kai > > >> > > > >> > -----Original Message----- > > >> > From: Li, Jiajia [mailto:[email protected]] > > >> > Sent: Wednesday, April 26, 2017 9:54 AM > > >> > To: [email protected] > > >> > Subject: RE: Kerby 1.0 GA > > >> > > > >> > Sorry for wrong typo. > > >> > > > >> > Hi all, > > >> > > > >> > We are going to start the Kerby 1.0.0 GA release progress. > > >> > It's more than one year since our last release 1.0.0-RC2, we > > >> > have added lots of new features and bug fixes. > > >> > And this release will include some blocking issues for Hadoop > > >> > and > > >> > 1.0.0 GA will impact the next Hadoop release version 3.0.0-alpha3. > > >> > > > >> > Regards, > > >> > Jiajia > > >> > > > >> > -----Original Message----- > > >> > From: Li, Jiajia [mailto:[email protected]] > > >> > Sent: Wednesday, April 26, 2017 9:49 AM > > >> > To: [email protected] > > >> > Subject: Kerby 1.0 GA > > >> > > > >> > Hi all, > > >> > > > >> > We are going to start the Kerby 1.0.0 GA release progress. > > >> > It's more than one year since our last release 1.0.0-RC2, we > > >> > have added lots of new features and bug fixes. > > >> > And this release will include some blocking issues for Hadoop > > >> > and > > >> > 1.0.0 GA will impact the next Hadoop release version 3.0.0-alpha1. > > >> > > > >> > Regards, > > >> > Jiajia > > >> > > > >> > > >> > > >> > > >> -- > > >> Colm O hEigeartaigh > > >> > > >> Talend Community Coder > > >> http://coders.talend.com > > >> > > > > > > > > > > > > -- > > > Colm O hEigeartaigh > > > > > > Talend Community Coder > > > http://coders.talend.com > > > > > > > > > > > -- > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > > > > > > > > > -- > > > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > > > > > > > > > -- > > > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
