Re: [iot-pmc] Request assistance for Eclipse Keyple®

[Pierre Terree <pierre.terree@xxxxxxxxxxxxxx>]

Exactly Kai, after version 2.0.0, all the components are released individually from each other.

We did release trains only for Keyple 0.7.0 to 2.0.0. So, for the C++ implementation, this release will be the last release train requiring to have all the components in the same version.

 

De : Hudalla Kai (IOB/PAD-PM) <Kai.Hudalla@xxxxxxxx>
Date : lundi, 29 août 2022 à 15:38
À : Pierre Terree <pierre.terree@xxxxxxxxxxxxxx>, PMC list for IoT top level project <iot-pmc@xxxxxxxxxxx>
Objet : Re: Request assistance for Eclipse Keyple®

I am not sure if I fully understand the strategy.

 

> The feature scope of the smartcard reader plugins is stable. We have mainly published patch evolutions (keyple-plugin-android-omapi-java-lib:2.0.1, keyple-service-resource-java-lib:2.0.2)

 

This sounds like you are versioning (and releasing) the components individually from each other, or am I mistaken? When you released keyple-service-resource-java-lib:2.0.2, did you also release a 2.0.2 version of the other components?

---

From: Pierre Terree <pierre.terree@xxxxxxxxxxxxxx>
Sent: Thursday, August 25, 2022 1:34:12 PM
To: Hudalla Kai (IOB/PAD-PM); PMC list for IoT top level project
Subject: Re: Request assistance for Eclipse Keyple®

 

From version 2.0.0 of Keyple, each component evolves in its own life cycle with a versioning strictly respecting the rule Major(Breaking Release).Minor(Feature Release).Patch(Fix Release).

• For a fix release of a component, we publish a patch version ASAP when available. Keyple components will not necessarily have the same patch version depending on the Java or C++ implementation.
• For a particular component, we release a new major/minor version when a consistent set of new stable features is available. Java & C++ implementations of a Keyple's component will be release with the same major.minor version. We will try to synchronize the major.minor release for Java & C++ implementations.

 

For example, about the latest developments of Keyple Java's components:

• The feature scope of the smartcard reader plugins is stable. We have mainly published patch evolutions (keyple-plugin-android-omapi-java-lib:2.0.1, keyple-service-resource-java-lib:2.0.2).
• Lately, the development of new functionalities has mainly been done on the Calypso card processing library keyple-card-calypso-java-lib(2.2.1), for which new extensions are still to be provided (https://keyple.org/community/roadmap/#evolutions-of-the-keyple-components-after-the-version-200-of-the-sdk ).

 

De : Hudalla Kai (IOB/PAD-PM) <Kai.Hudalla@xxxxxxxx>
Date : jeudi, 25 août 2022 à 14:42
À : Pierre Terree <pierre.terree@xxxxxxxxxxxxxx>, PMC list for IoT top level project <iot-pmc@xxxxxxxxxxx>
Objet : Re: Request assistance for Eclipse Keyple®

Ok, understood. And what about the release strategy?

---

From: Pierre Terree <pierre.terree@xxxxxxxxxxxxxx>
Sent: Thursday, August 25, 2022 7:50:51 AM
To: PMC list for IoT top level project
Cc: Hudalla Kai (IOB/PAD-PM)
Subject: Re: Request assistance for Eclipse Keyple®

 

Hi KaI,

In fact, the Keyple project is still incubation phase, we never asked for the graduation.

 

There was an error on the Keyple PMI page, the logo of the project had been customized during the year, I removed it, and now it is well the Incubation logo which is visible.

 

De : iot-pmc <iot-pmc-bounces@xxxxxxxxxxx> de la part de Hudalla Kai (IOB/PAD-PM) via iot-pmc <iot-pmc@xxxxxxxxxxx>
Date : mercredi, 24 août 2022 à 12:26
À : iot-pmc@xxxxxxxxxxx <iot-pmc@xxxxxxxxxxx>
Cc : Hudalla Kai (IOB/PAD-PM) <Kai.Hudalla@xxxxxxxx>
Objet : Re: [iot-pmc] Request assistance for Eclipse Keyple®

Hi Pierre,

 

to me it looks like Eclipse Keyple has already graduated from incubation. At least the PMI [1] does not indicate that it is still in incubation, otherwise the incubation logo would show up on the right hand side of the page.

 

Apart from that I would like to make sure that I understand your approach to releasing Keyple correctly.

It looks to me like you are maintaining the Java and C++ based code in a separate release train, i.e. the Java variant's artifacts are being released independently from the C++ variant's artifacts. Is that correct?

 

[1] https://projects.eclipse.org/projects/iot.keyple

---

From: iot-pmc <iot-pmc-bounces@xxxxxxxxxxx> on behalf of Pierre Terree <pierre.terree@xxxxxxxxxxxxxx>
Sent: Friday, August 19, 2022 8:33:03 PM
To: iot-pmc@xxxxxxxxxxx
Subject: [iot-pmc] Request assistance for Eclipse Keyple®

 

Dear IoT PMC,

We are preparing the publication of release 2.0.0 of the C++ implementation of the Eclipse Keyple project.

This is a C++ porting of the Keyple Java 2.0.0 implementation we had already released last October.

 

Could you please review the C++ 2.0.0 release information https://projects.eclipse.org/projects/iot.keyple/reviews/2.0.0-c-2207-keyple-release-review

Here is the link provided by the EMO team to track the release review https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/335

A review of the IP log has been requested to EMO (in progress) → https://dev.eclipse.org/ipzilla/show_bug.cgi?id=24101

 

We expect to validate the release 2.0.0 of Eclipse Keyple C++ on the 7 of September. on this occasion, we would like the project to move from the incubation phase to the mature phase.

 

Discussion regarding Eclipse Keyple

 

https://projects.eclipse.org/projects/iot.keyple