Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standarise the way to publish releases #122

Closed
Emily-Jiang opened this issue Aug 13, 2019 · 2 comments
Closed

Standarise the way to publish releases #122

Emily-Jiang opened this issue Aug 13, 2019 · 2 comments
Labels
Architecture board Issues across more MP specifications

Comments

@Emily-Jiang
Copy link
Member

Emily-Jiang commented Aug 13, 2019

Since spec html and pdf are not in maven central. In the past, the pdfs and htmls are attached to the releases. However, it is not convenient as they have to be downloaded for viewing.

In the recent release architecture changes, all of the docs and javadocs are uploaded to here. When releasing MicroProfile reactive messaging, I used the following format, which is much more user friendly.

I updated MicroProfile config to use this format. All other specs should adopt this format for improvement.

We also need to update microprofile.io to list all spec/pdf. I've filed this issue on microprofile-site repo.

@Emily-Jiang Emily-Jiang added the Architecture board Issues across more MP specifications label Aug 13, 2019
@OndroMih
Copy link
Contributor

Ideally, the Jenkins release job would use GitHub API to generate the description for the release, including links to Javadocs and spec documents and info about the maven artifact.

@Emily-Jiang
Copy link
Member Author

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Architecture board Issues across more MP specifications
Projects
None yet
Development

No branches or pull requests

2 participants