isar-cip-core: Heading for a release cycle


Jan Kiszka
 

Hi all,

at least some of the isar-cip-core users are in a need for formal
release of the layer. The plan so far is to follow the Debian
point-release cycles, means basically having one every 3 months. First
one would then be after 11.7, likely mid to end of March.

What all that would mean for the layer recipes is to be defined. Already
clear is that we will offer snapshots of the Debian package sets via
snapshot.debian.org as build option. Beyond that, I plan to declare a
feature freeze at the end of February and only accept fixes before the
final release.

Long-term, we will also have to think about what kind of recipe changes
we consider as so breaking that they should be addressed with a "major
release" and how to continue maintenance of older branches after that.
But I would like to postpone that until we hit such a point AND hear
clear demands for such a branch.

Jan

--
Siemens AG, Technology
Competence Center Embedded Linux


Jan Kiszka
 

On 31.01.23 10:38, Jan Kiszka wrote:
Hi all,

at least some of the isar-cip-core users are in a need for formal
release of the layer. The plan so far is to follow the Debian
point-release cycles, means basically having one every 3 months. First
one would then be after 11.7, likely mid to end of March.

What all that would mean for the layer recipes is to be defined. Already
clear is that we will offer snapshots of the Debian package sets via
snapshot.debian.org as build option. Beyond that, I plan to declare a
feature freeze at the end of February and only accept fixes before the
final release.
Reminder as it is end of February now:

If you have any features to go into that first isar-cip-core release in
March, please push them now. I may grant some extra time till the end of
this week, but that I will feature-freeze.

Jan

--
Siemens AG, Technology
Competence Center Embedded Linux


Kazuhiro Hayashi
 

Hello Jan,

On 31.01.23 10:38, Jan Kiszka wrote:
Hi all,

at least some of the isar-cip-core users are in a need for formal
release of the layer. The plan so far is to follow the Debian
point-release cycles, means basically having one every 3 months. First
one would then be after 11.7, likely mid to end of March.

What all that would mean for the layer recipes is to be defined. Already
clear is that we will offer snapshots of the Debian package sets via
snapshot.debian.org as build option. Beyond that, I plan to declare a
feature freeze at the end of February and only accept fixes before the
final release.
Reminder as it is end of February now:

If you have any features to go into that first isar-cip-core release in
March, please push them now. I may grant some extra time till the end of
this week, but that I will feature-freeze.
No specific requirement from me.

If the Security WG is planning to make security feature available with bullseye
on one of CIP reference H/W, they need to be implemented / verified until
the feature freeze, otherwise they need to be targeted on bookworm.
Dinesh, do you have any opinions about this?

Kazu


Jan

--
Siemens AG, Technology
Competence Center Embedded Linux