Expired
Milestone
Aug 7, 2017–Apr 24, 2018
10.0
Display by
Error fetching burnup chart data
Burndown chart
Remaining
Burnup chart
Total
Completed
Unstarted Issues (open and unassigned)
7
Ongoing Issues (open and assigned)
2
Completed Issues (closed)
24
- Remove TLSv1 support from defaults
- Remove old gitlab_git_http_server configuration
- Remove PG 9.2 from package with GitLab 10
- Remove the need for manual config edit on first installation
- Create standalone registry container for Helm
- Nightly builds using wrong version prefix
- Release rake task should fail when it finds to artifacts
- Add retry option to CI jobs
- Geo: Proper services are not enabled by default in 10.0
- Mattermost 4.2: Upcoming breaking changes
- Make Redis persistence settings configurable
- Error thrown in master when booting in docker
- error update from 9.4.5 to 9.5.1
- PostgreSQL detection and upgrading since 10.0.0-rc5 (Ubuntu 16.10)
- Consul servers cannot run consul commands by default
- Fix omnibus-ctl wrapper to allow `*` in arguments
- PG HA setup trying to connect to db as gitlab-consul user
- update_databases assumes a populated databases.json
- Improve deprecation of git_data_dirs
- Error in Openshift Template
- Rework SSH private key handling for Geo nodes
- Don't add duplicate entries to pg_auth
- FGU September 13 by Build team
- Investigate including policycoreutils as a runtime dependency in order to be able to use semanage
Loading
Loading
Loading