Hi Brahma, Thank you for indicating the points we missed. Though all points are important and we should take actions in accordance with them, they are not critical blockers for this release in my opinion. Let me explain the rationale.
For #3 and #4, we should reflect your comment so that we could trace the changes done in this release later and users could know the roadmap toward the future, so I'll start with updating JIRA issues soon. But we can do them in parallel with or after the release and they are not the defects of the release artifacts themselves, so I don't think they are blockers. For #1, we should discuss the next version number on the master branch, but it's independent on branch-2.0 and that decision doesn't affect the current release artifacts at all. So that's not a blocker too. Regarding #2, the number after hyphen in the full version comes from HDP's versioning semantics, and we're using it as the "Release" number for RPM package, as explained in AMBARI-25859 [1]. Based on that, incrementing it for each RC is not that bad, because it doesn't affect users and users are often unaware of that number. So it's not also a blocker, IMHO. That being said, maybe we should separately discuss when we increment or not that number. Finally, here's a side note for Zhiguo (since I think this is your first release management): The release vote adopts majority approval [2], so getting a binding -1 doesn't mean the vote failed immediately. If there are three binding +1s and the number of binding +1s are larger than -1s, and you don't think the issues pointed out are critical, you still can move forward the release, as its manager. [1]: https://issues.apache.org/jira/browse/AMBARI-25859 [2]: https://www.apache.org/foundation/voting.html#ReleaseVotes Kengo Seki <sek...@apache.org> On Sat, Feb 25, 2023 at 3:50 PM Battula, Brahma Reddy <bbatt...@visa.com.invalid> wrote: > > -1 (binding). > > > 1) You Need to change master pom version[1], We need to discuss next version > what should be. > 2) For every RC, we no need to bump the version string. Let's not make so > clumsy. > 3) Mark jira's which are marked for 2.0.0, Looks so many jira's not having > the fix version itself and some are not closed[2]. > 4) We need to have separate wiki for metrics releases notes and roadmap.? > > > Regards, > Brahma > > 1. https://github.com/apache/ambari-metrics/blob/master/pom.xml > 2. https://issues.apache.org/jira/browse/AMBARI-25865 > https://issues.apache.org/jira/browse/AMBARI-25860 > > > On 24/02/23, 3:38 PM, "Zhiguo Wu" <wuzhi...@apache.org > <mailto:wuzhi...@apache.org>> wrote: > > > Hello Community, > > > This is a call for vote to release Apache Ambari Metrics 2.0.0 RC1 > > > The release candidates: > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fambari%2Fambari-metrics-2.0.0-rc1%2F&data=05%7C01%7Cbbattula%40visa.com%7Cbcfabf17cb6c47e3d7d608db164f19bb%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638128301210893555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eoc2ALVgjKKB32uDcMPnD9qhuOE%2FWghrMsPffzYrEa8%3D&reserved=0 > > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fambari%2Fambari-metrics-2.0.0-rc1%2F&data=05%7C01%7Cbbattula%40visa.com%7Cbcfabf17cb6c47e3d7d608db164f19bb%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638128301210893555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eoc2ALVgjKKB32uDcMPnD9qhuOE%2FWghrMsPffzYrEa8%3D&reserved=0> > > > Git tag for the release: > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari-metrics%2Ftree%2Frelease-2.0.0-rc1&data=05%7C01%7Cbbattula%40visa.com%7Cbcfabf17cb6c47e3d7d608db164f19bb%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638128301210893555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2GmBJWVMG7t6gMjpx55sbgYF7j3ktQz0ItGghdk3E5c%3D&reserved=0 > > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari-metrics%2Ftree%2Frelease-2.0.0-rc1&data=05%7C01%7Cbbattula%40visa.com%7Cbcfabf17cb6c47e3d7d608db164f19bb%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638128301210893555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2GmBJWVMG7t6gMjpx55sbgYF7j3ktQz0ItGghdk3E5c%3D&reserved=0> > > > Hash for the release tag: > 339afc60221efd910913f82b2b956fbfd6dcaba7 > > > The artifacts have been signed with Key > D3D5CF25076873C9AA068C0D8F062A5450E25685, which can be found in the KEYS > file: > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fambari%2FKEYS&data=05%7C01%7Cbbattula%40visa.com%7Cbcfabf17cb6c47e3d7d608db164f19bb%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638128301210893555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jVz2tdiZeFgEnV7saVbWMtHXdt1UCLDmSSBwRvwJPig%3D&reserved=0 > > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fambari%2FKEYS&data=05%7C01%7Cbbattula%40visa.com%7Cbcfabf17cb6c47e3d7d608db164f19bb%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638128301210893555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jVz2tdiZeFgEnV7saVbWMtHXdt1UCLDmSSBwRvwJPig%3D&reserved=0> > > > The vote will be open for at least 72 hours or until the necessary number > of votes are reached. > > > Please vote accordingly: > > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > > Best Regards, > Zhiguo Wu > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org For additional commands, e-mail: dev-h...@ambari.apache.org
