Hi Serge,
good morning from the US ;)
I already changed the version to 1.0.0-incubating-SNAPSHOT.
I'm testing a build on my machine (and also preparing the Jenkins instance).
If it works fine (and I bet it will ;)), I will stage the release.
I keep you posted.
Thanks,
Regards
JB
On 12/07/2015 10:32 AM, Serge Huber wrote:
Ok it seems we have consensus. We will change the version down to
1.0.0-incubating-SNAPSHOT
JB would you have time to do this change and cut our first release ?
Do we have everything we need to do this ?
Let me know how I can help.
cheers,
Serge...
Serge Huber
CTO & Co-Founder
T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com <http://www.jahia.com/>
SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER
<https://twitter.com/sergehuber> | VCARD
<http://www.jahia.com/vcard/HuberSerge.vcf>
JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained and
to discover why Jahia is a leading User Experience Platform (UXP) for
Digital Transformation.
On Wed, Dec 2, 2015 at 10:35 AM, Jean-Baptiste Onofré <[email protected]>
wrote:
+1
I would be more than happy to apply the change and cut off the release.
Regards
JB
On 12/02/2015 10:27 AM, Serge Huber wrote:
Hi guys,
As we are getting closer to a first release (yeah !), I’d like to propose
something about the version number of Apache Unomi.
Currently it is at 2.0.0-incubating-SNAPSHOT, which was mostly to
differentiate from the 1.0.X version that we had outside of Apache, but I’m
thinking more and more this doesn’t make much sense from the Apache point
of view.
I’d like to propose that we go to 1.0.0-incubating-SNAPSHOT and therefore
our first release would be at 1.0.0-incubating. I’m not that found of 0.x
numbers, especially since in my company we consider the current code as
good enough for production environments, and I generally tend to think that
if something can be used in production it should have a “major” version
number.
However this does beg the question of how do we map the Unomi version
number to the CXS specification. As the specification is still evolving, I
propose that we do something similar to what Apache Tomcat has done and
provide a version mapping page such as this one :
https://tomcat.apache.org/whichversion.html and that we can then freely
perform releases of working and useful code and still map it to the spec as
we want.
What do you think ?
Best regards,
Serge…
ps : lazy consensus will apply here :)
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
