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?“
- Labels on specific repositories can be created by any Committer in the Teams for their repositories, so simple
answer manually and it depends on the need for each team / part of the repository.
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>
Gesendet: Mittwoch, 11. Oktober 2023 18:18
An: Gruen, Fabian (415) <fabian.gruen@xxxxxxxxxxxxxxxxx>; tractusx-dev@xxxxxxxxxxx
Betreff: Re: Open Source Planning for Tractus-X 19./25. October 2023
[**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.
Reinhardtstr. 58 • 10117 Berlin
Tel: +49 30 53607799 Mobil +49 151 67353921
stephan.bauer@xxxxxxxxxxxx
Folgen
Sie uns auf LinkedIN
Vereinsregister beim Amtsgericht Berlin (Charlottenburg) Nr D1537
Vorstandsvorsitzender: Oliver Ganser
Hi all,
regarding to this open Planning and Review Sessions there are some missing labels for the products, kits, etc. within sig-release repository.
Maybe you have also a hint or wish want we want to have as label. See Discussion
https://github.com/eclipse-tractusx/sig-release/discussions/205
Roland and I will generate some best suggestions for the parts of Eclipse Tractus-X in scope of Release Management, but maybe you want to adapt or change some labels.
Feel free to state out your label for your part in the discussion.
Greets Fabian
[**EXTERNAL E-MAIL**]
Hello Open Source Enthusiasts!
🎉
the Catena-X open-source reference implementations are currently mainly driven by the Catena-X
consortium. We want to open-up the software development
step by step and therefore warmly invite you to shape and contribute to this reference implementation!
To get more transparency about the status and product roadmaps of our reference implementations, we will conduct refinement and planning meetings
in the Tractus-X open-source community.
We're thrilled to announce our upcoming planning sessions for Tractus-X:
-
Open Refinement Session on 19.10.2023
-
Open Planning/Review Session on 25.10.2023
Here's your chance to be part of an exciting journey from the ground up.
Read More …
Kind regards
Stephan Bauer
Plattform Domain Manager
Catena-X Automotive
Network e.V.
If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.
|