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

Update optimize C7 release workflow #4599

Closed
2 tasks done
Tracked by #22258
misiekhardcore opened this issue Sep 13, 2024 · 2 comments
Closed
2 tasks done
Tracked by #22258

Update optimize C7 release workflow #4599

misiekhardcore opened this issue Sep 13, 2024 · 2 comments
Assignees
Labels
scope:optimize Changes to Optimize. type:task Issues that are a change to the project that is neither a feature nor a bug fix.

Comments

@misiekhardcore
Copy link

misiekhardcore commented Sep 13, 2024

Acceptance Criteria (Required on creation)

After successfully updating the release workflow in the monorepo, we now can follow the same changes for Optimize C7

  • separate release:prepare and release:perform maven commands
  • push changes not with one of the commands, but do the push separately in between them (to resolve permissions issues we encountered in the past)
  • create tag and release also in examples repository

Hints

Links

Breakdown

Pull Requests

Dev2QA handover

  • Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment
@misiekhardcore misiekhardcore added type:task Issues that are a change to the project that is neither a feature nor a bug fix. scope:optimize Changes to Optimize. labels Sep 13, 2024
@RomanJRW
Copy link
Contributor

@misiekhardcore - I think we should keep the AP7 team issue template for issues in their repo rather than copying the Optimize one over

@misiekhardcore
Copy link
Author

@RomanJRW I am closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:optimize Changes to Optimize. type:task Issues that are a change to the project that is neither a feature nor a bug fix.
Projects
None yet
Development

No branches or pull requests

2 participants