| Re: [iot-pmc] Concierge 1.0 release review |
Okay, that sounds like a good plan. Let me quickly (within the margin of time zones) run the idea by the other committers (and the dev-list in case somebody else has an opinion about it) and I will then adjust the version number in the release plan accordingly. I am not sure if I need to re-submit my request for approval of the release review documentation because of this change but I will possibly do it just in case…
Regarding graduation, I think you (Jens and Kai) brought up very reasonable concerns and I see some improvements coming to the project in the immediate future so I would suggest I remove the graduation request, give the other committer and me some more time to work on the material, fix some of the pain points, and hopefully see the community picking up our release to an extent that justifies graduation more clearly. There is the possibility of a minor release on the horizon for when we got full IP approval for my OSGi REST reference implementation to be moved to Concierge so I guess we can target this as a possible time for graduation or even wait for the next major release.
Re: Possible Jens and myself are simply (too) German
No prob, I’ve been there, too. 17 years later, some people still think I am J
--Jan.
From: iot-pmc-bounces@xxxxxxxxxxx [mailto:iot-pmc-bounces@xxxxxxxxxxx] On Behalf Of Kai Kreuzer
Sent: Thursday, October 8, 2015 3:56 PM
To: PMC list for IoT top level project
Subject: Re: [iot-pmc] Concierge 1.0 release review
Ok, so +1 on a version >= 1.0 - with the existing release 1.0 on SF, I would actually agree with Benjamin that Concierge should consider to directly go to 2.0.
_______________________________________________
So what’s your opinion on the graduation part then?
Regards,
Kai
Am 08.10.2015 um 22:45 schrieb Benjamin Cabé <benjamin@xxxxxxxxxxx>:
@Benjamin: Are you suggesting that Jan should release a 1.0/2.0/5.0, but does NOT have to graduate at the same time, but could stay an incubation project? How can it be told that a project is in incubation then?
Absolutely. vert.x for example is still incubating, and releasing >1.0 versions [0] since they already had a “life” before Eclipse.
I’m just referring to the Eclipse Development Process [1] here. The only requirement is for incubating projects to make it clear in their branding [2] (bundle-name, features names, downloadable ZIP distros, etc) that it’s an incubation project. Also, the Wiki page [3] about the requirements for releases of an incubating project is pretty clear regarding possible having >1.0 releases.
Possible Jens and myself are simply (too) German and we wanted to follow the rules as we understood them for new Eclipse projects ("the Eclipse Way“).
There might be some documentation that refers to the now obsolete requirement that incubation means < 1.0, so if that’s what got you confused, please point us at the culprit documents.
HTH
Benjamin –
_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc