On 23.01.2018 11:38, Simon Bernard wrote:
Release a 2.0.0-RC means feature freeze and API freeze. Are we ready for that ?
I am not saying that we do the RC this week. All I am saying is that I would like to do a 2.0.0 release in the near future. FMPOV this goal helps us in focusing on things that must go in 2.0.0 and do a triage on things that we would like to see in 2.0.0.
I'm a bit perplex with this sudden urgency.
There is nothing sudden about it :-) We have been targeting the 2.0.0 release for Jan/Feb 2018 since EclipseCon Europe 2017. I have even communicated it in replies to inquiries on the mailing list.
Le 23/01/2018 à 09:05, Hudalla Kai (INST/ECS4) a écrit :
On 22.01.2018 17:56, Kraus Achim (INST/ECS4) wrote:
Dear Californians,
after merging PR #521 fixing the "theoretical token issue", I would like to release
Milestone 2.0.0-M7
to see, if our release job is now working and proper building the
"element-connector-tcp" and "git history".
There is one Bug open (see https://github.com/eclipse/californium/pull/527),
but though I would like to wait a couple of days for the feedback/voting,
I would prefer to release 2.0.0-M7 without that bugfix.
Any opinions on that?
Sure, go ahead. However, be aware that I have split up the parent-release build job into three parts:
1. parent-release - now simply builds, runs tests and creates the release tag in the repo
2. parent-deploy-eclipse - checks out a tag, builds and signs artifacts and deploys to Eclipse repo
3. parent-deploy-maven - checks out a tag, builds and signs artifacts and deploys to Maven Central staging repo
I did this in order to be able to re-try the deployment steps (which have failed often in the past) without the need to re-create the tags. So, once the parent-release job has been run successfully, you can trigger the other jobs to either deploy to Eclipse
or Maven Central.
I would also like to do a 2.0.0-RC in the (very) near future in order to prepare the 2.0.0 release :-)
Mit freundlichen Grüßen / Best regards
Achim Kraus
(INST/ECS4)
Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY | www.bosch-si.com
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-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
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-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
|
