FWIW I quite like your suggestion below about the Firefox style. It's
enough of a change getting rid of the 0. part to signal
maturity, but it essentially follows the existing convention, so is
unlikely to be too confusing to anyone (plus it looks less weird :-))
Can someone remind me what the perceived compelling advantage of a date
based system was? From what I see in general about products date based
approaches appear quite rare the only big one I can think of was
Microsoft Windows and Office, but MS have ditched dates in favour of
numbers too.
So +1 from me for Justin's new suggestion (and sorry for bringing this
up again I'm afraid I saw 15.02 and went, eeewww)
Frase
On 19/01/15 19:30, Justin Ross wrote:
We can still change it. I know Robbie isn't sold either, and I'm open to
the alternative we discussed: 3.1, 3.2, 3.3, etc.
I should note that while I think the date-based approach is reasonable,
it's not a good fit for a pure-API module such as qpid-proton or qpid-jms.
There I think you want the major number to signal the presence or absence
of big API changes.
Since it wasn't mentioned before: I also like 31, 32, 33 for Qpid C++ and
similar. It's the style that Firefox uses, and I think it does a slightly
better job of representing the pace and lifecycle of some of our
components. Stated negatively, it avoids the major number becoming
arbitrary--more marketing than substance.
In summary, my preference:
Pure API modules such as qpid-jms, -proton: 0.1, 0.2, 1.0, 1.1, 2.0, 2.1,
etc.
Servers, tools, test suites: 31, 32, 33, 33.1, etc.
Justin
On Mon, Jan 19, 2015 at 2:03 PM, Fraser Adams <fraser.ad...@blueyonder.co.uk
wrote:
I know this has been discussed previously, but looking at "15.02" in the
cold hard light of day just looks, well, weird to my eyes :-(
Perhaps it's just 'cause it's new and I'm not used to seeing versions like
that, but I have to be honest, I'm still not sold. I know there's reasons
for the change etc. etc. but I can't quite mentally gel with it :-( Oh well
I guess I'll just have to get used to it.
Frase
On 19/01/15 12:22, Justin Ross wrote:
Hi, everyone. I've begun the process to release the C++ and Python
components. You can see more details at the release pages:
https://cwiki.apache.org/confluence/display/qpid/Qpid+Cpp+15.02
https://cwiki.apache.org/confluence/display/qpid/Qpid+Python+15.02
Alpha is set for the 28th of this month, and Beta (and release branching)
will follow two weeks after that. Remember to complete major work by the
Alpha deadline so we can test the build and distribution metadata.
I've made an initial pass and found some failures:
http://people.apache.org/~jross/qpid-cpp-20150116/
Proton ABI change causes build failure:
http://people.apache.org/~jross/qpid-cpp-20150116/cpp-test.out
http://people.apache.org/~jross/qpid-python-20150116/
Tools install failure:
http://people.apache.org/~jross/qpid-cpp-20150116/tools-test.out
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
