Release manual trigger, new steps, and mini survey

[Sakshi-Dhakad]

1. Pipeline name can be changed when a pipeline is in inactive state. Hope that clarifies.
2. Ok
3. Nothing super noticeable, small things like better performance, better UI -- similar to what happens when you upgrade to a new version of apple.
4. Ok

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Dana Breseman @.> Sent: Tuesday, July 2, 2024 4:07:41 PM To: mendix/docs @.> Cc: Sakshi Dhakad @.>; Mention @.> Subject: Re: [mendix/docs] Release manual trigger, new steps, and mini survey (PR #7974)

@dbreseman commented on this pull request.

---

In content/en/docs/releasenotes/deployment/mendix-cloud.mdhttps://github.com/mendix/docs/pull/7974#discussion_r1662605843:

@@ -16,6 +16,16 @@ For information on the current status of deployment to Mendix Cloud and any plan

2024

+### July 4, 2024 + +#### Pipelines Improvements + +* We added support for two new pipeline steps:

• • Use the Start Environment step to start a selected environment.
• • Use the Promote Package step to move a deployment package from a specified source environment to a specified target environment. + It is now possible to trigger pipelines manually. To use this new trigger in your pipeline, select Manual as the Trigger in the Start Pipeline step of your pipeline design. + We will be launching a mini survey for Pipelines soon, asking you some questions about what you like and dislike.

@Sakshi-Dhakadhttps://github.com/Sakshi-Dhakad my feedback is below:

1. I think there's a typo here—could you clarify? When can pipeline names be changed?
2. The Docs already have a warning alert with this text: "If you delete a pipeline design in the Designs tab, any run history associated with that pipeline design is deleted from the Runs tab." If I understand correctly, this behavior isn't changing, but there's now a new pop-up that makes this harder to miss in the UI. I generally wouldn't include this new pop-up in the release notes because it just reinforces pre-existing functionality in a way that should be self-explanatory, but I can if you think it's important to emphasize to users.
3. Will the switch to the LTS version be apparent to users when they use Pipelines? Otherwise, it's okay to omit this.
4. Thanks for flagging this. I'll make sure it's included.

— Reply to this email directly, view it on GitHubhttps://github.com/mendix/docs/pull/7974#discussion_r1662605843, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2WLGYVCYDN2XVQIL2PSNTDZKKX23AVCNFSM6AAAAABKG5ULB6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNJTHE2TSMRZGQ. You are receiving this because you were mentioned.Message ID: @.***>

[dbreseman]

@Sakshi-Dhakad Updated now to integrate your feedback: https://github.com/mendix/docs/pull/7974/files. Please let me know if you see anything that needs further adjustments.