sameersbn / sameersbn/docker-gitlab
Status update for this repository - abandoned/maintenance mode ?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
For a few months now, this repository has not been updated to current GitLab versions (I think the last 'new' version this repo moved to was 12.7 from January, while we are currently at 12.9). Issues asking about 12.8 have also not been addressed.
Certainly in times like these it's understandable if less effort is available to be put into (free!) projects, but if this repository is not going to get updated to current GitLab versions anymore, or if updates will considerably lag behind (before now it was always a few days at most), I would ask that the users be informed about that, so we can make educated decisions - for example, I don't mind a lower release schedule for my private instance, but at work, we have strict guidelines for how many version numbers we are allowed to lag behind in core tools like GitLab.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Begin by reviewing the repository's release history and the unresolved questions about GitLab 12.8 and 12.9; done would require a clear maintainer decision and an updated user-facing status about supported versions and release cadence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100