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

Prepare release candidate #133

Closed
arnoweiss opened this issue Dec 16, 2024 · 0 comments · Fixed by #139
Closed

Prepare release candidate #133

arnoweiss opened this issue Dec 16, 2024 · 0 comments · Fixed by #139
Labels
enhancement New feature or request triage all new issues awaiting classification

Comments

@arnoweiss
Copy link
Contributor

arnoweiss commented Dec 16, 2024

What's missing?

When the content is finished, we need

  1. a commit that sets the specStatus config option to base and
  2. sets the title of the spec to "Eclipse Decentralized Claims Protocol v1.0-RC1"
  3. a tag v1.0-RC1 on the release commit
  4. to change the redirect in .github/scripts/index.html to point to latest release candidate
  5. (again) adjusted w3id referrals (currently going to resources/v1.0 but the deployment will be v1.0/resources
  6. adjust the textual description of the context URI in the base spec
  7. specifically put in the release date

and then another commit

  1. a commit that sets the specStatus config option to base and
  2. sets the title of the spec to "Eclipse Decentralized Claims Protocol v1.0-RC2"
  3. remove the releasedate

Why should it be in the spec?

proper versioning

Where should this be added?

mentioned locations

More context

The referrals will stay broken until there's a tag 1.0 unless we change them with each release candidate.

@arnoweiss arnoweiss added enhancement New feature or request triage all new issues awaiting classification labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage all new issues awaiting classification
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant