[meta] 8.17

Q1 Goal

• In Q1 2017 we want to iterate on idea to production and auto deploy.
• Using Google Container Engine (GKE) everyone should be able to go from 0 to a container cluster with GitLab, chat and projects that are auto deployed.
• We're hoping to fuel the power of idea to production with monitoring of system, app and business metrics through prometheus.

Priorities

1. Add value to EE
2. Realize our vision
3. Make GitLab.com a viable SaaS

Links

• 8.17 CE
• 8.17 EE

Get ready for 9.0

We will also have two people working on the breaking changes for 9.0 until they are done: https://gitlab.com/groups/gitlab-org/issues?scope=all&state=opened&milestone_title=9.0&label_name%5B%5D=breaking+change

Deliverable issues

Big

• EE Starter Add "Export" to issues list https://gitlab.com/gitlab-org/gitlab-ee/issues/1480 PM @regisF | BE @jamedjo | FE @samrose3 | UX @dimitrieh
• EE Premium License Finder https://gitlab.com/gitlab-org/gitlab-ee/issues/1125 PM @regisF | FE @brycepj | UX @hazelyang
• EE Starter Squash https://gitlab.com/gitlab-org/gitlab-ee/issues/150 PM @victorwu | FE @mikegreiling | UX @pedroms | BE @smcgivern
• EE Starter Auditor user https://gitlab.com/gitlab-org/gitlab-ee/issues/1439 PM @mydigitalself | FE @jivanvl | BE @timothyandrew | UX @cperessini
• EE Premium Geo: Disaster Recovery https://gitlab.com/gitlab-org/gitlab-ee/issues/846 BE @dbalexandre
• EE Starter Get ElasticSearch in shape https://gitlab.com/gitlab-com/infrastructure/issues/388 BE @nick.thomas

Smaller

• ~"q1-vision" #26687 (closed) Create new file from issue for repo-less project using new branch button | PM @victorwu | FE @annabeldunstone | UX @pedroms

• https://gitlab.com/gitlab-org/gitlab-ee/issues/1589 Deployboard | FE @filipa | UX @tauriedavis

• #19949 (closed): [Epic] Remove usage of "build" | FE: @filipa | UX @dimitrieh

  • #17662 (closed): Rename "Builds" to "CI/CD Pipelines" in a few places | FE: @filipa | UX @dimitrieh

• #26205 (closed) Add existing issues to issue board | PM @victorwu | UX @cperessini | FE @iamphill

• https://gitlab.com/gitlab-org/gitlab-ee/issues/1587 Create and edit issue board with milestone | PM @victorwu | UX @cperessini | FE @iamphill

• #26732 (closed) Combine Deploy Keys and Push Rules and Mirror Repository and Protect Branches settings pages | PM @victorwu | UX @tauriedavis | FE @jivanvl

• #26733 (closed) Change cog / gear navigation to tabbed navigation for settings | PM @victorwu | UX @tauriedavis | @annabeldunstone

• Minimal Pipeline API to deprecate build API (specifically build triggers)

• customer+ Impersonation tokens
• customer Repository mirroring: Support for configurable sync time /24206)

• ~"q1-vision" #26905 (closed) Prometheus Environment monitoring for Kubernetes based auto-deploys PM @joshlambert | UX @tauriedavis | FE @jivanvl
• #25487 (closed) Improve UI of Mattermost and Slack Command services | FE @lbennett | UX @pedroms
• #24917 (closed) Improve styles of Mattermost and Slack messages | BE @zj | UX @pedroms
• #23964 (closed) Link GitLab group to Mattermost team | BE @zj | FE @filipa | UX @pedroms

Stretch issues

• #26360 (closed): Make manual jobs obey the laws of physics | FE

• customer+ Preventing users from disconnecting from CAS
• customer+ Configuring OmniAuth does not prevent standard GitLab Auth
• external services Stretch Microsoft Teams Integration

• omnibus-gitlab#1862 (closed) Export additional metrics for GitLab CE and other Omnibus GitLab services | PM @joshlambert

Other issues not in scope

These other issues were not scoped specifically into 8.17, but should be considered if there is any open capacity during the milestone.

EE specific

• EE Starter Repository mirroring: Support for SSH keys https://gitlab.com/gitlab-org/gitlab-ee/issues/98 PM @regisF
• EE Starter First step of Audit logs improvements https://gitlab.com/gitlab-org/gitlab-ee/issues/579 PM @regisF
• EE Starter Allow LDAP users to be synced on login again https://gitlab.com/gitlab-org/gitlab-ee/issues/906

Customer

Victor

• Add breadcrumbs/nav to Wiki feature proposal | PM @victorwu | FE @alfredo1 | UX @hazelyang

Mark

• Jenkins does not use username and password for auth bug | PM @markpundsack
• Inconsistent documentation for private registry support ~CI | PM @markpundsack

Discussion (candidate issues, in priority order)

• #26396 (closed) Real-time | PM @mydigitalself
• ~"q1-vision" #26432 (moved) Jump to Mattermost channel from GitLab issue | PM @victorwu FE @nmrony UX @pedroms
• direction https://gitlab.com/gitlab-org/gitlab-ee/issues/91 Burndown chart | PM @victorwu | FE @selfup UX @pedroms
• #21518 (closed) Use reCAPTCHA when user attempts to create an issue detected as spam | PM @victorwu | FE @samrose3 | UX @hazelyang
• #26652 (closed) View and edit tokens in issues search bar | PM @victorwu | UX @cperessini | FE @ClemMakesApps
• direction #2641 (closed) View and add comments on previous commits in image file view | PM @victorwu | FE @fatihacet | UX @dimitrieh
• direction https://gitlab.com/gitlab-org/gitlab-ee/issues/1526 Suggest approvers in merge request - UX improvements | PM @victorwu | FE @MadLittleMods | UX @hazelyang
• https://gitlab.com/gitlab-org/gitlab-ee/issues/1126 Approve a merge request beyond the number of required approvals | PM @victorwu | FE @nmrony | UX @hazelyang
• https://gitlab.com/gitlab-org/gitlab-ee/issues/1315 View approval counts in the merge requests list view| PM @victorwu | FE @kushalpandya | UX @hazelyang
• #26670 (closed) Auto space and dropdown in issues search bar | PM @victorwu | UX @cperessini | FE @ClemMakesApps

UX

(candidates, issues where UX work is completed, and fixing would help improve UX flows and overall consistency)

• Uniquely and uniformly style status badges (https://gitlab.com/gitlab-org/gitlab-ce/issues/25564)
• Consider styling links and GFM references in user profile events and todos (https://gitlab.com/gitlab-org/gitlab-ce/issues/24370)
• Branch name when using "new branch" button in issues (https://gitlab.com/gitlab-org/gitlab-ce/issues/21143)
• Add a more helpful issues empty state (https://gitlab.com/gitlab-org/gitlab-ce/issues/25043) | UX @pedroms
• Standardize dropdown menu styling (https://gitlab.com/gitlab-org/gitlab-ce/issues/26202)
• Give existing issue results when typing in your issue title (https://gitlab.com/gitlab-org/gitlab-ce/issues/22071)
• Make search boxes consistent throughout GitLab (https://gitlab.com/gitlab-org/gitlab-ce/issues/26303)
• No indication Emoji cant be added on own Awardable (https://gitlab.com/gitlab-org/gitlab-ce/issues/21881)
• Code Blob search result keyword highlighting! (https://gitlab.com/gitlab-org/gitlab-ce/issues/24475)
• Summarize search hits for same file (https://gitlab.com/gitlab-org/gitlab-ce/issues/23750)
• Simplify milestone summary (https://gitlab.com/gitlab-org/gitlab-ce/issues/23674) | UX @pedroms

Frontend

• Adding in Webpack (#14634 (closed) - !7288 (merged)) @mikegreiling
• Remove Turbolinks https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8570 @brycepj
• Make large commits usable (#14775 (moved)) - @alfredo1
• Remove jQuery UI (#18437 (closed)) - @lbennett @iamphill
• Load Participants via Ajax (#23206 (moved)) @lbennett
• Award emoji rendering once per page instead of on every note (#23226 (moved)) - @fatihacet
• Improve performance Emoji reaction popup loading (lazyload?) (#22474 (closed)) - @MadLittleMods

@JobV https://gitlab.com/gitlab-org/gitlab-ce/issues/25986 seems to be about replicating the demo, but bringing I2P to everyone needs to be more than that.

@markpundsack haha, absolutely. The issue is a start for other issues to come. The title aspirational.

Our goal for Q1 should be to make I2P usable for everyone (given constraints, such as: you must use Kubernetes / Google Container Engine) and more types of projects than it is now (multi-container projects such as App + DB).

I updated the description to match our goals.

New option to prevent too big Git pushes: https://gitlab.com/gitlab-org/gitlab-ce/issues/26044

mentioned in issue #26642 (closed)

added meta label

mentioned in issue #25913 (moved)

Added Prometheus topics. #26798 (closed) is early and needs more design work, but wanted to get it on the list as I imagine we will want to try to deliver a portion of it (or begin work) in Feb.

Microsoft Teams integration https://gitlab.com/gitlab-org/gitlab-ce/issues/24206 appears like it may just be a fairly transform on the webhook format specific for Teams. Would be a simple quick win and will work on getting the MS PR machine behind us on the announcement of the feature.

Audit user role for EE: https://gitlab.com/gitlab-org/gitlab-ee/issues/1439

@victorwu The manage label page is dog slow due to it displaying MRs and issues per label, i'm sure this also puts a lot of weight and blocks server threads while it's happening. Is there any plan to do something about this soon? I'm happy to manage if you're overwhelmed for this release as I'm still getting up to speed and don't have a huge list of features quite yet.

@mydigitalself I also ran into that this past week (since there is no search/filtering on that page, it is especially painful) but that may just be a GitLab.com performance issue. Self-hosted/GitHost servers may not see that issue, and could complain if we take away those metrics. Something to think about.

The issue for that is https://gitlab.com/gitlab-org/gitlab-ce/issues/25413.

We need to do https://gitlab.com/gitlab-org/gitlab-ee/issues/99, which has already slipped far too many times

We're going to need to ship/finish the Pipelines API so we can kill the deprecated Builds API. /cc @ayufan

@ayufan We need to push I2P forward (https://gitlab.com/gitlab-org/gitlab-ce/issues/25986), starting with getting the demo on GKE. I'd like to push forward on something on CI speed (https://gitlab.com/gitlab-org/gitlab-ce/issues/21624) and something on Deployboards (https://gitlab.com/gitlab-org/gitlab-ce/issues/21413). Smart deploys may be a prerequisite for deploy boards?

We will have a meeting on Friday (Jan 20) to establish scope for 8.17.

@DouweM @smcgivern @jschatz1 will carve out top priorities and indicate them here (issue description or link them) before the meeting so all can review. These top priorities will largely consist of API breaking changes to get ready for 9.0. They will not be activated until the 9.0 release. But they are important and should be worked on during 8.17's window so that we get ready accordingly.

With any remaining engineering capacity for 8.17, we will scope out high priority features to work on. Folks should list them as candidates here (in the issue description preferably), with I2P features being a GitLab-wide priority.

In summary, prioritization for 8.17 is:

1. Improve GitLab platform to prepare for 9.0.

2. Make a big dent in I2P vision.

@joshlambert @bjk-gitlab What can we get done for user app monitoring in 8.17? I'd like to see some basic monitoring of user apps and graphs for production and staging environments, even if we have to cut a lot of scope to get that in (such as asking the user to install Prometheus themselves and provide the URL, only supporting node-exporter metrics rather than response metrics, etc.). This is huge for the Feedback step of our Idea to Production vision. We have some initial designs from @tauriedavis in https://gitlab.com/gitlab-org/gitlab-ce/issues/23841, although we might need some additional UI help to figure it out end-to-end. We'll definitely need some front-end help too. /cc @jschatz1

I think what I'd like to see done in the first iteration is to have resource stats (CPU/memory) from Kubernetes available. I'm having a chat with @joshlambert today about our ideas/priorities.

@markpundsack @bjk-gitlab I have updated #26905 (closed), to reflect what we have discussed today.

First step to bring usage ping to CE, let's do this in 8.17:

• Move usage ping JSON payload to a new page (https://gitlab.com/gitlab-org/gitlab-ee/issues/1498)

It's worth mentioning that the packaging team has a full time resource dedicated to make a HA product: https://gitlab.com/gitlab-org/gitlab-ee/issues/77 that will span multiple releases (similar to DR).

Once ready, this will add value to our EE offering.

I'm working on list of Kubernetes-related things that we would like to include in GitLab Runner as part of making Kubernetes integration to be marked as stable for 9.0. We will have a @tmaczukin working on that and partially @zj helping out with Go and Kubernetes.

It would be good to think about implementing this: https://gitlab.com/gitlab-org/gitlab-ce/issues/26896 (overview of pipeline status). We have a lot of done already as part of e-mail templates, maybe we could re-use some of that.

We have a number of ~Frontend related issues that are connected with making views real-time. It will use the significant amount of time to ship it. So we could split the effort of backend to follow two paths: help ~Frontend and work on improving GitLab Runner and performance of builds: https://gitlab.com/gitlab-org/gitlab-ce/issues/21624. Some of the capacity will have to be allocated to work on improving the API performance, something that @bkc started working on.

@filipa @grzesiek Could you post a list of ~Frontend related things that are left-overs and that we should work for 8.17?

@ayufan Yes I have a few realtime things waiting for backend changes as well.

Issue Title (eventually body) and Pipelines#index

@ayufan @grzesiek

Real time related issues:

• https://gitlab.com/gitlab-org/gitlab-ce/issues/25226 Update individual pipeline view in real-time or at least refresh (rewrite in Vue) ~Frontend backend
• https://gitlab.com/gitlab-org/gitlab-ce/issues/25177 Rewrite builds tab in pipelines show view with vue.js to prepare for real time updates ~Frontend backend
• https://gitlab.com/gitlab-org/gitlab-ce/issues/25051 View issue title real-time updates ~Frontend backend
• https://gitlab.com/gitlab-org/gitlab-ce/issues/5983 Update pipelines in real-time or at least refresh ~Frontend backend

Frontend Leftovers from 8.16 and 8.15

• https://gitlab.com/gitlab-org/gitlab-ce/issues/25910 - convert manual action icons to svg to propperly position them ~Frontend backend
• https://gitlab.com/gitlab-org/gitlab-ce/issues/25786 - Tech debt: Add feature specs for the builds dropdown in the mini pipeline graph ~Frontend
• https://gitlab.com/gitlab-org/gitlab-ce/issues/25499 - Paginate environment list ~Frontend backend

We also have some Frontend smaller bugs to fix

@ayufan : I thought we were blocked on the real-time stuff until https://gitlab.com/gitlab-org/gitlab-ce/issues/26396 and https://gitlab.com/gitlab-org/gitlab-ce/issues/26926 are solved/completed?

mentioned in issue #2641 (closed)

Just a small bump to hopefully get the burndown chart higher on the list

The issue actually already looks quite well described to me: https://gitlab.com/gitlab-org/gitlab-ee/issues/91

mentioned in issue #26687 (closed)

closed via commit d2db3649

reopened

mentioned in issue #27154 (closed)

@selfup : Yes, I updated the description. My mistake. I didn't update that and it was a vestige of copy and paste.

@victorwu No worries! thanks :)

mentioned in issue #21722 (closed)

Added under Deliverable smaller:

• #26384 (closed) Improve Omnibus-Mattermost Command installation flow | FE @lbennett | UX @pedroms

Added under Deliverable smaller:

• #25487 (closed) Improve UI of Mattermost and Slack Command services | FE @lbennett | UX @pedroms
• #24917 (closed) Improve styles of Mattermost and Slack messages | BE @zj | UX @pedroms
• #23964 (closed) When creating a new GitLab group/project, automate the setup of the Mattermost team/channel. | BE @zj | FE @lbennett | UX @pedroms

mentioned in issue #18713 (closed)

mentioned in issue #14416 (closed)

mentioned in issue #14775 (moved)

Removed gitlab-ee#895 because it has been moved to %9.0:

• direction https://gitlab.com/gitlab-org/gitlab-ee/issues/895 Auto-rebase when merging merge request | PM @victorwu | UX @pedroms | FE @jivanvl

Removed these issues because they've been moved to %9.0:

• gitlab-ee#918 Add global configuration option to restrict group owners to admins Platform | PM ? | FE @kushalpandya | UX @pedroms
• #26384 (closed) Improve Omnibus-Mattermost Command installation flow | FE @lbennett | UX @pedroms

closed