Open ther3sa opened 2 months ago
Shall we add the #Feature section?
Examples:
Looks good!
just one thing, it might make sense to wait for eclipse-tractusx/eclipse-tractusx.github.io#865 to be merged to remove also the Styleguide point, which is also moved to a TRG
And just one small hint: the pull request title is very long, would maybe make sense to summerize to into something like
docs: update product release issue template
Hey Evelyn, what do you mean by Styleguide point? :)
@ther3sa there is a new TRG about styleguide: https://eclipse-tractusx.github.io/docs/release/trg-9/trg-9-01
Honestly, I would keep it out of the v24.08, and maybe ensure that is compliant in the v24.12.
Looks good! just one thing, it might make sense to wait for eclipse-tractusx/eclipse-tractusx.github.io#865 to be merged to remove also the Styleguide point, which is also moved to a TRG And just one small hint: the pull request title is very long, would maybe make sense to summerize to into something like
docs: update product release issue template
Hey Evelyn, what do you mean by Styleguide point? :)
I think I was confusing it with the point User Journey
, I suggest to either remove it or define who should check that in the future, as the role of the PO doesn't exist anymore
Looks good! just one thing, it might make sense to wait for eclipse-tractusx/eclipse-tractusx.github.io#865 to be merged to remove also the Styleguide point, which is also moved to a TRG And just one small hint: the pull request title is very long, would maybe make sense to summerize to into something like
docs: update product release issue template
Hey Evelyn, what do you mean by Styleguide point? :)
I think I was confusing it with the point
User Journey
, I suggest to either remove it or define who should check that in the future, as the role of the PO doesn't exist anymore
@ther3sa could you please provide feedback about the removal of the User Journey
or if it's not planned to remove it, who is supposed to check that?
Looks good! just one thing, it might make sense to wait for eclipse-tractusx/eclipse-tractusx.github.io#865 to be merged to remove also the Styleguide point, which is also moved to a TRG And just one small hint: the pull request title is very long, would maybe make sense to summerize to into something like
docs: update product release issue template
Hey Evelyn, what do you mean by Styleguide point? :)
I think I was confusing it with the point
User Journey
, I suggest to either remove it or define who should check that in the future, as the role of the PO doesn't exist anymore@ther3sa could you please provide feedback about the removal of the
User Journey
or if it's not planned to remove it, who is supposed to check that?
I am currently in the process of clarifying how we will deal with the user journey in future. I will provide an update on this as soon as I have a result. :)
@ds-hzimmer , @ds-tthies , @ther3sa as discussed ... @ther3sa and I adapted the content. Please have a look beforehand. Is something missing? If yes, please adapt.
We should check topics redundant. Some checks are already done via TRGs
@stephanbcbauer and @ther3sa Can we also add something like: Architecture Approval? Was not somthing that was mentioned in the last technical sync?
Do we also want to include dependencies? Like - Updated dependency graph?
@stephanbcbauer and @ther3sa Can we also add something like: Architecture Approval? Was not somthing that was mentioned in the last technical sync?
Do we also want to include dependencies? Like - Updated dependency graph?
Hi @matbmoser , the architecture approval will be addressed in the feature issue.
Could you please clarify what you mean by the dependency graph? I’m not entirely sure I understand your idea correctly.
Removed checks for interoperability, data sovereignty and threat modeling because of changes in the process
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: