Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [leshan-dev] [iot-pmc] Leshan Roadmap
One main benefit of a formal 0.x release, IMO, is to provide a release with a fully approved IP log. Not only will this allow everyone using Leshan today to be more confident with its IP, but will certainly make it easier for an upcoming 1.0 should there be any IP problems that need to be addressed.


Benjamin -

Le 12 janv. 2018 à 15:51, Simon Bernard <contact@xxxxxxxxxxxxxxx> a écrit :

I agree this is a bit confusing. I try to explain the way it is here : https://github.com/eclipse/leshan/wiki/Roadmap

What does "ready" mean ? I think this is something like :
- when we thought that the API is stable enough
- when californium 2.0.0 will be out.
- when main needs of the community are cover. (limited by the scope of the 1.0.x LWM2M version)
E.g. We thought "object versioning" would not be in 1.0.0 scope because we thought that this was not so useful.. but community show interest on it and provide PR and now we work together to integrate it in the right way.

Let's think about releasing a 0.x version:
What does it means "a stable release by itself" ?
What would be the difference with our milestone releases ?
Does it will be more or less confusing to release a 0.x version which will be something between a 1.0.0-M4 and a 1.0.0-M5 ?
This 0.x version will depend of californium 2.0.0-M6, is it ok ?
Concretely what would be the benefits of this ?

Simon

Le 12/01/2018 à 09:15, Jens Reimann a écrit :
Hi Simon,

I got short question, maybe I missed something in this discussion.

You mentioned that you will do a 1.0.0 release when it is "ready" and that there is no roadmap. How do you define "ready" then?

In any case, I completely agree with Ian, that you should have a 0.x release, which might not be "ready" in a 1.0.0 sense. But still is a stable release by itself.

Thanks

Jens

On Thu, Jan 11, 2018 at 5:31 PM, Ian Skerrett <ian.skerrett@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Simon,

A couple of things:
- My comments are directly to all committers involved in the Leshan project. I don't believe it is your sole responsibility to make a release happen.
- Many projects will not do a 1.0 release until they finalize their APIs.  What they will do is a 0.7 or 0.8 release to demonstrate to their community that a release is available but the APIs might/will change. It seems to me Leshan might want to consider this approach.
- I appreciate Leshan wants to do it 'like Debian' but the key difference is Debian does actual releases and has developed a release cadence that their community can expect. I hope Leshan can move towards more predictability.

The good news is companies like Cumulocity are interested in using Leshan and I know there are other companies interested in using Leshan for their commercial products. I believe the Leshan project would better serve the community if they develop a more predictable release plan.

Ian

On 1/11/2018 5:58 AM, Simon Bernard wrote:

Ian,

Le 10/01/2018 à 20:18, Ian Skerrett a écrit :
Elias, are there specific features you are looking for in an M5 release?

Simon,

It is important that all Eclipse projects have a project roadmap that at a minimum provides a schedule for the next release.
 This is not the way we do, we will release the 1.0.0 version when it will be ready.
This is an important part of being an open, transparent project within the Eclipse community.
 We try to be as open and transparent as possible, we answer to all user questions and take into account user feedbacks, all our development is done in github transparently. We work closely with Californium project. We don't hide the roadmap we just have no roadmap, user inputs drive us.
I would highly encourage you to work with the other committers to create a plan and roadmap for Eclipse Leshan.
 I just talk for me : I will not do that but I suppose I could make sense to create a page which explain the way we actually work.

I also think it is important Leshan has a plan to do a formal release. Leshan has been in development for over 3 years so I think it is time to do a formal release view.
We are not ready for 1.0.0 version ... and by the way we are based on Californium 2.0.0 which is not released too (Please do not put pressure on Californium like you do here, this does not help at all)
If this is not fast enough for you, please contribute PR ...
A release review is an important step in validating the IP of Eclipse projects, again another important part of being an Eclipse project.
I would like to request the Eclipse IoT PMC to provide any assistance you might need to getting a format release review scheduled and completed.

Regards
Ian

On 1/10/2018 11:15 AM, Simon Bernard wrote:

Hi,

  There is no roadmap.
  But we can consider to release a new milestone soon if this is needed.

  Did you try to integrate master and see if it seems right for you ?

  If you are using the RedisRegistrationStore, we break the data structure compatibility, so you could be interested by [1].

Simon   

[1]https://dev.eclipse.org/mhonarc/lists/leshan-dev/msg00953.html

Le 10/01/2018 à 11:57, Elias Weingärtner a écrit :
Hi there,

just a short question: When can we expect the next Milestone (M5) to be released? Is there a public roadmap of the project?

Best Regards,
Elias


Try Cumulocity free at cumulocity.com.
Follow us on Twitter, Xing or LinkedIn.



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




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




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



_______________________________________________
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




--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill

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

Attachment: signature.asc
Description: Message signed with OpenPGP

Back to the top