CONTRIBUTING: Describe project and milestone usage #8038
Conversation
CONTRIBUTING.md
Outdated
| GitHub conventions | ||
| ------------------- | ||
|
|
||
| Each `Cabal`/`cabal-install` release has a corresponding GitHub Project and milestone. |
There was a problem hiding this comment.
"Each major"? 3.6.3 doesn't have a project. 3.6 does.
There was a problem hiding this comment.
Isn't 3.6.3 a minor release?
There was a problem hiding this comment.
Yeah, I meant new 3.x numbers, because that seems to be what we really plan for, while 3.x.y are reactive.
CONTRIBUTING.md
Outdated
|
|
||
| Each `Cabal`/`cabal-install` release has a corresponding GitHub Project and milestone. | ||
| A ticket is included in a release's project if the release manager is tenatively | ||
| planning on including a fix for the ticket in the release. |
There was a problem hiding this comment.
(add -- i.e. if they are actively seeking someone to work on the ticket)
There was a problem hiding this comment.
only the release manager can do it, then? do we have release manager now? If we mention that role, would not be good to talk about who is or are the individuals in docs (or at least give some tip on how to know it)?
There was a problem hiding this comment.
I think it's the release manager for that release. But we are more distributed/chaotic than that, so the release manager is not known until the night of the release. So, perhaps, "release managers" meaning all maintainers?
CONTRIBUTING.md
Outdated
| planning on including a fix for the ticket in the release. | ||
|
|
||
| By contrast, a ticket is milestoned to a given release if we are open to accepting | ||
| a fix in that release. |
There was a problem hiding this comment.
(add - i.e. if we would very much appreciate someone working on it, but are not committing to actively sourcing someone to work on it)
|
CI seems to be stuck here and randomly failing in another PR, so let me rebase and see how it goes to get a better picture what's going on with our CI. |
|
@Mergifyio rebase |
✅ Branch has been successfully rebased |
andreabedini
force-pushed
the
bgamari-patch-1
branch
from
d079551 to
1ba5fc2
Compare
|
@Mergifyio rebase |
✅ Branch has been successfully rebased |
andreabedini
force-pushed
the
bgamari-patch-1
branch
from
1ba5fc2 to
2fa985f
Compare
ulysses4ever
force-pushed
the
bgamari-patch-1
branch
from
2fa985f to
4468526
Compare
|
Dear reviewers! I appended a commit addressing your comments. Show time?! |
ulysses4ever
added
squash+merge me
Please include the following checklist in your PR:
Please also shortly describe how you tested your change. Bonus points for added tests!