Sorry, I am totally lost.
1. As far as I know release candidates are immutable. We don't change
the content of the packages as it requires new vote. Let's say people A
votes to a an RC0 but RC0 is changed in the mean time.
For me vote := proposal + deadline
If the content of the proposal is changed we need new vote.
If some additional modification is required we need a new RC (rc1 in our
case). At least this was the practice what I have seen until now.
2. feel free to commit any required pom changes, you don't need to
create PR (unless you would like to have one, or you would like to test
the release with CI, but that's also possible with branch)
The release manager role is a full authorization to create tags or push
technical version bumps.
3.
>> I had not committed the older tags and released the artificats. It
was only in my fork. The release wiki asked for waiting until voting.
I think it can be confusing. This ask is about the final tag
(ozone-1.0.0) not about rc tags and commits (like ozone-1.1.0-rc0 or
ozone-1.1.0-rc1). As we don't know (yet) which rc will be passed we need
to wait with pushing the final tag. But rc tags can be pushed and
shared. As rc0 is failed, we need an ozone-1.1.0-rc1 tag. (I suggest to
remove rc0 from the branch name and use ozone-1.1 as branch name. With
this pattern we can release ozone-1.1.0 and ozone-1.1.1 from the same
branch)
As an example this is what we have from 1.0:
c53eb9fa17c919be937441887f4d041479155c5e refs/tags/ozone-1.0.0-RC0
5b1dcf52b31b4a3fea877baa8824dd815fc40930 refs/tags/ozone-1.0.0-RC1
Summary: I suggest to...
1. commit/push all the required pom.xml version changes
2. create a new rc package (rc1) from the last valid commit
3. tag it with ozone-1.1.0-rc1
3. Share the tagged commit in a new rc1 mail thread (to make it
possible to double check if the src package contains the tagged version
of the source)
((At least this is my understanding about the common release process))
Sorry if it was not clear from the wiki page (I will try to update it
and clarify if we have an agreement)
And thanks for all the work to make ozone 1.1.0 real: <3
Thanks,
Marton
On 4/7/21 5:01 PM, Prashant Pogde wrote:
All the artifacts are getting release from a committed fork and PR is pending at
https://github.com/apache/ozone/pull/2125
<https://github.com/apache/ozone/pull/2125>
This pending release PR has just the final pom.xml changes + release tag.
Other than this, I believe all the other changes required for 1.1.0 release are
already in the apache:1.1.0-RC0 branch.
Once We get a Yes vote, this can be merged with upstream and would be in
official apache:1.1.0-RC0 branch.
Regards,
Prashant
On Apr 7, 2021, at 7:55 AM, Prashant Pogde <ppo...@cloudera.com> wrote:
I had not committed the older tags and released the artificats. It was only in
my fork. The release wiki asked for waiting until voting.
Therefore I could delete the older tag from my fork. I also removed the older
artifacts to start from a clean state.
I think we can continue this as RC0.
On Apr 6, 2021, at 11:54 PM, Elek, Marton <e...@apache.org> wrote:
On 4/7/21 8:32 AM, Prashant Pogde wrote:
Refreshed artifacts at
https://repository.apache.org/content/repositories/orgapachehadoop-1301/
<https://repository.apache.org/content/repositories/orgapachehadoop-1301/>
Binaries at
https://home.apache.org/~prashantpogde/ozone-1.1.0-rc0/
<https://home.apache.org/~prashantpogde/ozone-1.1.0-rc0/>
Thanks for the update Prashant,
As far as I understand they are new artifacts with new content:
Do we need a new rc1 thread which also shares the used commit / tag and defines
the new deadline? Might be more clear...
What do you think?
Thanks,
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
