Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

operate_8_2_6_support_notice #2245

Merged
merged 2 commits into from
Jun 14, 2023
Merged

operate_8_2_6_support_notice #2245

merged 2 commits into from
Jun 14, 2023

Conversation

johanwelgemoed
Copy link
Contributor

Description

Added text to the announcements section to warn users to not directly udpate from 8.1.x to 8.2.6.

When should this change go live?

asap

  • This change is not yet live and should not be merged until {ADD_DATE} (apply hold label or convert to draft PR)?
  • There is no urgency with this change.
  • This change or page is part of a marketing blog, conference talk, or something else on a schedule.
  • This functionality is already available but undocumented.
  • This is a bug fix or security concern.

PR Checklist

  • I have added changes to the relevant /versioned_docs directory, or they are not for an already released version.
  • I have added changes to the main /docs directory (aka /next/), or they are not for future versions.
  • My changes require an Engineering review, and I've assigned an engineering manager or tech lead as a reviewer, or my changes do not require an Engineering review.
  • My changes require a technical writer review, and I've assigned @christinaausley as a reviewer, or my changes do not require a technical writer review.

@johanwelgemoed johanwelgemoed requested a review from megglos June 14, 2023 13:30
megglos
megglos previously approved these changes Jun 14, 2023
Copy link
Contributor

@megglos megglos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking this! As the events overlapped, let's already make clear 8.2.7 is available?

docs/reference/announcements.md Outdated Show resolved Hide resolved
versioned_docs/version-8.2/reference/announcements.md Outdated Show resolved Hide resolved
@megglos
Copy link
Contributor

megglos commented Jun 14, 2023

let's also assign @akeller for review
@akeller can you please make sure we git this published asap? thx! 🙇

@megglos megglos requested a review from akeller June 14, 2023 13:35
@akeller
Copy link
Member

akeller commented Jun 14, 2023

@megglos I'm going to accept your suggestions and give this a 👍 so we can merge this in quickly.

Co-authored-by: Sebastian Bathke <sebastian.bathke@camunda.com>
Copy link
Member

@akeller akeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 will revisit if we need to clean up language/style, but let's merge this and get it released for awareness.

@akeller akeller enabled auto-merge (squash) June 14, 2023 13:39
@akeller akeller merged commit 73c2dbe into main Jun 14, 2023
@akeller akeller deleted the operate_8_2_6_support_notice branch June 14, 2023 13:58
mesellings added a commit that referenced this pull request Dec 5, 2024
mesellings added a commit that referenced this pull request Dec 10, 2024
* Add initial and potential alpha 2 release note epics

* Add Export activity endpoints

* Remove 2126

* TW edits

* Add document handling 2409

* Add 2073 unified deployment

* Badges and edits

* Remove license expiration 2529 placeholder

* Add #2244 and #2245

* Remove 1314 Replay Scenarios

* Add process instance migration

* Remove release blog

* Add Connectors entries

* Add testing support for Connectors

* Webhook connector details

* Restructure connectors section

* Add Gemini link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants