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?

[Edited excerpts of email back to dev-list]

> David,
> thanks for the quick response again.
> Some of the components aren't as ready as others, and I personally
> wouldn't have added them to the download list yet.  I see what you
> mean about binary download availability though, and we definitely
> need to fix that.

Sounds right .... you may just need a way to indicate which are planned for Luna,
and which are not.

> We haven't been keeping up older builds because generally the newest
> is definitely the best.  Some of the older Hudson builds are kept in
> the Hudson workspace.  Currently the output from the C build is put here:
>, but again, it's only the
> latest one.  We could change that to keep history.

One reason to "keep history", is that, as you mature, you may find you have
adopters that are using/testing an "old" version (say, with their own
internal client ... or "value add client") and they may well be planning to "move up" to the new version
at some point, but they might not be ready yet, and may still need the older
version for a few weeks/months ... eventually years! :\

That's what we mean by asking projects to have a "retention policy", so
adopters know what to expect.

> For unit test results, where are you expecting to find them?  They
> are in the Hudson build history, like here for the C client:

I'm not sure. Definitely something simple and easy for you. And something "near" the downloadable binary or artifacts.  

And fine if they temporarily "point back" to Hudson ... but eventually you'll want them on "downloads".
("downloads" is actually "backed up", made for heavy use, etc., whereas Hudson, even if you mark something as "keep this build" is not backed up and those "keep forever" builds will disappear some day -- such as after a disk crash, Hudson upgrade, or something :)

Perhaps a short summary, that "linked" to the more detailed, specific results ... such as

(31 of 31 tests passed) --> which would link to ""

and once you actually "promoted" an "M4 version" just the link would change (I'm assuming) to something like

(31 of 31 tests passed) --> which would link to ""

after you "copied up" the artifacts and results to "downloads". (And, if not obvious, see how I point to specific build, "103", not "latest").

> All the C client builds are dynamically linked with external libraries.

Sounds like you are on top of it all.

Hope this helps.

Back to the top