Christina Lohr (13b01d0a) at 17 Mar 17:04

What does this MR do and why?

Adding the What's New MR as per the guidelines in the 18.10 release post MR.

References

gitlab-com/www-gitlab-com!142715

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Christina Lohr (3064b0c1) at 17 Mar 16:40

The Slack reference to @product-leaders needs to be updated, as it has multiple matches. Not sure which one was the intended one, so I chose @product-leadership-team.

💡 Something we can improve

Content assembly cannot be run before 4 pm UTC. For folks in Europe, this means 5 pm, and then to wait around until the pipeline has run before the next steps can be taken up. For me, it was 6:30 pm before I could start with the many, many steps required to verify that everything went well. This took until 8:30 pm and I couldn't even finish all tasks for that day. I'd suggest to either make this process more flexible in order not to push the effort into the late evening for people in Europe, or to select RPMs in a time zone that can accommodate this within normal working hours.

💡 Something we can improve

I find the overall release post guide difficult to navigate, it was much easier when it was clearly organized into tasks arranged by due date. Now it requires unfolding several sections to figure out what really needs to be delivered on each day. There is also duplication amomgst the sections, for instance, there are two different references to check dead links, one of which is not supported by Chrome anymore. This should be removed to optimize the flow. I'd also suggest rearranging the sections by day as was the case before for better clarity what deliverables are expected each day.

💡 Something we can improve

@mnohr If you need to remove the content block, could you follow the steps outlined here before the end of today, so that we can run the last checks tomorrow?

Christina Lohr (617d4011) at 17 Mar 15:35

@uchandran I think that's a hard limit, so we unfortunately don't have much room here. I'll apply your suggestion.

Christina Lohr (4164a02b) at 17 Mar 15:34

@leetickett-gitlab Just wanted to check, is IssueSummary supposed to be written together or is that a typo?

    Harshith's contributions were first recognized by [Lee Tickett](https://gitlab.com/leetickett-gitlab), Fullstack Engineer in DevRel Engineering at GitLab, who nominated him. His work has strengthened how we support contributors behind the scenes through improvements to our automation and contributor-facing experiences. For example, he expanded our triage automation by [updating the Issue Summary processor in triage-ops to work with multiple projects](https://gitlab.com/gitlab-org/quality/triage-ops/-/merge_requests/3589), including [contributors.gitlab.com](https://contributors.gitlab.com), making it easier for us to keep more community projects consistently summarized and visible. He also helped recognize community-created content through the [new “Add content” button and flow](https://gitlab.com/gitlab-org/developer-relations/contributor-success/contributors-gitlab-com/-/merge_requests/1250), which lets contributors log blog posts, videos, and other content directly from their profile and get rewarded.

@uchandran Should credits be de-capitalized here as well?

title: "GitLab 18.10 released with Duo SAST and free tier credits" # short title (no longer than 62 characters) - required

@brothwell1 Could you replace this with a public facing issue or open the issue to the public?

@smaglangit I think it would be nice to use the same modal both for settings and quick actions, but I can see that this means that we would need to redesign the settings flow a bit and move the destination selection into the modal. Perhaps it could be as simple as just moving the selection into the modal and renaming the action button to "transfer", because it already works in two steps. But would love to confirm with @jason_istakinganap.