[GitHub] [daffodil-vscode] stevedlawrence commented on issue #78: Publish 1.0.0 release candidate

[GitBox <gi...@apache.org>]

stevedlawrence commented on issue #78:
URL: https://github.com/apache/daffodil-vscode/issues/78#issuecomment-1034942499


   Below is a summary of what must be done for the release process.
   
   Although this is the minimum, I would suggest that you create a wiki page and release candidate container, similar to what we do with Daffodil, so that the process can be fully documented and automated to avoid potential errors. It also gives us a chance to review the release process. It might even be worth modifying the release candidate container to support choosing to build the extension or daffodil--much of the process will be very similar.
   
   https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow
   
   Here's the summary:
   
   1. A [DISCUSS] email thread should be started to determine if a release should be started. That should be open for 72 hours.
    
   1. Assuming the community agrees, a release manager is decided to perform the actions. Technically this person does not need to be a committer, but it makes the process much easier if they have committer privileges, so I recommend that.
   
   1. That files that will be voted on must be created. A source zip and/or tar archive are mandatory. Convenience binaries (i.e. the .vsix file) are optional, but I recommend that we do those as well.
   
   1. All release files must be signed with the release managers gpg key (see the release workflow for the gpg key creation process) and sha512sum hashes created.
   
   1. All files and signatures/hashes must be uploaded to https://dist.apache.org/repos/dist/dev/daffodil/
    
   1. A webpage on daffodil.apache.org should be created for to describe this release, including links to downloads, signature, hashes, etc.
   
   5. The git repo should be tagged with a rc version number
   
   6. A VOTE email must be sent out, and be open for at least 72 hours.
   
   5. The vote passes if it receives at least 3 binding +1's, and more +1's than -1's
   
   6. The release is moved from the dist.a.o/dev directory to dist.a.o/release/
   
   7. A git tag is created
   
   8. An announce email is sent out


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org