Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Release records on Eclipse PMI

Dear all, 
@Wayne Beaton has already opened an issue regarding this topic, here:
https://gitlab.eclipse.org/eclipsefdn/it/websites/projects.eclipse.org/-/issues/146
Please feel free to add any feedback directly there. Some work around it is already being carried out by the EF team.
Kind regards,
Maria Teresa Delgado

On Mon, Jan 8, 2024 at 3:32 AM Gunnar Wagenknecht via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:
Happy New Year from me as well!

I do believe that we don't have specific requirements in the EDP, which require the use of PMI to create release records. If there is anything vaguely impacting communication it would be 4.10 Project Plans (https://gitlab.eclipse.org/eclipse/vhant/development-process/-/blob/master/source/development_process.adoc?ref_type=heads#4_10_Plans). 

Especially if the PMC agrees, I believe GitHub Releases is a great way to communicate releases to the community. If anything, the PMI needs to be enhanced to connect/link with GitHub releases allowing projects to avoid populating information twice.

I'd support any PMC attesting that GitHub Releases is in alignment with the EDP communication requirements.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/



On Jan 8, 2024, at 09:48, Hudalla Kai (BD/TOA-IDE2) via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:

Dear Architecture Council,

I wish all of you a happy new year and would like to get your opinion on the following:

During the last months I have seen several projects which do no longer seem to create release records on the Eclipse PMI for their projects and/or project components.

For example, the Eclipse Keyple project is currently engaging in a progress review [1] and maintains multiple components with distinct release cycles under the scope of the Keyple project. They seem to have created a release per month on average per component last year and keep track of these releases on their project website's changelog [2] but did not create corresponding release records on the PMI for these releases [3].

I also see other projects adopting this habit, e.g. using only GitHub releases. In all these cases it seems that the records on the PMI do/would not provide any additional value so I wonder if we cannot simply get rid of them altogether and simply use the PMI to keep track of the progress reviews.

In the meantime, the IoT PMC has been asked to approve the Keyple project's progress review and I wonder if we can indeed attest that the project is following the EDP, given that they do not create the release records on the PMI? Any input would be helpful here ...


Mit freundlichen Grüßen / Best regards

Kai Hudalla

Center of Excellence Open and Inner Source
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Mobil +49 151 54336335

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; Geschäftsführung: Dr. Stefan Hartung,
Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus Heyn, Dr. Tanja Rückert

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council


--
The Eclipse Management Organization | Eclipse Foundation

Back to the top