Dear community,
As you know, we are in the
refinement phase. Now its time to proactively refine the features -> driven by the
committee/expert groups from the association. Your help as contributor/committer is needed.
It is important to work together during the refinement phase. Committees and expert groups are responsible for creating the features (requirements). They support the features throughout the entire release and contribute
their expertise. The open-source community is essential for the technical part and must be involved in the refinement of the features (especially the committers). Without a committer, the feature won't make it into the release.
Contributors/Committers should create Issues aon product specific repositories and link them with the feature.
Terminology: feature proposal
should be linked with one or more User Stories/Subtasks (issues in product-specific repositories)
DRAFT Feature freeze
This Friday we will have our next meeting in the refinement phase. As always for open meetings, you can find it on the
open meetings page. This event is organised and moderated by the Catena-X Association. Until this date, feature proposal can be submitted to the
planning board (in GitHub). The status (as an interim status in the refinement phase) of the previous feature proposals will also be discussed at this meeting.
This is an opportunity to talk about the current refinement state, locate dependencies, discuss, and ask questions related to the feature, the process. The feature author/assignee is driving the
feature.
To be able to talk about features, for sure we need features on the board. Here is just a short reminder how are
features created on the board in the
sig-release repository.
Please note that while you are technically creating an issue, in the business process, this is referred to as a “Feature proposal.” To avoid confusion, keep the following guidelines in mind for each
issue you create:
- MUST set the label “Prep-R24.12” (only issues with this label will be
considered in the refinement/release planning).
- MUST keep the status on “Inbox” until the feature met the Definition
of Entry
- SHOULD set additional labels to highlight dependencies to other components
(e.g. portal, edc …)
- MUST NOT set the Milestone. This is done together during planning
days
- SHOULD include as much detail as possible in the issue. Please refer
to the Definition
of Entry (DoE) for guidance.
- MUST add a link to the new generated issue in the corresponding roadmap
item
- MUST link the supporting Group with filed supported-by (open the feature
-> right box “Release Planning”). If your Expert Group is not available, please select the committee
If a feature is further broken down into tasks by adding issues in the component repositories, these issues MUST be linked
to their parent feature proposal.
Who is invited
- Everybody, it’s an open meeting
- Expert groups
- Committees
- former product owner
Agenda
- 09:05 – 09:30 Welcome, overview, current phase, expectations, tooling, boards
- 09:30 – 11:00 Feature discussion
group by group
*
- 11.00 – 12:00 Buffer
*
This views shows the features, which could be discussed (if your feature is not on the board, make sure, you used the correct labels)
=> currently, there are 22 features (from Networks Service Committee and related Expert Groups) and 1 from Industry Core
Next Milestone Events:
- 22.07. -
Refinement
Day 2: Further refinement, dependency discussions, status update and validation, setting the status to “Backlog” upon meeting entry criteria.
-
31.07. and 01.08 - Planning
Days: Present the features which already met the DoE. The milestone is
set to 24.12 if the audience agrees on it. Features with milestone MUST now have a committer and all dependencies MUST be
resolved.
Stephan