Hello,
this may be a repeated email for some of you, but I had some trouble with the mailing list. I hope it works.
Please read below.
Cheers,
Bor
Hello colleagues,
I am a little confused with the release and the new structure of repositories. Now we have three repos:
· unide.java
· unide.python
· unide
The first two ones are obviously for the java and python development, but the third one (the original one) is not very clear to me what should be used for. Moreover, it has been released as 0.1.0 containing only Java code.
In my opinion, the old “unide” repository should be one of those:
· A dummy repository with links to unide.python and .java. If used like this, there is no need for versioning or releases.
· A repository containing ppmp specification (and maybe the unide web). In this case, it makes sense to version/release it.
Once this is said, this would be our immediate plan for unide.python:
· Wait for access rights to unide.python repository
· Move the old repository to its new place and delete the old one.
· Do some minor corrections on unide.python (links, etc)
· Tag it as 0.1.0
· Release it in PyPI and github
· Remove the 0.9.0 version from PyPI
Moreover, I’d like to say that ideally, unide.java and unide.python (and the many more to come like unide.c or .go) would run in parallel with same version numbers and offering the same capabilities… but this is the real world, they are at the end different projects and I’m pretty sure they are going to diverge and have different capabilities and version numbers. So there is no big reason to be very strict with the versioning of those subprojects…
Would this be OK? Are we all on the same page?
Cheers,
Bor
Mit freundlichen Grüßen / Best regards
Axel Meinhardt
(INST-INL/PRM1)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch-si.com
Tel. +49 30 726112486 | Mobil +49 173 5173094 | Fax +49 30 726112-100 | axel.meinhardt@xxxxxxxxxxxx
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn
Hi all,
sounds good! To begin with, we should approach the repo problem really soon now.
@Bor: we should pull the unide-python from PyPI then and replace it with one with the right release number. @Others: we have to have a unide-python distro on PyPI for automated deployments/builds to work. Any suggestions what we should use as a version while the overal Unide relase is at 0.1.0?
P.S: did I somehow miss that there is a unide-dev list now?
Unide Release 0.1.0 has approved,
So I’ve scheduled the next release for 31.01.2018:
o Benjamin: you wanted to review this, any updates here?
What’s your opinion/feedback on this plan?
Mit freundlichen Grüßen / Best regards
Axel Meinhardt
(INST-INL/PRM1)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY |
www.bosch-si.com
Tel. +49 30 726112486 | Mobil +49 173 5173094 | Fax +49 30 726112-100 | axel.meinhardt@xxxxxxxxxxxx
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn