Hey Szabi, Thanks for the reach out!
I've already seen emails about those commits, and I plan to cherry pick them to the 1.4.6 release branch this evening. Until: Could you please add a comment about these changes on the umbrella JIRA? (you could also open a subtask wit links if that's easier on your side). The rest I'll handle. Many thanks in advance, Attila <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 20, 2017 at 4:11 PM, Szabolcs Vasas <[email protected]> wrote: > Hi Attila, > > Thank you for creating the branch, I have just one comment. > It turned out that some third party tests were failing on trunk branch so I > submitted 2 patches (https://issues.apache.org/jira/browse/SQOOP-3194 , > https://issues.apache.org/jira/browse/SQOOP-3198) which were committed > today. Shall we include these changes in the release too? > > Regards, > Szabolcs > > On Fri, Jun 16, 2017 at 9:18 AM, Attila Szabó <[email protected]> wrote: > > > Dear community, > > > > First of all many thanks for the valuable feedbacks. As agreed the > > releasing process had been started. > > > > We do have an umbrella JIRA for this: > > https://issues.apache.org/jira/browse/SQOOP-3199 > > > > All feedbacks, comments more than welcome here. > > > > A short status: > > As you can see sanitize, branching, changelog, doc+version updates is > > already done. > > > > To finalize the scope of 1.4.7 I'd like to kindly ask all of you to check > > the CHANGELOG.txt (release notes) and check if every JIRA ticket is there > > what is vital on your side for 1.4.7. > > > > According to the current plans/status: > > all of the issues which are not fixed (TODO, in progress) right now, and > > connected to 1.4.7 (please check > > https://issues.apache.org/jira/projects/SQOOP/versions/12329683 for > > details) are meant to move to 1.5.0 unless there is any specific reason > to > > include in 1.4.7 and thus changing the scope/delaying the process. > > > > The content of 1.4.7 branch should be changed only in sync with the > > umbrella JIRA, and all new commits on the trunk from now is considered as > > part of 1.5.0. > > > > In case of any questions, suggestions, change requests please use this > mail > > thread or the umbrella JIRA. > > > > I'll keep you updated with the progress of the release. > > > > Best regards, > > Attila > > > > > > On Wed, May 31, 2017 at 11:18 AM, Boglarka Egyed <[email protected]> > > wrote: > > > > > Hi Attila, > > > > > > +1 to the idea and many thanks for driving this! > > > > > > I don't have any specific requirement or concern so feel free to > proceed > > > with the proposed timeline. > > > > > > Thanks, > > > Bogi > > > > > > On Wed, May 31, 2017 at 4:51 AM, Ying Cao <[email protected]> > > > wrote: > > > > > >> Hi Attila, > > >> > > >> This is really great, +1 to the idea ! > > >> > > >> 2017-05-30 23:40 GMT+08:00 Szabolcs Vasas <[email protected]>: > > >> > > >> > Hi Attila, > > >> > > > >> > Thank you for taking the initiative, big +1 to the idea! > > >> > > > >> > Regards, > > >> > Szabolcs > > >> > > > >> > On Tue, May 30, 2017 at 1:40 PM, Anna Szonyi <[email protected]> > > >> wrote: > > >> > > > >> > > Hi Attila, > > >> > > > > >> > > This would be really great! Please let me know if I can help with > > >> > anything! > > >> > > > > >> > > Thanks, > > >> > > Anna > > >> > > > > >> > > On Thu, May 25, 2017 at 6:20 PM, Attila Szabó <[email protected]> > > >> wrote: > > >> > > > > >> > > > Hello everyone, > > >> > > > > > >> > > > In the past few months we've mentioned it a few times that it > > would > > >> > make > > >> > > > sense to create a new release of Sqoop from the current trunk > > >> version > > >> > > > (1.4.7). > > >> > > > > > >> > > > IMHO this is the right time to move forward with this topic. > > >> > > > First of all because the latest release is 2 years old (1.4.6 > was > > >> > > released > > >> > > > in 2015 May), and it would make a great impact for the end users > > to > > >> > > deliver > > >> > > > all of the changes we as a community have made since. > > >> > > > As a second argument, recently we were able to onboard quite a > few > > >> new > > >> > > > contributor (including but not limited to Illya Yalovyy, Ying > Cao, > > >> > Eric > > >> > > > Lin, Chris Teoh, Dmitry Zagorulkin), and as a recognition of > their > > >> > work, > > >> > > > I'd like to ensure their commits gets into a release as soon as > > >> > possible. > > >> > > > Third: recently Anna, Bogi and Szabi were super active on the > > front > > >> of > > >> > > > stabilizing and improving the tests, the build system and so, > > >> however > > >> > > > according to my feelings the current status quo (waiting for a > > minor > > >> > > > version change with bigger changes) holding them back from more > > >> > > fundamental > > >> > > > improvements (I guess this is the reason why the Gradle/Maven > new > > >> build > > >> > > > sytem is still in progress, and the conversation around feature > > >> > branches > > >> > > > started). I think it would make a great impact for the whole > > >> community > > >> > > and > > >> > > > the product itself, if we would be able to remove this burden > from > > >> > their > > >> > > > shoulders, and thus they would be able to focus on bigger > > >> > > > changes/challenges. > > >> > > > > > >> > > > Because of the reasons mentioned above, on the top of my > existing > > >> > duties, > > >> > > > I'd like to help the community's life by owning the 1.4.7 > release > > >> > > process, > > >> > > > and starting the release with branching the trunk as of > 2017-06-01 > > >> > (next > > >> > > > Friday) PST 8PM, and finishing the whole process latest by the > end > > >> of > > >> > > June. > > >> > > > > > >> > > > Of course before starting even creating the related JIRA tasks, > > >> plans, > > >> > > the > > >> > > > branching, etc. I'd like to collect the inputs from all of you > if > > >> this > > >> > > fits > > >> > > > your plan/requirements/etc. > > >> > > > > > >> > > > Looking forward hearing all of your thoughts, concerns, pros and > > >> cons. > > >> > > > > > >> > > > Best regards, > > >> > > > Attila Szabo > > >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > -- > > >> > Szabolcs Vasas > > >> > Software Engineer > > >> > <http://www.cloudera.com> > > >> > > > >> > > > > > > > > > > > > -- > Szabolcs Vasas > Software Engineer > <http://www.cloudera.com> >
