| Re: [openpass-sc] openPASS v1.0 |
|
Hi all, Thank you for the feedback! I totally agree Per. GitLab is the single source of truth. I only used MS Project to illustrate the roadmap to v1.0. So let’s stick to the plan for now and let’s see how far we are coming with our efforts. Next week we will synchronize anyway. Kind regards Tuan From: Schoenawa, Stefan, Dr. (K-GERM/A) <stefan.schoenawa@xxxxxxxxxxxxx>
"Attention! External Mail. Be careful with Links/Attachments!" Hi all, I’m fine with you proposed timeline and would underline the “quite challenging [date]”. On Thursday I’m going on vacation, but Gwendal will be back next Monday. Please keep him in the loop. I already said to the Hexad, that they should
have a look on the gitlab (and especially on occurring issues) and they will solve/fix them with high priority. Furthermore, they will have a look into Jenkins and the automatically build process. The first estimation was that this will be quite simple for the frontend part, but maybe a little bit more time-consuming for the backend/middleware part. BR, Stefan INTERNAL Von: Per.Lewerenz@xxxxxxxxxxxxxxxxx <Per.Lewerenz@xxxxxxxxxxxxxxxxx>
Hi Tuan, thanks for the proposal. As for the topics themselves, we will allocate as much capacity as possible to review/test the MR as discussed. However, we should remain realistic and, as you wrote, do not forget that we have limited resources due to the holiday season. In general, i personally would prefer to label the major GitLab issues as "major" more than having a parallel ms-project timeline with “new” task-names. BR Per Von: Duong Quang, Tuan <tuan.duongquang@xxxxxxxxxx>
[**EXTERNAL E-MAIL**]
Hi all, in the last SC meeting we have decided to aim for the release date 21st August for v1.0. The date is quite challenging especially because some key players are already
on vacation. In addition to that we have 28 ongoing issues in GitLab for v1.0. Nevertheless, I have summarized the “major” issues. Thus, I would like to check if the proposed timeline is possible:
I want to point out that the v1.0 shouldn’t be perfect. After the v1.0 release we can still release in a faster cycle a v1.1, v1.2 and so on. The 21st August will be my last day in office. I will come back on the 25th September. @Per.Lewerenz@xxxxxxxxxxxxxxxxx,@Schoenawa,
Stefan, Dr. (K-AERT/A),@Katharina.Donauer@xxxxxx
Could you please give me feedback about the timeline? Is anything missing? Kind regards Tuan From: Duong Quang, Tuan Hi all, thank you Jan for your proposal and the summary. We have some open topics to discuss as a working group. Therefore, I would like to organize a 2 hours planning v1.0 workshop to discuss Jan’s points and the further planning.
Topics:
I hope we can find a proper time slot on short notice. Please participate in the following poll:
https://doodle.com/meeting/participate/id/eX5wExoa. Kind regards Tuan From: openpass-sc <openpass-sc-bounces@xxxxxxxxxxx>
On Behalf Of Jan Dobberstein Daimler via openpass-sc "Attention! External Mail. Be careful with Links/Attachments!" Dear openPASS fellows, I would like to summarize the “road to a 1.0 release”. Until now, we have released minor releases of opSimulation (earlier simopenpass) Eclipse openPASS | projects.eclipse.org NEW: the release of openPASS v1.0 with the new architecture would look like this (Tractus.X)
3.0 | projects.eclipse.org: “The Tractus-X release 3.0 includes the following repositories: https://github.com/eclipse-tractusx/app-dashboard https://github.com/eclipse-tractusx/autosetup-backend https://github.com/eclipse-tractusx/bpdm/tree/v3.0.3 https://github.com/eclipse-tractusx/charts (…)” Hence: “The openPASS release 1.0 includes the following repositories https://gitlab.eclipse.org/eclipse/openpass/opSimulation/1.0.0 https://gitlab.eclipse.org/eclipse/openpass/mantle-api/1.0.0 https://gitlab.eclipse.org/eclipse/openpass/openscenario1_engine/1.0.0 https://gitlab.eclipse.org/eclipse/openpass/yase https://gitlab.eclipse.org/eclipse/openpass/opgui …hence, openPASS v1.0 is a release across all these repos, where certain subrepos would also have a major release. Definitions of done:
Status:
Next steps (..just a proposal): @Tuan: could you suggest a timeline for the v1.0: when are the subcomponents available, when will the review/testing take place, time to address findings? @VW could you already provide a current status of opGUI to a feature branch? And a time plane, please note that we need to consider some time for testing the GUI before releasing v1.0 @BMW/Arun: how should we align the versioning topic of the mantle/ose with opSimulation? Please feel free to add steps and comments to my thoughts! Take care, Jan Jan Dobberstein Mercedes-Benz AG 71059 Sindelfingen Wenn diese Email nicht für Sie bestimmt ist, bitten wir Sie, uns umgehend über den irrtümlichen Empfang zu informieren und diese Email zu
löschen. Wir danken Ihnen für Ihre Unterstützung.
Mercedes-Benz AG, Stuttgart, Germany
Sitz und Registergericht/Domicile and Court of Registry: Stuttgart, HRB - Nr./Commercial Register No. : 762873 Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Bernd Pischetsrieder Vorstand/Board of Management: Ola Källenius, Vorsitzender/Chairman; Jörg Burzer, Renata Jungo Brüngger, Sabine Kohleisen, Markus Schäfer, Britta Seeger, Hubertus Troska,
Harald Wilhelm
|
