Roadmap Gitlab
Roadmap for Gitlab
Safe GitLab with Mercurial for a simple workflow (pull, push and merge requests with topics)
(about a month and half)
- Fix GitLab's tests (about one week)
- Display Mercurial hashes everywhere in the UI (about three days)
- view file -> hash in the dropdown
- other locations not spotted yet
- Display Mercurial hashes in the URLs (about a week)
- Hide the SSH-related UI (about two days)
- warning about the SSH key
- configuration of the SSH keys
- other locations not spotted yet
- Hide all changing actions from the web UI (about three days)
- on a merge request, “remove source branch”
- on a commit, “modify commit message”
- on a project, “Add Changelog”, “License”, “Contribution Guidelines” or “CI”, “Add a new file/branch/tag”
- other locations not spotted yet
- Remove the .hg folder as well as the .git folder when deleting a project (about a day)
- move the .hg folders away as the .git folders are
- really delete the .git folders as the .git folders are
- Display Mercurial instructions (about a day)
- tags (repository without tags)
- merge request (“check out branch”, “merge locally”, “command line”)
- other locations not spotted yet
- Disable conflict resolution in the web UI (about two days)
- Fix the permissions on branches and topics
- hg-git should forward credentials to Git (about a week)
- Administrator pass-through permission should be removed (about an hour)
Additional features
(about a month)
- Be able to import a repository from any hg url (about two days)
- Button to display the obsolete revisions in the graph (about a week)
- Fork another user's repository (about a week)
- Support ssh access to Mercurial repository (about a week)
- Enhance the
remote: remote:
output of push (about a day) - Allow large pushs through workhorse (about two weeks)
Option 1: Replace Git by Mercurial in GitLab backend
(about two months)
-
Wait for gitaly to be fully used by Gilab CE (soon-ish?)
would be in 10.0 according to announced date on the project page (Q4 2017) and the GitLab milestone dates (Sep 22, 2017 for 10.0), but we use 10.1.4 and rugged may still be in use at some places
-
Write a gitaly-like API for Mercurial (about a month)
-
Modify GitLab pages to match the Mercurial workflow (true branches, topics) (about a month)
Option 2: Make GitLab able to manage both Git and Mercurial projects
(about two months)
- Add a property on GitLab projects to qualify their type (Git or Mercurial) (about a week)
- Adapt the screens for a Mercurial workflow (true branches, topics) depending on the project (about two months)