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

doc(open planning): add new entry for open planning release 24.08 #686

Merged
merged 5 commits into from
Feb 22, 2024

Conversation

stephanbcbauer
Copy link
Member

Description

This PR is the preparation for the next open planning r24.08. It provides some information, like:

  • new open meeting entry (ics file and session link)
  • news blog entry (agenda is not publishes yet)

image

image

image

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

add initial news blog
add open meeting
delete old open meetings
@stephanbcbauer stephanbcbauer added the documentation Improvements or additions to documentation label Feb 19, 2024
@stephanbcbauer stephanbcbauer self-assigned this Feb 19, 2024
danielmiehle
danielmiehle previously approved these changes Feb 19, 2024
@mabige
Copy link

mabige commented Feb 20, 2024

Regarding: "The goal for this meeting is the planning of the features for the next Tractus-X release"

In fact it is not only the feature planning for the next release. Finally it is the planning of the intended work content for the next program increment - which contains also preparation of future release content, refactoring, general architectural work, tool & process improvement, ...

Of course are the features for the next release usually the main content.
But the other part should not be neglected -> technical depts.

@stephanbcbauer
Copy link
Member Author

Regarding: "The goal for this meeting is the planning of the features for the next Tractus-X release"

In fact it is not only the feature planning for the next release. Finally it is the planning of the intended work content for the next program increment - which contains also preparation of future release content, refactoring, general architectural work, tool & process improvement, ...

Of course are the features for the next release usually the main content. But the other part should not be neglected -> technical depts.

Thx, adpated the description

Copy link
Contributor

@FaGru3n FaGru3n left a comment

Choose a reason for hiding this comment

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

LGTM small remark to a link

Copy link
Contributor

@carslen carslen left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

@FaGru3n FaGru3n left a comment

Choose a reason for hiding this comment

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

LGTM

@stephanbcbauer stephanbcbauer merged commit ce3aa66 into main Feb 22, 2024
4 of 5 checks passed
@stephanbcbauer stephanbcbauer deleted the doc/add-open-meeting-r2408 branch February 22, 2024 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants