stevedlawrence commented on pull request #61: URL: https://github.com/apache/daffodil-vscode/pull/61#issuecomment-998879586
Note that we can distribute through github releases, but it must only be for convenience (like how the marketplace is allowed but only for convenience). "Official" releases must be made available via downloads.apache.org from our website. In general, I thin apache perfer that githug releases not be used in favor of website or something like a marketplace, because github will automatically create "release" in some cases, and it can be confusing what is actually an official release that was voted on. The release process should be something like: 1. Create a zip of the source and a vsix file that is expected to be the final release. The .vsix is considered a convenience binary. 2. This is called an "-rc1", but rc1 doesn't actually appear anywhere in the source or the convenience binary. Usually it's just the name of a directory in an ASF svn repo (e.g. https://dist.apache.org/repos/dist/dev/daffodil/3.2.1-rc2/) staging files for a vote. 3. We vote on releasing the source and the convenience .vsix binary 4. When the vote passes, we rename the directory to remove the -rc1 label, and then we can upload the convenience binaries where it is most convenient. For example, in Daffodil this is maven central, our webiste, and an RPM repo. For vsix ideally it would be the marketplace, and maybe github releases if it makes sense. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
