GitLab Release Stage, 31 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Release 3-year vision - UX sync

Description

Rayana and Dimitrie sync up on 3-year Release Vision Mocks https://gitlab.com/groups/gitlab-org/-/epics/3825

A

Before you do that.

B

Okay cool so today we're here to um review some of the prototypes that we have for the release of three-year vision and also look at the flows, a and b that are proposed by um product managers and see that how that could align with the prototypes and the flows that we already have.

B

So I'm just going to quickly share my screen, so you can see the figma files that we have all right. You can see that. um So what else uh trying to to say immediately is that from the prototypes that we have from last friday, so we have this and some for future flags.

B

I was thinking that, um since the flow b that we have here covers mostly um room books, um deploy phrases and the release page, and most of it makes sense with what I already have here. I just started prototyping it um following the instructions for at least the proposal in that issue.

B

So first the user starts with like an email, saying: hey, you have a new deployment to review, so you can approve or view details and then the proposal I'm going to show you on the screen here from jackie- has a bunch of things that are very detailed. For example, um once you click approve or review, you go to a group release and then you can see each deployment for the projects in a specific group.

B

Once you click to review the review app, you have the option to review that deployment and approve it if it's behind a feature flag, which is what I have in this prototype here, the user gets like notified and once you approve you go to the merge request view and it says aversion and will be ready to be merged and it mentions a lot of things uh related to future flags, but I don't think there's any ui for feature flags on this, the flow b.

B

So that's why I suggested I, since I already have most mockups for group releases and requirements, etc that I'll just continue prototyping flow b and we can review it together. Maybe asynchronously does that.

A

Make sense so I'm what I'm, what I'm yet to understand this? uh The second like the brown yeah, like these steps, like it states something like you're looking at a deployment, but it it shows different like it's in an incomplete mock. I I'd say right.

B

Everything I just started this morning, so this is this is like it's like a review app, but then you just have to approve this review app. So if you click approve it's going to trigger an action which will be, you know, triggering the pipeline to merge this thing into master and then we go in the merger merchandise view you have a different notification: their users use an email etc, um which is all detailed here.

B

A

So why why are we showing the um I'm just trying to get on the same on the same page as you so the? So let me let me let me look at the flow here usually get employment right.

B

A

Clicks the link to view the deployment.

B

A

Takes them to a group release with issue progress, views and now you're doing it away.

B

That's a different view: that's uh I'm doing a different flow, I'm doing in the same issue, but I'm doing uh step five uh and I'm doing I'm doing step five with the egypt flags and without future flights.

B

The step three would be going here.

A

B

A

A

So you say like ritu's.

A

Number five: you to click second review app and is prompted that the future flag features behind the feature flag and will not be available to users until feature flag is removed. They can acknowledge the statement review the app would, but where this is the thing I'm trying.

B

You're breaking.

A

B

Looking up here.

A

Lab and shows all these projects and.

B

You're breaking up, I didn't hear the last part.

A

So what I'm trying to understand is what this view is. Why does it say, discover projects group, snippets, explore gitlab and shows like prague.

B

This is every viewer.

A

This is relevant to the mock-up.

B

This is a deployment of uh gitlab, so someone, let's say that you have uh the white freezes and labels right and someone actually tries to deploy something to production. When you plan during christmas, that's not supposed to so you as a release manager. um You receive a notification on your email. Saying: hey, jane, though try to merge something uh to master on gitlab, but the libraries are enabled do you want to approve this merge or this deployment or click here to view the details.

A

uh Wait a second so where I was slightly confused, is that we are looking at git lab itself as both the management application, as well as the deployed application.

A

So what? What do you think about changing that? Because I think perhaps this is so meta that it might be, at least it confuses me so, instead of like the project being itself, it being a random app like being in hello world or something super simple, that it is clear that this is the deployment of a certain app that has been built by a developer or something somewhere.

A

B

A

B

You can even use the gitlab.com or whatever just uh the website. I guess what you mean, because this would be, for example, in this view, it's more or less like your jdk instance right. You see that specific branch.

A

B

Specific thing that you're.

A

B

To merge uh into master to deploy, so that's why I see- um and this is just a quick and dirty prototype- that's why you see some like um I'm, not an alert, but whatever this uh this uh ui here saying hey what you're looking at is something that is still pending. Do you want to approve, or you want to see details? That's why they're that's what they asked in the in the from me.

B

So if you approve ask for their description here, um you can approve their families and that's why it's always linked to the releases view.

B

This is just a prototype that I made last friday, but you're going to see all the review apps for different 13.4, uh pajamas and runner, and then you can approve each one of them until gitlab 13.4 is.

A

B

That's what uh flow b uh describes this one here.

A

And just a thought towards approving uh the review app. Do you think it's essential to approve within the review app, as that is an environment where we have we inject code into the uh like the app of the of the customer.

B

Can you repeat that you're breaking up a little bit.

A

Sure so what I said is, do you think it's essential that the approving process, the approval process within the review app itself? Do you think that is essential, because the review app environment is not within get it's an external.

A

By, for example, uh adding in gitlab ui such as this approval like bar of alert or call out, however, you want to call it. uh We will inject the code into the application of the customer.

B

um I'm less worried about that now, so this is just that this is a vision thing. Doesn't my head doesn't really matter if we can support that right? Now? Yes or no, um we should have this this button to approve in the in other views as well as per the description here. You have this in the group releases view and it will also show somewhere, I think in the merger class yeah merge, request and review it's approved.

B

So I got your point, but I'm like okay.

B

Okay, yeah, I'm just wondering yeah.

A

The colors are open, so um so in in terms of the flower, I'm looking at you know the flow b um flow for release. So you you have step one. You have step five kind of. uh Are you intending to create the in-between steps as well.

B

Yeah, I want to finish it today: I'm going to go over everything because most of these prototypes, I I have from different issues, I'm just going to try and throw them here.

A

So did you have the attention that we each create a flow, then create like feedback on each other, so I will create flow, a yeah. That's right, all right.

B

Let's and because I haven't read this one yeah, this one is more like rollback.

B

An external integration then, for example, it goes to the environment uh dashboard. We don't have that.

B

I have some prototypes that look like environment dashboards for the new new version, so you can work on that async to make some updates yeah.

B

But I think it's fine if we go um async and continue with what we had, because indeed the the first part of the ideation, it would be too much work and after I found this uh these issues where we suggest the flow, it's really like more granular, it's really about going from a to b, um like what we try to kind of like what the future views that we try to put together here.

B

So I think it's a good exercise for us to to connect them, even though they are very solution. Oriented like what you say before.

A

B

A

Sorry um this sounds good. Let's, let's do that and ask each other for an async review and iterate on that and try to finish at least the first duration, yeah.

B

A

B

Yeah sounds good and then I think, let's use the figma comments here, to need feedback so that we can uh tackle the tasks and reply to each other. That's good.

B

um With the prototypes, but I don't think I'll- need anything different from the views that I already have here but I'll, let you know.

A

Sounds good, let's uh I'll give you a slight message when I have something to show cool.

A

Cool see you uh see you later.

A