Sqoop developer community,It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.

To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.

This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!

It would definitely be nice to get a release of Sqoop 1 out asap. I am definitely interested in driving a Sqoop release. I was the release manager for Apache Flume 1.3.1, so I am quite familiar with the process of driving a release. So, I'd like to volunteer to drive the release. Thanks, Hari -- Hari ShreedharanOn Friday, February 1, 2013 at 7:18 PM, Jarek Jarcec Cecho wrote:

> Sqoop developer community,> It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.> > To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.> > This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!> > Jarcec> > Links:> 1: http://s.apache.org/ARW> >

Sqoop developer community,It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.

To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.

This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!

Since Hari is interested in doing this with prior experience in doing this, i think he is a better qualified candidateThanksVenkat

> From: [EMAIL PROTECTED]> Subject: RE: Release planning for 1.4.3> Date: Fri, 1 Feb 2013 19:35:26 -0800> To: [EMAIL PROTECTED]> > Jarcec> > I can volunteer to take this with guidance from you and others> > Venkat> ________________________________> From: Jarek Jarcec Cecho> Sent: 2/1/2013 7:19 PM> To: [EMAIL PROTECTED]> Subject: Release planning for 1.4.3> > Sqoop developer community,> It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.> > To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.> > This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!> > Jarcec> > Links:> 1: http://s.apache.org/ARW

Hi Hari and Venkat,I'm excited to hear that you are both interested in becoming Release managers. Whereas previous experience with doing release might be helpful, it's definitely not a requirement. I believe that one of the main reasons for driving release this way is to help the community volunteer to learn more about Apache Sqoop and the Apache Software Foundation in general. It's my job as a release mentor to supplement any previous knowledge and experience.

I would like to help anyone who is interested to learn more about Sqoop and who wants to contribute to the project. Thus I would like to help you both. Sadly it make sense to have only one release manager for one particular release. I was thinking about this during the weekend and whereas I can't do any promises, I believe that Sqoop PMC will be open to follow the release mentor and community volunteer model for next release as well. As a result I would suggest that one of you might be driving this 1.4.3 release and the another one might drive next release - for example 1.99.2 that hopefully will happen in near future. What do you think guys?

Jarcec

On Fri, Feb 01, 2013 at 07:45:08PM -0800, Venkatesan Ranganathan wrote:> Since Hari is interested in doing this with prior experience in doing this, i think he is a better qualified candidate> Thanks> Venkat> > > From: [EMAIL PROTECTED]> > Subject: RE: Release planning for 1.4.3> > Date: Fri, 1 Feb 2013 19:35:26 -0800> > To: [EMAIL PROTECTED]> > > > Jarcec> > > > I can volunteer to take this with guidance from you and others> > > > Venkat> > ________________________________> > From: Jarek Jarcec Cecho> > Sent: 2/1/2013 7:19 PM> > To: [EMAIL PROTECTED]> > Subject: Release planning for 1.4.3> > > > Sqoop developer community,> > It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.> > > > To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.> > > > This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!> > > > Jarcec> > > > Links:> > 1: http://s.apache.org/ARW>

Hi JarcecThanks for the thoughtful comments. I think it would be good for someone with RM experience to work on the release management tasks for something like a 1.4.3 release as there is a large installed base of customers. I believe that will make the release smoother.While I can definitely learn and contribute in that role (I have been in this industry for embarrassingly too long in various capacities!) , I feel Hari is a better candidate for the release at hand for aforementioned reasonsWe can definitely revisit this for the next opportunity.ThanksVenkat

> Date: Mon, 4 Feb 2013 10:29:46 -0800> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re: Release planning for 1.4.3> > Hi Hari and Venkat,> I'm excited to hear that you are both interested in becoming Release managers. Whereas previous experience with doing release might be helpful, it's definitely not a requirement. I believe that one of the main reasons for driving release this way is to help the community volunteer to learn more about Apache Sqoop and the Apache Software Foundation in general. It's my job as a release mentor to supplement any previous knowledge and experience.> > I would like to help anyone who is interested to learn more about Sqoop and who wants to contribute to the project. Thus I would like to help you both. Sadly it make sense to have only one release manager for one particular release. I was thinking about this during the weekend and whereas I can't do any promises, I believe that Sqoop PMC will be open to follow the release mentor and community volunteer model for next release as well. As a result I would suggest that one of you might be driving this 1.4.3 release and the another one might drive next release - for example 1.99.2 that hopefully will happen in near future. What do you think guys?> > Jarcec> > On Fri, Feb 01, 2013 at 07:45:08PM -0800, Venkatesan Ranganathan wrote:> > Since Hari is interested in doing this with prior experience in doing this, i think he is a better qualified candidate> > Thanks> > Venkat> > > > > From: [EMAIL PROTECTED]> > > Subject: RE: Release planning for 1.4.3> > > Date: Fri, 1 Feb 2013 19:35:26 -0800> > > To: [EMAIL PROTECTED]> > > > > > Jarcec> > > > > > I can volunteer to take this with guidance from you and others> > > > > > Venkat> > > ________________________________> > > From: Jarek Jarcec Cecho> > > Sent: 2/1/2013 7:19 PM> > > To: [EMAIL PROTECTED]> > > Subject: Release planning for 1.4.3> > > > > > Sqoop developer community,> > > It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.> > > > > > To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.> > > > > > This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!> > > > > > Jarcec> > > > > > Links:> > > 1: http://s.apache.org/ARW> >

Thanks for giving me this opportunity. I'd definitely like to do Sqoop 1.4.3. I would also gladly help Venkatesan if he would want to be the RM for Sqoop 1.99.2 (if the Sqoop PMC agrees, of course). ThanksHari

> Hi Jarcec> Thanks for the thoughtful comments. I think it would be good for someone with RM experience to work on the release management tasks for something like a 1.4.3 release as there is a large installed base of customers. I believe that will make the release smoother.> While I can definitely learn and contribute in that role (I have been in this industry for embarrassingly too long in various capacities!) , I feel Hari is a better candidate for the release at hand for aforementioned reasons> We can definitely revisit this for the next opportunity.> Thanks> Venkat> > > Date: Mon, 4 Feb 2013 10:29:46 -0800> > From: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > Subject: Re: Release planning for 1.4.3> > > > Hi Hari and Venkat,> > I'm excited to hear that you are both interested in becoming Release managers. Whereas previous experience with doing release might be helpful, it's definitely not a requirement. I believe that one of the main reasons for driving release this way is to help the community volunteer to learn more about Apache Sqoop and the Apache Software Foundation in general. It's my job as a release mentor to supplement any previous knowledge and experience.> > > > I would like to help anyone who is interested to learn more about Sqoop and who wants to contribute to the project. Thus I would like to help you both. Sadly it make sense to have only one release manager for one particular release. I was thinking about this during the weekend and whereas I can't do any promises, I believe that Sqoop PMC will be open to follow the release mentor and community volunteer model for next release as well. As a result I would suggest that one of you might be driving this 1.4.3 release and the another one might drive next release - for example 1.99.2 that hopefully will happen in near future. What do you think guys?> > > > Jarcec> > > > On Fri, Feb 01, 2013 at 07:45:08PM -0800, Venkatesan Ranganathan wrote:> > > Since Hari is interested in doing this with prior experience in doing this, i think he is a better qualified candidate> > > Thanks> > > Venkat> > > > > > > From: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > Subject: RE: Release planning for 1.4.3> > > > Date: Fri, 1 Feb 2013 19:35:26 -0800> > > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > > > > > Jarcec> > > > > > > > I can volunteer to take this with guidance from you and others> > > > > > > > Venkat> > > > ________________________________> > > > From: Jarek Jarcec Cecho> > > > Sent: 2/1/2013 7:19 PM> > > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > Subject: Release planning for 1.4.3> > > > > > > > Sqoop developer community,> > > > It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.> > > > > > > > To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.> > > > > > > > This is a great opportunity for enthusiastic contributor to make a difference for the project and learn more about the workings of Apache Sqoop and Apache Software Foundation in general. Please do not hesitate and respond to this email if you're interested!

Thanks Hari. Thanks for agreeing to do this release management workVenkat

> Date: Mon, 4 Feb 2013 16:34:34 -0800> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re: Release planning for 1.4.3> > Hi guys,> > Thanks for giving me this opportunity. I'd definitely like to do Sqoop 1.4.3. I would also gladly help Venkatesan if he would want to be the RM for Sqoop 1.99.2 (if the Sqoop PMC agrees, of course). > > > Thanks> Hari> > -- > Hari Shreedharan> > > On Monday, February 4, 2013 at 4:09 PM, Venkatesan Ranganathan wrote:> > > Hi Jarcec> > Thanks for the thoughtful comments. I think it would be good for someone with RM experience to work on the release management tasks for something like a 1.4.3 release as there is a large installed base of customers. I believe that will make the release smoother.> > While I can definitely learn and contribute in that role (I have been in this industry for embarrassingly too long in various capacities!) , I feel Hari is a better candidate for the release at hand for aforementioned reasons> > We can definitely revisit this for the next opportunity.> > Thanks> > Venkat> > > > > Date: Mon, 4 Feb 2013 10:29:46 -0800> > > From: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > Subject: Re: Release planning for 1.4.3> > > > > > Hi Hari and Venkat,> > > I'm excited to hear that you are both interested in becoming Release managers. Whereas previous experience with doing release might be helpful, it's definitely not a requirement. I believe that one of the main reasons for driving release this way is to help the community volunteer to learn more about Apache Sqoop and the Apache Software Foundation in general. It's my job as a release mentor to supplement any previous knowledge and experience.> > > > > > I would like to help anyone who is interested to learn more about Sqoop and who wants to contribute to the project. Thus I would like to help you both. Sadly it make sense to have only one release manager for one particular release. I was thinking about this during the weekend and whereas I can't do any promises, I believe that Sqoop PMC will be open to follow the release mentor and community volunteer model for next release as well. As a result I would suggest that one of you might be driving this 1.4.3 release and the another one might drive next release - for example 1.99.2 that hopefully will happen in near future. What do you think guys?> > > > > > Jarcec> > > > > > On Fri, Feb 01, 2013 at 07:45:08PM -0800, Venkatesan Ranganathan wrote:> > > > Since Hari is interested in doing this with prior experience in doing this, i think he is a better qualified candidate> > > > Thanks> > > > Venkat> > > > > > > > > From: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > > Subject: RE: Release planning for 1.4.3> > > > > Date: Fri, 1 Feb 2013 19:35:26 -0800> > > > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > > > > > > > Jarcec> > > > > > > > > > I can volunteer to take this with guidance from you and others> > > > > > > > > > Venkat> > > > > ________________________________> > > > > From: Jarek Jarcec Cecho> > > > > Sent: 2/1/2013 7:19 PM> > > > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > > Subject: Release planning for 1.4.3> > > > > > > > > > Sqoop developer community,> > > > > It has been several months since our last release and there has been steady activity on the codebase with about 68 issues resolved [1]. Some of them are usual bugfixes, but we also added major new functionality. For example we added support for stored procedures in export tool, upsert functionality into MySQL connector and/or schema support for Microsoft SQL Server and PostgreSQL. It will therefore be appropriate time to do a maintenance release of the project with version number 1.4.3.> > > > > > > > > > To that effect Sqoop PMC has decided to keep the slight change from the usual release process that was introduced during last release. Instead of having one of the committers running the release, I've stepped out as a release mentor that will guide someone from the community that will volunteer to become the release manager.

Hari,I'm looking forward to work with you on the release. Please do not hesitate and contact me any time if you will any help. There are currently two "How to Release" wiki pages. First older one is describing how to release Sqoop 1 and it's based on SVN [1]. The newer one is written for git, but describes only Sqoop 2 [2]. Thus we will to merge information from both wiki pages to get information how to release Sqoop 1 on git.

On Mon, Feb 04, 2013 at 05:24:17PM -0800, Venkatesan Ranganathan wrote:> Thanks Hari. Thanks for agreeing to do this release management work> Venkat> > > Date: Mon, 4 Feb 2013 16:34:34 -0800> > From: [EMAIL PROTECTED]> > To: [EMAIL PROTECTED]> > Subject: Re: Release planning for 1.4.3> > > > Hi guys,> > > > Thanks for giving me this opportunity. I'd definitely like to do Sqoop 1.4.3. I would also gladly help Venkatesan if he would want to be the RM for Sqoop 1.99.2 (if the Sqoop PMC agrees, of course). > > > > > > Thanks> > Hari> > > > -- > > Hari Shreedharan> > > > > > On Monday, February 4, 2013 at 4:09 PM, Venkatesan Ranganathan wrote:> > > > > Hi Jarcec> > > Thanks for the thoughtful comments. I think it would be good for someone with RM experience to work on the release management tasks for something like a 1.4.3 release as there is a large installed base of customers. I believe that will make the release smoother.> > > While I can definitely learn and contribute in that role (I have been in this industry for embarrassingly too long in various capacities!) , I feel Hari is a better candidate for the release at hand for aforementioned reasons> > > We can definitely revisit this for the next opportunity.> > > Thanks> > > Venkat> > > > > > > Date: Mon, 4 Feb 2013 10:29:46 -0800> > > > From: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > Subject: Re: Release planning for 1.4.3> > > > > > > > Hi Hari and Venkat,> > > > I'm excited to hear that you are both interested in becoming Release managers. Whereas previous experience with doing release might be helpful, it's definitely not a requirement. I believe that one of the main reasons for driving release this way is to help the community volunteer to learn more about Apache Sqoop and the Apache Software Foundation in general. It's my job as a release mentor to supplement any previous knowledge and experience.> > > > > > > > I would like to help anyone who is interested to learn more about Sqoop and who wants to contribute to the project. Thus I would like to help you both. Sadly it make sense to have only one release manager for one particular release. I was thinking about this during the weekend and whereas I can't do any promises, I believe that Sqoop PMC will be open to follow the release mentor and community volunteer model for next release as well. As a result I would suggest that one of you might be driving this 1.4.3 release and the another one might drive next release - for example 1.99.2 that hopefully will happen in near future. What do you think guys?> > > > > > > > Jarcec> > > > > > > > On Fri, Feb 01, 2013 at 07:45:08PM -0800, Venkatesan Ranganathan wrote:> > > > > Since Hari is interested in doing this with prior experience in doing this, i think he is a better qualified candidate> > > > > Thanks> > > > > Venkat> > > > > > > > > > > From: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > > > Subject: RE: Release planning for 1.4.3> > > > > > Date: Fri, 1 Feb 2013 19:35:26 -0800> > > > > > To: [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> > > > > > > > > > > > Jarcec> > > > > > > > > > > > I can volunteer to take this with guidance from you and others> > > > > > > > > > > > Venkat> > > > > > ________________________________

NEW: Monitor These Apps!

All projects made searchable here are trademarks of the Apache Software Foundation.
Service operated by Sematext