You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Nabarun Nag <nn...@vmware.com> on 2021/03/22 16:27:47 UTC
[INFO] Apache Geode 1.14.0 Release Manager
Hi everyone,
I hope you all are doing well. This is to inform the Apache Geode community that I will be volunteering as the Release Manager for 1.14.0 release. Thank you, Owen, for all the work that has been done to get the release to this point.
As for backporting, as a developer, you just need to create a PR against the support/1.14 branch, and you are done. As a release manager, I will take over from there.
Just ensure the following:
* The PR is a cherry-pick (cherry-pick -x) of a commit that is already in develop
* Ensure that there are no merge conflicts.
Regards
Nabarun Nag
Re: [INFO] Apache Geode 1.14.0 Release Manager
Posted by Nabarun Nag <nn...@vmware.com>.
Hi Alberto,
We are starting tests this weekend, and with the condition that the tests are all good, we should have a release candidate for voting next week. I will keep you updated!
Regards
Nabarun
________________________________
From: Alberto Gomez <al...@est.tech>
Sent: Tuesday, August 24, 2021 2:58 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager
Hi Naba,
Is there any new information about the 1.14 Geode release?
Thanks in advance,
Alberto
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, June 1, 2021 6:46 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager
Hi Alberto,
For releasing 1.14 we are waiting on two more backports.
GEODE-8609 - DUnit runners were not checking the logs for suspicious errors/fatal messages in VMs that were being restarted in a test. A fix is ready and is in PR review stage[1]
GEODE-9289 - A problem with Cluster Configuration where a new locator sends its configuration to an old locator, the old locator is unable to deserialize it, causes NPEs and clears out certain fields in the configuration. A PR is ready and is in review phase but this will need GEODE-8609 checked in first.[2]
Once these two PRs are merged and backported, we are going to start the process for voting on the release branch and release candidates. My personal estimate is that we can start with the voting process within next week, if we do not detect any serious issues.
Please do reach out if you require any additional information.
Regards,
Nabarun
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F6526&data=04%7C01%7Cnnag%40vmware.com%7C60c8954316a542ace8e608d966e5b527%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637653959043733474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZZDeZkEiKWyaEGqMjxvZu7T6rZKhqsSD%2BnYDx6Fd060%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F6495&data=04%7C01%7Cnnag%40vmware.com%7C60c8954316a542ace8e608d966e5b527%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637653959043733474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cP9cmUb1tVoULPx6brwoChMSpeJiEU0AFFTgKhwsC6M%3D&reserved=0
________________________________
From: Alberto Gomez <al...@est.tech>
Sent: Monday, May 31, 2021 8:08 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager
Hi Naba,
Can you please provide some information about how the 1.14 release is going and if is there any planned date for it?
Thanks in advance,
Alberto
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Monday, March 22, 2021 5:27 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [INFO] Apache Geode 1.14.0 Release Manager
Hi everyone,
I hope you all are doing well. This is to inform the Apache Geode community that I will be volunteering as the Release Manager for 1.14.0 release. Thank you, Owen, for all the work that has been done to get the release to this point.
As for backporting, as a developer, you just need to create a PR against the support/1.14 branch, and you are done. As a release manager, I will take over from there.
Just ensure the following:
* The PR is a cherry-pick (cherry-pick -x) of a commit that is already in develop
* Ensure that there are no merge conflicts.
Regards
Nabarun Nag
Re: [INFO] Apache Geode 1.14.0 Release Manager
Posted by Alberto Gomez <al...@est.tech>.
Hi Naba,
Is there any new information about the 1.14 Geode release?
Thanks in advance,
Alberto
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, June 1, 2021 6:46 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager
Hi Alberto,
For releasing 1.14 we are waiting on two more backports.
GEODE-8609 - DUnit runners were not checking the logs for suspicious errors/fatal messages in VMs that were being restarted in a test. A fix is ready and is in PR review stage[1]
GEODE-9289 - A problem with Cluster Configuration where a new locator sends its configuration to an old locator, the old locator is unable to deserialize it, causes NPEs and clears out certain fields in the configuration. A PR is ready and is in review phase but this will need GEODE-8609 checked in first.[2]
Once these two PRs are merged and backported, we are going to start the process for voting on the release branch and release candidates. My personal estimate is that we can start with the voting process within next week, if we do not detect any serious issues.
Please do reach out if you require any additional information.
Regards,
Nabarun
[1] https://github.com/apache/geode/pull/6526
[2] https://github.com/apache/geode/pull/6495
________________________________
From: Alberto Gomez <al...@est.tech>
Sent: Monday, May 31, 2021 8:08 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager
Hi Naba,
Can you please provide some information about how the 1.14 release is going and if is there any planned date for it?
Thanks in advance,
Alberto
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Monday, March 22, 2021 5:27 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [INFO] Apache Geode 1.14.0 Release Manager
Hi everyone,
I hope you all are doing well. This is to inform the Apache Geode community that I will be volunteering as the Release Manager for 1.14.0 release. Thank you, Owen, for all the work that has been done to get the release to this point.
As for backporting, as a developer, you just need to create a PR against the support/1.14 branch, and you are done. As a release manager, I will take over from there.
Just ensure the following:
* The PR is a cherry-pick (cherry-pick -x) of a commit that is already in develop
* Ensure that there are no merge conflicts.
Regards
Nabarun Nag
Re: [INFO] Apache Geode 1.14.0 Release Manager
Posted by Nabarun Nag <nn...@vmware.com>.
Hi Alberto,
For releasing 1.14 we are waiting on two more backports.
GEODE-8609 - DUnit runners were not checking the logs for suspicious errors/fatal messages in VMs that were being restarted in a test. A fix is ready and is in PR review stage[1]
GEODE-9289 - A problem with Cluster Configuration where a new locator sends its configuration to an old locator, the old locator is unable to deserialize it, causes NPEs and clears out certain fields in the configuration. A PR is ready and is in review phase but this will need GEODE-8609 checked in first.[2]
Once these two PRs are merged and backported, we are going to start the process for voting on the release branch and release candidates. My personal estimate is that we can start with the voting process within next week, if we do not detect any serious issues.
Please do reach out if you require any additional information.
Regards,
Nabarun
[1] https://github.com/apache/geode/pull/6526
[2] https://github.com/apache/geode/pull/6495
________________________________
From: Alberto Gomez <al...@est.tech>
Sent: Monday, May 31, 2021 8:08 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [INFO] Apache Geode 1.14.0 Release Manager
Hi Naba,
Can you please provide some information about how the 1.14 release is going and if is there any planned date for it?
Thanks in advance,
Alberto
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Monday, March 22, 2021 5:27 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [INFO] Apache Geode 1.14.0 Release Manager
Hi everyone,
I hope you all are doing well. This is to inform the Apache Geode community that I will be volunteering as the Release Manager for 1.14.0 release. Thank you, Owen, for all the work that has been done to get the release to this point.
As for backporting, as a developer, you just need to create a PR against the support/1.14 branch, and you are done. As a release manager, I will take over from there.
Just ensure the following:
* The PR is a cherry-pick (cherry-pick -x) of a commit that is already in develop
* Ensure that there are no merge conflicts.
Regards
Nabarun Nag
Re: [INFO] Apache Geode 1.14.0 Release Manager
Posted by Alberto Gomez <al...@est.tech>.
Hi Naba,
Can you please provide some information about how the 1.14 release is going and if is there any planned date for it?
Thanks in advance,
Alberto
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Monday, March 22, 2021 5:27 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [INFO] Apache Geode 1.14.0 Release Manager
Hi everyone,
I hope you all are doing well. This is to inform the Apache Geode community that I will be volunteering as the Release Manager for 1.14.0 release. Thank you, Owen, for all the work that has been done to get the release to this point.
As for backporting, as a developer, you just need to create a PR against the support/1.14 branch, and you are done. As a release manager, I will take over from there.
Just ensure the following:
* The PR is a cherry-pick (cherry-pick -x) of a commit that is already in develop
* Ensure that there are no merge conflicts.
Regards
Nabarun Nag