Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1 for all the reasons outlined. On Tue, May 26, 2015 at 6:13 PM, Thejas Nair thejas.n...@gmail.com wrote: +1 - This is great for users who want to take longer to upgrade from hadoop-1 and care mainly for bug fixes and incremental features, rather than radical new features. - The ability to release initial 2.x releases marked as alpha/beta also helps to get users to try it out, and also lets them choose what is right for them. - This also lets developers focus on major new features without the burden of maintaining hadoop-1 compatibility. On Tue, May 26, 2015 at 11:41 AM, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan. -- Nothing better than when appreciated for hard work. -Mark
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1 -- Lefty On Wed, May 27, 2015 at 3:21 PM, Alexander Pivovarov apivova...@gmail.com wrote: +1 On May 27, 2015 10:45 AM, Vikram Dixit K vikram.di...@gmail.com wrote: +1 for all the reasons outlined. On Tue, May 26, 2015 at 6:13 PM, Thejas Nair thejas.n...@gmail.com wrote: +1 - This is great for users who want to take longer to upgrade from hadoop-1 and care mainly for bug fixes and incremental features, rather than radical new features. - The ability to release initial 2.x releases marked as alpha/beta also helps to get users to try it out, and also lets them choose what is right for them. - This also lets developers focus on major new features without the burden of maintaining hadoop-1 compatibility. On Tue, May 26, 2015 at 11:41 AM, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan. -- Nothing better than when appreciated for hard work. -Mark
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1 On May 27, 2015 10:45 AM, Vikram Dixit K vikram.di...@gmail.com wrote: +1 for all the reasons outlined. On Tue, May 26, 2015 at 6:13 PM, Thejas Nair thejas.n...@gmail.com wrote: +1 - This is great for users who want to take longer to upgrade from hadoop-1 and care mainly for bug fixes and incremental features, rather than radical new features. - The ability to release initial 2.x releases marked as alpha/beta also helps to get users to try it out, and also lets them choose what is right for them. - This also lets developers focus on major new features without the burden of maintaining hadoop-1 compatibility. On Tue, May 26, 2015 at 11:41 AM, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan. -- Nothing better than when appreciated for hard work. -Mark
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1 - This is great for users who want to take longer to upgrade from hadoop-1 and care mainly for bug fixes and incremental features, rather than radical new features. - The ability to release initial 2.x releases marked as alpha/beta also helps to get users to try it out, and also lets them choose what is right for them. - This also lets developers focus on major new features without the burden of maintaining hadoop-1 compatibility. On Tue, May 26, 2015 at 11:41 AM, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
[VOTE] Stable releases from branch-1 and experimental releases from master
We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
I'm +1 too. I think it is important to allow the Hive development community to move forward with these big features while supporting users who want a more conservative set of features and more backwards compatibility. .. Owen On Tue, May 26, 2015 at 12:29 PM, Sergey Shelukhin ser...@hortonworks.com wrote: +1. I want to clarify about being not production ready though. That shouldn’t mean known shortage of functionality (other than the deprecated parts like hadoop-1), imho, just the fact that they are recent with big features enabled. They should be production ready modulo the higher expected bug count. On 15/5/26, 11:41, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1. I think this will help a lot in having a clean way to experiment with new features. ‹Vaibhav On 5/26/15, 12:29 PM, Sergey Shelukhin ser...@hortonworks.com wrote: +1. I want to clarify about being not production ready though. That shouldn¹t mean known shortage of functionality (other than the deprecated parts like hadoop-1), imho, just the fact that they are recent with big features enabled. They should be production ready modulo the higher expected bug count. On 15/5/26, 11:41, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1. I want to clarify about being not production ready though. That shouldn’t mean known shortage of functionality (other than the deprecated parts like hadoop-1), imho, just the fact that they are recent with big features enabled. They should be production ready modulo the higher expected bug count. On 15/5/26, 11:41, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1 This would protect those who might not want to lose workflow features from the stable releases for the coming year. I¹m not looking forward to a branch merge tearing out the hive CLI client away in a single chop. Having a master branch where we can plan for the future is essential and this is an established way to do that without inconveniencing the existing user base. Also, git - I couldn¹t have handled this before we moved over onto it. Cheers, Gopal On 5/26/15, 11:41 AM, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
Re: [VOTE] Stable releases from branch-1 and experimental releases from master
+1 I hope that important bugfixes (and functionality) will be backported from trunk to branch-1 for a reasonable amount of time given that many people will continue to rely on branch-1. Thanks, chris On Tuesday, May 26, 2015 1:45 PM, Gopal Vijayaraghavan gop...@apache.org wrote: +1 This would protect those who might not want to lose workflow features from the stable releases for the coming year. I¹m not looking forward to a branch merge tearing out the hive CLI client away in a single chop. Having a master branch where we can plan for the future is essential and this is an established way to do that without inconveniencing the existing user base. Also, git - I couldn¹t have handled this before we moved over onto it. Cheers, Gopal On 5/26/15, 11:41 AM, Alan Gates alanfga...@gmail.com wrote: We have discussed this for several weeks now. Some concerns have been raised which I have tried to address. I think it is time to vote on it as our release plan. To be specific, I propose: Hive makes a branch-1 from the current master. This would be used for 1.3 and future 1.x releases. This branch would not deprecate existing functionality. Any new features in this branch would also need to be put on master. An upgrade path for users will be maintained from one 1.x release to the next, as well as from the latest 1.x release to the latest 2.x release. Going forward releases numbered 2.x will be made from master. The purpose of these releases will be to enable users to get access to new features being developed in Hive and allow developers to get feedback. It is expected that for a while these releases will not be production ready and will be clearly so labeled. Some legacy features, such as Hadoop 1 and MapReduce, will no longer be supported in the master. Any critical bug fixes (security, incorrect results, crashes) fixed in master will also be ported to branch-1 for at least a year. This time period may be extended in the future based on the stability and adoption of 2.x releases. Based on Hive's bylaws this release plan vote will be open for 3 days and all active committers have binding votes. Here's my +1. Alan.
