Rename "Complete" project stage to "Feature-Complete", add new "Sunsetting" stage #1654
Conversation
…tting" stage Goals: 1. Provide more transparency and clarity around project lifecycle by distinguishing feature complete projects from sunsetting ones. 2. Make it easier for project to transition to "Feature-complete" without necessarily implying that they're sunsetting.
|
@tobie overall this looks solid to me. And I believe we should audit our projects once this is merged, there are likely projects that should have one of the new statuses applied. (e.g. globalizejs/globalize#949) The only question I had was related to the flowchart, I was unsure what was meant by the following: 
|
|
Oh, thanks for catching this, folks! I thought I had a fixed it. That's a search and replace gone wrong! ( |
Signed-off-by: Tobie Langel <[email protected]>
Signed-off-by: Tobie Langel <[email protected]>
Could not agree more. We really want to normalize being more transparent about where a project is in its lifecycle. |
Signed-off-by: Tobie Langel <[email protected]>
|
Notes from today's CPC call: This was presented as a way to make it easier for maintainers to be transparent about their intentions wrt to the maturity of their project. In particular, this changes allows projects that are feature complete, but don't have an intention to sunset to say so, without suggesting that they are on a track for archiving their projects. |
PROJECT_PROGRESSION.md
Outdated
| Projects may be granted Feature-complete status through CPC consensus and with the approval of the maintainers of the project. | ||
|
|
||
| An OpenJS software project is Complete, when the developers responsible for it are no longer providing feature development or enhancements and are solely providing security updates and bug fixes. The software doesn't disappear; it remains functional but is not under active development. | ||
| In cases where the project maintainers aren't responding after having been repeatedly contacted through appropriate channels about the CPC's intent to move the project to Feature-complete stage, the CPC may proceed with the stage change to either Feature-complete, Sunsetting, or Archived without approval from the maintainers. |
There was a problem hiding this comment.
without approval from the maintainers
This language may put some people off. I wonder if we could expand on this to make it clear this is "an emergency measure only" or something? Like we know that, but someone reading this at face value may not see it in the same positive light.
There was a problem hiding this comment.
I agree with the sentiment. However, that's existing language that I'm just moving around, so I'd be inclined to leave it as is.
Co-authored-by: Wes Todd <[email protected]> Signed-off-by: Tobie Langel <[email protected]>
Co-authored-by: Wes Todd <[email protected]> Signed-off-by: Tobie Langel <[email protected]>
Signed-off-by: Tobie Langel <[email protected]>
tobie
changed the title
|
Thanks @wesleytodd. Appreciate the thoughtful review and the reference to PACKAGE-SUPPORT.md which I'm adding to the inventory of resources for the CRA (tracking here: orcwg/cra-hub#293). |
5 participants
Goals:
Q&A
Q: Why rename "Complete" to "Feature-Complete"?
The name "Complete" wasn't super clear to folks and people weren't super thrilled of adopting it. I believe this new name makes it easier to understand what it means.
Q: What does the new "sunsetting" stage changes?
It splits the "Complete" stage into two:
Q: What's makes you move from "Feature-Complete" to "Sunsetting"?
The only difference between the two is that you've announced an EOL date. That's it.