merge main which includes process changes into v1.1 #784
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add PR review process for 2021. * Avoid GitHub id auto-linking. Co-authored-by: David I. Lehn <[email protected]> * Update README.md Co-authored-by: Manu Sporny <[email protected]> Co-authored-by: Manu Sporny <[email protected]> Co-authored-by: David I. Lehn <[email protected]> Co-authored-by: Brent Zundel <[email protected]>
kdenhartog
force-pushed
the
kdh/v1.1-add-process
branch
from
bca9e00 to
16f2e34
Compare
kdenhartog
changed the title
TallTed
reviewed
Jul 29, 2021
| - 1 substantive update (v1.2?) | ||
| - VC Test Suite Refactoring | ||
| - Start planning VC v2 Work, request a rechartering 3-6 months before end of | ||
| year to keep VC WG functioning. |
There was a problem hiding this comment.
Suggested change
| year to keep VC WG functioning. | |
| year to keep VC WG functioning |
TallTed
reviewed
Jul 29, 2021
| - [v1] Fixing a specific bug | ||
| - [v1] Update examples in the spec to make them modern | ||
| - [v2] VC `@context` needs updating, possibly with security vocab modularized | ||
| into smaller components instead of all included into a large context file. |
There was a problem hiding this comment.
Suggested change
| into smaller components instead of all included into a large context file. | |
| into smaller components instead of all included into a large context file |
brentzundel
approved these changes
Jul 30, 2021
|
@TallTed I agree with your suggested changes, but I'm going to leave them out in this scenario in order to keep alignment between main and V1.1 as close as possible. Main reason being I just want this in so that when commits are targeted at main and I need to update to V1.1 I don't want any wonky git overrides to slow things down. We can merge these separately onto main first and then merge them downstream to this one after if you'd like. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is here to bring main and v1.1 back in alignment. The specific commit I'm looking to bring into V1.1 is the changes to the readme which are defining the process of how we will go about handling changes in the maintenance WG as agreed to via the CCG and merged already in main.
Preview | Diff