Understanding release process of Apache Incubator answer

[surapuramakhil]

Hi can I know when following branch get updated

1. main branch - I see an release has been made 8 hours ago but changes of those release are in main branch from a a long time two - three weeks prior release

can you explain the process you follow especially from main branch to tag creation

can you also explain when you use Dev branch i.e Dev vs main branch

Also when will be release branch i.e release/ and release tags will be created? and its timeline with release announcements

I just shocked by seeing, an release announcement has been made but those changes are already in main branch for more than 2-3 weeks (depending of when it got merged)

[surapuramakhil]

@fenbox

[LinkinStars]

can you explain the process you follow especially from main branch to tag creation

can you also explain when you use Dev branch i.e Dev vs main branch

FYI: https://answer.apache.org/community/contributing#branch-organization

I just shocked by seeing, an release announcement has been made but those changes are already in main branch for more than 2-3 weeks (depending of when it got merged)

Projects in Apache go through two rounds of voting before they are released. So the actual release depends on how long it takes to vote.

FYI:

• https://www.apache.org/legal/release-policy.html
• https://answer.apache.org/community/how-to-release/

[surapuramakhil]

Ah I didn't understood the process completely.

based on my reading voting refers to peer Dev testing (Apache members or member of dev@answer.apache.org.) and approval. https://answer.apache.org/community/contributing/#helping-with-version-releases

correct me, if my understanding is wrong.
for releases an release branch will be created release/, new feature are added to release branch, testing and fixes are added into release branch. I notice a sign off that's happening, is it a sign off of segment fault team? and code get merged to main branch. Now its sent to Apache voting process for approval of release (Am i correct?)

can you explain what exactly you mean by release? is it creating Apache signed artifacts for public to use an trusted version of Apache answer.

[LinkinStars]

Thank you. I'll briefly describe the steps for release:

1. Create tag with RC
2. Package all artifacts and sign them
3. Release the vote for the dev phase and wait for it to finish
4. Release the vote for the general phase and wait for it to finish
5. Create the tag without RC and announce the release.

can you explain what exactly you mean by release? is it creating Apache signed artifacts for public to use an trusted version of Apache answer.

Yes, according to Apache's requirements we will sign and verify the release content.