Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Revise our handling of Camunda Modeler patch releases in user communication and rollout

See original GitHub issue

Is your feature request related to a problem? Please describe.

We got updating the release info as part of a patch release in our patch release checklist. It does not really make sense to do so, though: Rather than understanding that one particular bug has been fixed in a patch users remain interested in what has been shipped with the last minor, especially when they simply unwittingly download the “v4.11” release promoted on camunda.com and end up with a patch release (v4.11.1 for example).

Then again, when looking into the what’s new communication without an updated release info it looks like all these features got added with the patch release:

Then again, the update server / staged rollout does not distinguish between patch releases and a stable release, it may very well promote v4.11.0 to a user while v4.11.1 is already out, fixed and ready to install.

Describe the solution you’d like

What’s new communication for patch releases is revised ➡️ we talk about minor releases only
Update server is patch release aware ➡️ does not offer unpatched versions if a patch is available
Release checklist is updated to reflect what’s new communication and update server related changes for patch releases ➡️ we do not update the release info during a patch release.

Describe alternatives you’ve considered

Keep things as awkward as they are, given that only few patch releases are anticipated. We’d love to not have them, if we could.

Additional context

Popped up during the https://github.com/camunda/camunda-modeler/issues/2499 release.

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

andreasgeiercommented, Nov 11, 2021

My suggestion was to not mention the patch at all, i.e. continue to talk about the minor only.

I would be fine with this as well because we would not lose the minor information in a patch release overlay.

Your proposal would be an alternative to that, offering details for individual patch releases, if I understand correctly?

Yes, similar to this examples:

0reactions

nikkucommented, Nov 11, 2021

My suggestion was to not mention the patch at all, i.e. continue to talk about the minor only. Patches do rarely ship with noteworthy items (major new capabilities). If we settle down on that we could go so far to not enable the what’s new dot in case nothing changed with a patch.

Your proposal would be an alternative to that, offering details for individual patch releases, if I understand correctly?

Top Results From Across the Web

Release Camunda Modeler v4.11.1 #2499 - GitHub

I deployed successfully a diagram with a User Task and Camunda Forms with default value latest . I was able to shut down...

Camunda Desktop Modeler 5.6 released

We are happy to announce the release of Camunda Desktop Modeler 5.6, which ships with broader BPMN support and some key UI improvements....

Release Policy | Camunda

Camunda provides a standard support period of 18 months for their Enterprise customers. Therefore, the last three released minor versions are supported with ......

Camunda Platform 8.0 Released - What's New

Modeler ; Connectors – Developers Preview; Workflow Engine; Decision Engine; Operate; Tasklist; Optimize. This blog post will provide an overview ...

Camunda Platform 8 for Camunda Platform 7 Users - Camunda

Since then, Camunda has released 17 minor versions and more than 100 patch releases. Now is the time to increment the big number...