thanks for your thoughts.
No, we've not had any releases yet. But in my opinion, the Java,
talk to Roger about the Python client. We are getting regular bug
reports for the Java and C clients.
I thought a release would be a useful way of promoting Paho (as
you say, signalling that the included components are ready for
production) as well as making sure the project is in good shape
from an admin point of view.
When you say "incubating" release, you mean as opposed to a
Graduation Review, or Simultaneous Release? If so, I say yes,
this time around. As Wayne suggested, I think aligning dates with
the Simultaneous Release would be highly desirable.
On 27/11/13 20:17, David M Williams wrote:
> Are the mentors
subscribed to the dev list?
Yes, "we" are subscribed.
I think Wayne's covered many of
basics for the mechanics ... or, given the links that do.
But will add my high level
Given the "age" of the project,
I'd say a release was in order. (You've not had any, yet,
But, that should be balanced with
"need" for one. One thing that characterizes a "release"
is that it becomes relatively permeant, and to some degree (of
mostly, driven by your adopters) maintenance releases would
.... in addition to your next "major" release stream.
A "release", to me, sends
a message that "this is ready for production use" (again, with
what ever qualifications you wanted) ... but definitely it says
a "milestone" or "checkpoint" build ... which we typically
advise people to never use those production.
I'm assuming this would still be
"incubating" release? Sorry I've not kept closer track, but
you've been having regular "milestone" and/or "integration"
builds ... and assuming you've been getting good bug reports
then I'd think a release (even if incubating) would be good. If
not getting much "adopter use" yet and/or have a ways to go
being "usable in production" then that might be reason to
it more carefully, as it would not serve much purpose and might
All that said, I'm happy to
specific questions and/or "catch up" with the project to give
more specific advice, if you head in that direction.
Thanks, and good luck!
General development discussions for paho project
11/27/2013 02:36 PM
Release Planning for Paho - thoughts?
Are the mentors subscribed to the dev list? It
a good idea to reach out to them to make sure they are (we don't
For releases, start here:
That will take you to here:
which will encourage you to use the project page to enter
on the project page.
There's loads more information here (but start with the "release
Other than the checklist, I believe that most of the review
are language and technology agnostic. The checklist on the
Reviews" page does reflect our "mostly Java" heritage. I'll
have to take a pass at it with language generalization in mind.
meantime, if something just doesn't make sense for Paho, use
judgement to either ignore the item or adapt to your situation.
In terms of simultaneous release participation, that might be a
for the cross-project-issues-dev mailing list, or your planning
representative (who you can contact via your PMC). I believe
is potential value in aligning your project's
schedule and leveraging the marketting effort behind the
even if it doesn't make any sense to include bits in the
aggregate p2 repository.
On 11/27/2013 06:08 AM, Ian Craggs wrote:
To Paho committers, Eclipse mentors,
for a while I've been thinking about what we need to do to
achieve a Release
of Paho. There seems to be a lot of information to absorb, but
seems we need to start here:
to formally create a release and a plan to go with it.
I was wondering what a release means for a non-Java component?
about Release Reviews
I can't see that any particular method of making the release
is dictated. What would it mean to be part of a Simultaneous
for a non-Java component?
Any thoughts, advice or pointers to useful information
Director of Open Source Projects, The
Learn about Eclipse
paho-dev mailing list
paho-dev mailing list