Skip to content

Conversation

@EuroLew
Copy link
Contributor

@EuroLew EuroLew commented Oct 31, 2025

Description

Reduce the bulk delay from 5s to 1s. Implementation PR here camunda/camunda#40299

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
  • This is already available but undocumented and should be released within a week. (add available & undocumented label)
  • This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
  • This is part of a scheduled alpha or minor. (add alpha or minor label)
  • There is no urgency with this change (add low prio label)
  • My changes are for an upcoming minor release and are in the /docs directory (version 8.8).
  • My changes are for an already released minor and are in a /versioned_docs directory.
  • I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:

@github-actions
Copy link
Contributor

👋 🤖 🤔 Hello, @EuroLew! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

  • docs/self-managed/components/orchestration-cluster/zeebe/exporters/camunda-exporter.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

@EuroLew EuroLew changed the title Reduced defauolt bulk delay Reduced default bulk delay Oct 31, 2025
@mesellings
Copy link
Collaborator

Hi @EuroLew 👋 - what version is this for please? I see you have specified a release, but haven't added the relevant release label - e.g. 8.9-alpha1 etc? Qe use the labels to group and triage docs work so it really helps to have the info upfront - thank you! 🙇

@EuroLew
Copy link
Contributor Author

EuroLew commented Oct 31, 2025

Hi @EuroLew 👋 - what version is this for please? I see you have specified a release, but haven't added the relevant release label - e.g. 8.9-alpha1 etc? Qe use the labels to group and triage docs work so it really helps to have the info upfront - thank you! 🙇

its getting merged into main so my understanding is my code changes would make it into 8.8.2 what label would I use then? I'm a bit confused here

@mesellings
Copy link
Collaborator

Hi @EuroLew 👋 - what version is this for please? I see you have specified a release, but haven't added the relevant release label - e.g. 8.9-alpha1 etc? Qe use the labels to group and triage docs work so it really helps to have the info upfront - thank you! 🙇

its getting merged into main so my understanding is my code changes would make it into 8.8.2 what label would I use then? I'm a bit confused here

Thanks @EuroLew the extra context is enough - sounds like this is for an 8.8.2 patch - looking at the files you have changed, those are just for 8.9, and would need to also be added to the versioned 8.8 folder if this is for 8.8 as well. I can help with that if you like?

@mesellings mesellings added the hold This issue is parked, do not merge. label Oct 31, 2025
@EuroLew
Copy link
Contributor Author

EuroLew commented Oct 31, 2025

Hi @EuroLew 👋 - what version is this for please? I see you have specified a release, but haven't added the relevant release label - e.g. 8.9-alpha1 etc? Qe use the labels to group and triage docs work so it really helps to have the info upfront - thank you! 🙇

its getting merged into main so my understanding is my code changes would make it into 8.8.2 what label would I use then? I'm a bit confused here

Thanks @EuroLew the extra context is enough - sounds like this is for an 8.8.2 patch - looking at the files you have changed, those are just for 8.9, and would need to also be added to the versioned 8.8 folder if this is for 8.8 as well. I can help with that if you like?

It's ok I can do it, in conclusion:

  • backported to stable 8.8 so it should end up in 8.8.2 so I added the affects/8.8 label
  • to be merged into main so it should end up in 8.9.0 so I added the label 8.9.0-alpha1

this is correct?

@mesellings
Copy link
Collaborator

Yep sounds good - we also use the 8.9-alpha1 label as a guide to when it should be published - I think we're all good here - apologies as well, I've just noticed our template hasn't been updated following 8.8 which might have resulted in some confusion as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

8.9.0-alpha1 affects/8.8 hold This issue is parked, do not merge.

Projects

Status: 👀 In Review

Development

Successfully merging this pull request may close these issues.

3 participants