Editor 15.2 Planning issue
Release planning for the Editor Group
Overview
Milestone 15.2 Board
Key Themes
| Category | Theme |
|---|---|
 |
Deserialization of Markdown on the FE, autocomplete/suggestion spike |
 |
OverlayFS integration |
 |
API Caching |
 |
Monaco upgrade, Vue migration |
Team Capacity
- FE Weight: 24
- BE Weight: 8
- Pages Weight: 17
- Total Weight Capacity: 49
PTO (June 20th - July 18th)
| Team Member | PTO(Days) |
|---|---|
| @dmishunov | |
| @cwoolley-gitlab | 9 (2 FnF, 1 PH, 6 PTO |
| @pslaughter | |
| @ealcantara | 1 (FnF) |
| @fjsanpedro | |
| @vtak | 2 (FnF) |
| @kassio | 3 (2 FnF, 1 PTO) |
| @viktomas | 8 (2x PH, 2x FnF, 4x PTO) |
UX (Total weight capacity: 0)
| Issue | Assignee | Weight | Type |
|---|---|---|---|
| Solution validation: VS Code-based Web IDE | Assignee | Weight | Type |
| Create user journeys for using Source Editor | Assignee | Weight | Type |
Carry-over:
- https://gitlab.com/gitlab-org/gitlab/-/issues/349806+
- Allow activation of URI includes for AsciiDoc i... (gitlab-org/gitlab#348687 - closed)
Frontend (Total weight capacity: 27)
Backend (Total weight capacity: 9)
Pages (Total weight capacity: 18)
| Issue | Assignee | Weight | Type |
|---|---|---|---|
| Pages Internal API Caching (gitlab-org&7920 - closed) | Kassio | 8 | Deliverable |
| Workspaces | Category Strategy (gitlab-org&7419) | Vishal | 8 | Deliverable |
Checklist
EM @oregand
- Get Team Capacity
- Assign ~Direction Items for Milestone
- Define Key Themes
PD @mle
- Update UX issues
Stable counterparts
FYI @aqualls @a_mcdonald / @jzhang_gl
Activity
changed milestone to %15.2
added Planning Issue label
PTO (June 20th - July 18th)
@dmishunov @cwoolley-gitlab @pslaughter @ealcantara @himkp @vtak @kassio
Can y'all add any possible PTO for %15.2 and I can begin to flesh out the milsetone
Please also feel free to comment in a thread if there is work you would really like to tackle during %15.1
assigned to @oregand
assigned to @ericschurter
-
@oregand @ericschurter: I’d like to move gitlab-org/gitlab#355784 (closed) to %15.3 and continue my focus on supporting new content types on the client-side parser. I would focus on GitLab Flavored Markdown extensions on %15.2. This is a list of issues that I pointed out as good candidates for %15.2:
- gitlab-org/gitlab#360946 (closed) (already included on this planning issue)
- gitlab-org/gitlab#359008 (closed) (this one is important because it requires implementing an extension for the Markdown parser)
- gitlab-org/gitlab#359012 (closed) (The last three are low hanging fruits that we can implement easily)
- gitlab-org/gitlab#359020 (closed)
- gitlab-org/gitlab#359022 (closed)
-
I am okay with this from a planning perspective, I think there is a lot of value in this items
@oregand @ealcantara Works great for me! I'll adjust milestones accordingly.
-
@oregand @ericschurter: I need to update the plan again
I want to ensure that we fully support Commonmark/GFM before moving to the GitLab extensions. I created an issue that documents this requirement, and I’d like to resolve it on this milestone.
After that change, we end up with this plan for %15.2
- gitlab-org/gitlab#360946 (closed) (already included on this planning issue)
- gitlab-org/gitlab#365292 (closed)
- gitlab-org/gitlab#359012 (closed)
- gitlab-org/gitlab#359022 (closed)
- gitlab-org/gitlab#359020 (closed) (Stretch)
Sorry for moving the target so much
-
No worries, there's still plenty of time to adjust our plan @ealcantara
-
Thank you for updating the list for us, I have since updated the planning issue. Just be aware that you are currently at a weight of 17 for the issues and we generally budget 10 per milestone, so if you need to push out some items please don't hesitate
Looks like @ealcantara did figure out how to clone himself after all.
-
I am willing to be we are one of the most productive teams by a long shot (Andres team too obviously
Edited by David O'Regan -
Looks like ealcantara did figure out how to clone himself after all.
Maybe’s it’s been Enrique’s clone writing all along
. Just be aware that you are currently at a weight of 17 for the issues and we generally budget 10 per milestone, so if you need to push out some items please don't hesitate
Thanks for the reminder, David! I’ll make sure to move the last three issues to the next milestone as soon as I see my capacity significantly reduced by the first two that are the complex ones.
An update: Issue gitlab-org/gitlab#350364 (closed) will make it in %15.1 so I'll have some additional capacity for %15.2. I'd like to do some research around autocomplete suggestions in content editor. It also includes support for quick actions and emoji.
-
That sounds good, I will update the plan
-
A spike on autocomplete and suggestions would be amazing, thanks @himkp!
mentioned in issue gitlab-com/Product#4321 (closed)
@oregand Updated my issues. Regarding some of the issues that require coding, I will take up your offer for pairing on some of my carry over issues that have increased in complexity.
-
Async update
As per gitlab-org/gitlab#359020 (comment 1007466843), updaing the FE deliverables.
mentioned in issue gitlab-org/technical-writing#627
mentioned in issue gitlab-com/www-gitlab-com#13631 (closed)
