This repository has been archived by the owner on Oct 2, 2023. It is now read-only.
chore: add maintenance status to top of README #2236
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
14 out of 25 issues on the first page of https://github.com/bazelbuild/rules_docker/issues have no replies. Issues like #2213 show that releases are stalled right now. https://github.com/bazelbuild/rules_docker/pulse/monthly shows four commits touching four files in the last month, one of those was me removing an external docs link. I discussed this with the maintainers on the discussion thread, and we agreed to put up a message for now to better set user expectations. I also alerted the Bazel team to this change in the SIG meeting on March 7, see https://docs.google.com/document/d/1YGCYAGLzTfqSOgRFVsB8hDz-kEoTgTEKKp9Jd07TJ5c/edit# To be clear: I greatly appreciate the effort that the current two maintainers have made, this is not a vote-of-no-confidence in their engineering abilities or desire to make this repo great. It's just acknowledging the current state of the resources (time and funding) available for this project at the present time.
alexeagle
requested review from
gravypod,
linzhp,
pcj,
smukherj1 and
uhthomas
as code owners
linzhp
approved these changes
Mar 21, 2023
adamsb6
pushed a commit
to rockset/rules_docker
that referenced
this pull request
Apr 18, 2023
14 out of 25 issues on the first page of https://github.com/bazelbuild/rules_docker/issues have no replies. Issues like bazelbuild#2213 show that releases are stalled right now. https://github.com/bazelbuild/rules_docker/pulse/monthly shows four commits touching four files in the last month, one of those was me removing an external docs link. I discussed this with the maintainers on the discussion thread, and we agreed to put up a message for now to better set user expectations. I also alerted the Bazel team to this change in the SIG meeting on March 7, see https://docs.google.com/document/d/1YGCYAGLzTfqSOgRFVsB8hDz-kEoTgTEKKp9Jd07TJ5c/edit# To be clear: I greatly appreciate the effort that the current two maintainers have made, this is not a vote-of-no-confidence in their engineering abilities or desire to make this repo great. It's just acknowledging the current state of the resources (time and funding) available for this project at the present time.
copybara-service bot
pushed a commit
to bazelbuild/bazel
that referenced
this pull request
Aug 18, 2023
I believe it is no longer maintained, so I'm following the process outlined in the Bazel documentation: https://bazel.build/community/recommended-rules#demotion Here's some data on rules_docker: - Maintenance signals have gone down significantly in the last year: https://oss-compass.org/analyze/snbnfub0?range=1Y - Hasn't been released in a year - Second-most-recent commit was mine from about five months ago, adding the "minimal maintenance mode" bazelbuild/rules_docker#2236 - there's more context in that PR. - Never reached 1.0 rules_oci seems like the replacement. - It has strong adoption testimonials bazel-contrib/rules_oci#299 - Version is 1.2 with semver guarantees Closes #19123. PiperOrigin-RevId: 558059587 Change-Id: I4c175a79b3429947fa036a22165839dcf285b28d
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
14 out of 25 issues on the first page of https://github.com/bazelbuild/rules_docker/issues have no replies.
Issues like #2213 show that releases are stalled right now.
https://github.com/bazelbuild/rules_docker/pulse/monthly shows four commits touching four files in the last month, one of those was me removing an external docs link.
I discussed this with the maintainers on the discussion thread, and we agreed to put up a message for now to better set user expectations. I also alerted the Bazel team to this change in the SIG meeting on March 7, see https://docs.google.com/document/d/1YGCYAGLzTfqSOgRFVsB8hDz-kEoTgTEKKp9Jd07TJ5c/edit#
To be clear: I greatly appreciate the effort that the current two maintainers have made, this is not a vote-of-no-confidence in their engineering abilities or desire to make this repo great. It's just acknowledging the current state of the resources (time and funding) available for this project at the present time.