| Re: [tractusx-dev] Open Source Planning for Tractus-X 19./25. October 2023 |
|
Good morning everyone, On this occasion, here is some more information about tomorrow's open refinement. The detailed description and the dial-in links can be found
here. The refinement will take place in parallel in the teams (for the respective topics). We currently assume that the whole 3 hours will not be needed for the team itself. In the remaining
time other topics/contributer (dependencies) are welcome to join the sessions. To discuss and thematize topics. Please
talk to each other here and communicate openly. You can find the respective main contact persons/POs in the tables. Feel free to use the mailing list for communication (open communication). The goal for the refinement is to develop a common understanding for the features and to document this also in the feature and/or in task breakdowns (linked issues in the dedicated
repository). If you want to contribute, please create the features on the sig-release repository and assign appropriate labels. Your feature should then be visible and filterable via the
view. I myself will create the features that Markus Hauser provides today until EOB. These should be familiar to you from the roadmap. There are some features, which might be also interesting for you. Maybe you also want to add your Subtasks/Issues here (@Zahn
Johannes, EG-124 thx for creating them)
Unfortunately I didn't manage to write a blog entry and you find the information anyway in the
wiki and
sig-release/Readme but please find attached a summery about "Working/Planning with GitHub".
It is a little bit more focused on the open refinement/planning topics. As always, please use your voice and give feedback. Looking forward to seeing you all tomorrow. Stephan Stephan Bauer Platform Domain Manager Catena-X Automotive Network e.V.
Vereinsregister beim Amtsgericht Berlin (Charlottenburg) Nr D1537 Vorstandsvorsitzender: Oliver Ganser From:
fabian.gruen@xxxxxxxxxxxxxxxxx <fabian.gruen@xxxxxxxxxxxxxxxxx> Hi all, thanks to you Stephan for your Feedback. To answer your questions:
„The features are created as agreed in the sig-release repository and provided with appropriate
labels. What other important configuration options are there? Labels, attributes for topics like PI, Release, Sprint... ?
Idea is to have an overarching View for the Releases and the upcoming Features / Bugs / Release Acceptance criteria that will provided for
the Release. „And I have the same question about the subtasks/issues
which are created in the specific repositories
by the teams. Are these labels/attributes also automatically available there? Or do they have to be set up manually?“
For all other Planning “Q&A”
https://github.com/eclipse-tractusx/sig-release/discussions/categories/q-a everyone can also create a little Discussion on the sig-release repo to bring everyone to the same knowledge base or even can share their problems with it. Cheers,
Fabian Von: Stephan Bauer <stephan.bauer@xxxxxxxxxxxx>
[**EXTERNAL E-MAIL**]
Hello Fabian, thank you for the email and the link. I personally do not miss any label right now :) But have a question about the "configuration" of the issues.
The features are created as agreed in the sig-release repository and provided with appropriate labels. What other important configuration options are there? Labels, attributes
for topics like PI, Release, Sprint... ? And I have the same question about the subtasks/issues
which are created in the specific repositories
by the teams. Are these labels/attributes also automatically available there? Or do they have to be set up manually? Once the features are initially created, I'd like to have another "Get Ready" session where these questions can be clarified and any outstanding planning/configuration
issues can be discussed. Should be with beginning of next week. Many greetings ... ... and have a nice day ( to the whole community) Stephan Bauer Platform Domain Manager Catena-X Automotive Network e.V.
Vereinsregister beim Amtsgericht Berlin (Charlottenburg) Nr D1537 Vorstandsvorsitzender: Oliver Ganser
|
Attachment:
Open-Refinement-Planning.md
Description: Open-Refinement-Planning.md
