Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Release Planning for Paho - thoughts?

David, Wayne,

thanks for your thoughts.

No, we've not had any releases yet.  But in my opinion, the Java, C and _javascript_ clients are ready for production use, and I would 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 the basics for the mechanics ... or, given the links that do.

But will add my high level thoughts ...

Given the "age" of the project, I'd say a release was in order. (You've not had any, yet, right?)

But, that should be balanced with the "need" for one. One thing that characterizes a "release" is that it becomes relatively permeant, and to some degree (of your choice, mostly, driven by your adopters) maintenance releases would follow that .... 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 more than a "milestone" or "checkpoint" build ... which we typically advise people to never use those production.

I'm assuming this would still be an "incubating" release? Sorry I've not kept closer track, but assuming you've been having regular "milestone" and/or "integration" builds ... and assuming you've been getting good bug reports from "adopters" then I'd think a release (even if incubating) would be good. If you are not getting much "adopter use" yet and/or have a ways to go before being "usable in production" then that might be reason to consider it more carefully, as it would not serve much purpose and might give the wrong impression.

All that said, I'm happy to answer more specific questions and/or "catch up" with the project to give more specific advice, if you head in that direction.

Thanks, and good luck!

From:        Wayne Beaton <wayne@xxxxxxxxxxx>
To:        Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>, General development discussions for paho project <paho-dev@xxxxxxxxxxx>,
Date:        11/27/2013 02:36 PM
Subject:        Re: [paho-dev] Release Planning for Paho - thoughts?
Sent by:        paho-dev-bounces@xxxxxxxxxxx

Are the mentors subscribed to the dev list? It might be a good idea to reach out to them to make sure they are (we don't set this up automagically).

For releases, start here:

That will take you to here:

which will encourage you to use the project page to enter release information on the project page.

There's loads more information here (but start with the "release cycle" page above).

Other than the checklist, I believe that most of the review requirements are language and technology agnostic. The checklist on the "Release Reviews" page does reflect our "mostly Java" heritage. I'll have to take a pass at it with language generalization in mind. In the meantime, if something just doesn't make sense for Paho, use your best judgement to either ignore the item or adapt to your situation.

In terms of simultaneous release participation, that might be a good question for the cross-project-issues-dev mailing list, or your planning council representative (who you can contact via your PMC). I believe that there is potential value in aligning your project's development/milestone delivery schedule and leveraging the marketting effort behind the simultaneous release, 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 it 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? Reading about Release Reviews

I can't see that any particular method of making the release available is dictated.  What would it mean to be part of a Simultaneous Release for a non-Java component?

Any thoughts, advice or pointers to useful information appreciated.



Wayne Beaton
Director of Open Source Projects,
The Eclipse Foundation
Learn about
Eclipse Projects
EclipseCon 2014_______________________________________________
paho-dev mailing list

paho-dev mailing list

Back to the top