docs: Add roadmap document for 2019 into 2020 #567
Merged
Conversation
This file contains 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
|
picked a bad example :-p |
matthewfeickert
force-pushed
the
docs/add-ROADMAP
branch
from
e37e1d7
to
8cad7ce
Compare
I'm not directly against it, but it seemed more like documentation to me and there doesn't seem to be as clear of an agreed upon path to put it in as |
kratsg
approved these changes
Sep 25, 2019
This is a document form of Issue 561 which will allow developers to mark off in the ROADMAP document how their PR contributes to it. As it is possible for the checklist in Issue 561 to get out of sync with developement this should help serve as a source of "truth" about developement status.
The roadmap will be treated like a normal version controlled file and be updated and changed as the plans for the project move
matthewfeickert
force-pushed
the
docs/add-ROADMAP
branch
from
8cad7ce
to
d2cb8aa
Compare
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.
Description
Resolves #563
This is a document form of Issue #561 which will allow developers to mark off in the ROADMAP document how their PR contributes to it. As it is possible for the checklist in Issue #561 to get out of sync with development this should help serve as a source of "truth" about development status.
Use:
For any PR that a developer completes that is associated with the pyhf 2019 into 2029 Roadmap project they mark the item in the roadmap that they have completed in the PR, or amend the roadmap. Once it is merged in they can amend the Issue #561 to reflect this for easier web viewing of developers and non-developers.
Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: