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
_______________________________________________
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
|
