Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [unide-dev] 0.2.0-SNAPSHOT: new website / repo structure / fixed schemas

Kai,

I don’t believe it is Axel’s intention to publish a 0.2.0 release without going through a proper release review, and AFAICT so far the 0.2.0 is indeed scheduled by the project for the end of this month - https://projects.eclipse.org/projects/iot.unide/releases/0.2.0
What needs to be highlighted though, is that having the Python biding will require the associated CQ to be fully approved by the IP team, so Axel, make sure to give the IP team a heads-up that you have a release coming. What’s more, if you plan on contributing the HTML 5 UI, my recollection is that there were a lot of libraries associated to this, so again make sure you have the IP team onboard, and an approved IP log.

WRT 0.1.0, I hate to curb your enthusiasm, Kai, but 0.1.0 is an approved release :-) See https://bugs.eclipse.org/bugs/show_bug.cgi?id=526231


Benjamin -


Le 17 janv. 2018 à 16:30, Hudalla Kai (INST/ECS4) <kai.hudalla@xxxxxxxxxxxx> a écrit :

Hi Axel,

I hate to curb your enthusiasm but you cannot simply create a release and publish it without going through the Eclipse release process as described in the Project Handbook [1].

What you can do, is publishing milestones. However, these need to be marked accordingly, i.e. the version in artifact names needs to reflect the milestone character like here: unide-java-0.2.0-M1.jar

You can also, of course publish SNAPSHOT builds on the Eclipse repository. But again, the version needs to indicate the snapshot character: unide-java-0.2.0-SNAPSHOT.jar

You should also open a ticket with the webmasters to remove the 0.1.0 artifacts that you have published to the Unide releases repository at Eclipse.

Thanks,

Kai

[1] https://www.eclipse.org/projects/handbook/#release


On 17.01.2018 14:20, Meinhardt Axel (BCI/ECM2) wrote:
Hi,
 
I ran the Jenkins jobs to put the release 0.1.0 on the eclipse repository [1]. So the current version is 0.2.0-SNAPSHOT.
I have split the java binding from the main repo [2] to unide.java [3].
Updates for the rest server as described in [4] are still to be pushed (this or next week). Nevertheless, the new website would be based on the fixed schemas [5]. I also recreated and synched the uml diagrams [6], [7], [8].
So finally, the schemas are consistent with the documentation on the website are consistent with the uml diagrams. I hope, especially for the process payload, that the contradictions haven’t led to implementations that are not conforming to the current state.
If we also get the unide.python up, I think that makes a nice release 0.2.0 scheduled for end of the month.
What do you think?
 
 
 
Best regards / Mit freundlichen Grüßen / Üdvözlettel / 致以诚挚的问候

Mr. Axel Meinhardt
Bosch Connected Industry – BCI/ECM2, Technical Lead Ecosystem
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY
 | www.bosch-si.com 
Phone +49 30 726112486  | Mobil +49 173 5173094  | axel.meinhardt@xxxxxxxxx

Registered office: Berlin, Register court: Amtsgericht Charlottenburg; HRB 148411 B;
Executives: Dr.-Ing. 
Stefan Ferber, Michael Hahn
 


_______________________________________________
unide-dev mailing list
unide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/unide-dev

-- 

Mit freundlichen Grüßen / Best regards

Kai Hudalla
Chief Software Architect

Bosch Software Innovations GmbH
Ullsteinstraße 128
12109 Berlin 
GERMANY
www.bosch-si.com

Registered Office: Berlin, Registration Court: Amtsgericht Charlottenburg; HRB 148411 B
Chairman of the Supervisory Board: Dr.-Ing. Thorsten Lücke; Managing Directors: Dr. Stefan Ferber, Michael Hahn

_______________________________________________
unide-dev mailing list
unide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/unide-dev

Attachment: signature.asc
Description: Message signed with OpenPGP


Back to the top