You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by Serge Huber <sh...@jahia.com> on 2015/12/02 10:27:44 UTC
Talking about versions
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 :)
Re: Talking about versions
Posted by Christophe Laprun <cl...@jahia.com>.
+1 on 1.0.0-incubating-SNAPSHOT. Version mapping seems also the way to go.
> On 02 Dec 2015, at 10:27, Serge Huber <sh...@jahia.com> 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 :)
Christophe Laprun
Senior Software Engineer
8 rue du Sentier | 75002 Paris | France
jahia.com <http://www.jahia.com/>
SKYPE <skype:chris.laprun?add> | LINKEDIN <https://www.linkedin.com/in/chrislaprun> | TWITTER <https://twitter.com/metacosm> | VCARD <http://www.jahia.com/vcard/LaprunChristophe.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.
Re: Talking about versions
Posted by Serge Huber <sh...@jahia.com>.
Hello JB,
Good evening here from Europe :)
Thanks a lot for helping with all this JB ! I saw that you changed the version number already. Once you have the release staged let me know I’ll check it out.
For Jenkins I believe I have an account on it already but possibly not enough access ?
cheers,
Serge…
> On 7 déc. 2015, at 17:40, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> 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://jahia.com/> <http://www.jahia.com/ <http://www.jahia.com/>>
>> SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber <https://www.linkedin.com/in/sergehuber>> | TWITTER
>> <https://twitter.com/sergehuber <https://twitter.com/sergehuber>> | VCARD
>> <http://www.jahia.com/vcard/HuberSerge.vcf <http://www.jahia.com/vcard/HuberSerge.vcf>>
>>
>>
>>> JOIN OUR COMMUNITY <http://www.jahia.com/ <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é <jb...@nanthrax.net>
>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net <http://blog.nanthrax.net/>
> Talend - http://www.talend.com <http://www.talend.com/>
Re: Talking about versions
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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é <jb...@nanthrax.net>
> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Talking about versions
Posted by Serge Huber <sh...@jahia.com>.
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é <jb...@nanthrax.net>
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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Talking about versions
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Using Unomi (was Re: Talking about versions)
Posted by Serge Huber <sh...@jahia.com>.
Maybe my presentation from ApacheCon can help ?
You can check it out here :
https://www.youtube.com/watch?v=y4uNwnVMVyg
Also I did a presentation where I integrate iOS and tvOS platforms at JavaOne here :
https://www.youtube.com/watch?v=RdY_F_YUn6M
cheers,
Serge…
> On 2 déc. 2015, at 11:48, Wentao Liu <wl...@welikecloud.com> wrote:
>
> Thanks for showing me the deployment method.
>
> I did the svn checkout and use the command
>
>> mvn clean install -P generate-package
>
> To get a build release then deployed into an existing Karaf server in stand-alone mode, it works.
>
> But need sometime to learn integration algorithm and event driven data processing.
>
>
> Sent from my iPad
>
>> On 02 Dec 2015, at 18:37, Serge Huber <sh...@jahia.com> wrote:
>>
>>
>>> On 2 déc. 2015, at 11:23, Wentao Liu <wl...@welikecloud.com> wrote:
>>>
>>> Hello Serge,
>>>
>>> Thanks for the response.
>>> First of all, I need set up the UNOMI server and get it running!
>>
>> Should be rather simple. We are working on building a release, but in the mean time you can simply checkout the code, build using the following command :
>>
>> mvn clean install -P generate-package
>>
>> and you should have the generated packages in
>>
>> package/target
>>
>> Simply deploy one of them and then launch using :
>>
>> bin/karaf
>>
>>> Generally, I need integrate data collecting code with web pages to collect user access data. Bases on this, I need design a UI to show user profiles. After this, we can try to sell the product to customers to help them analyze user behaviors and do online sales promotion. Probably need use Hadoop or other big data platforms as data process engine.
>>
>> BigData and algorithms integration is something we are looking at in both the standard at OASIS (CXS) and here. The idea is that the internal events sent to Unomi could then serve as input to BigData systems such as Hadoop or Apache Spark.
>>
>>> Glad to know you can accept my documents:) once I have more, will send you to review.
>>
>> Sure thing. The more we have the better.
>>
>> Best regards,
>> Serge…
>>
Re: Using Unomi (was Re: Talking about versions)
Posted by Wentao Liu <wl...@welikecloud.com>.
Thanks for showing me the deployment method.
I did the svn checkout and use the command
> mvn clean install -P generate-package
To get a build release then deployed into an existing Karaf server in stand-alone mode, it works.
But need sometime to learn integration algorithm and event driven data processing.
Sent from my iPad
> On 02 Dec 2015, at 18:37, Serge Huber <sh...@jahia.com> wrote:
>
>
>> On 2 déc. 2015, at 11:23, Wentao Liu <wl...@welikecloud.com> wrote:
>>
>> Hello Serge,
>>
>> Thanks for the response.
>> First of all, I need set up the UNOMI server and get it running!
>
> Should be rather simple. We are working on building a release, but in the mean time you can simply checkout the code, build using the following command :
>
> mvn clean install -P generate-package
>
> and you should have the generated packages in
>
> package/target
>
> Simply deploy one of them and then launch using :
>
> bin/karaf
>
>> Generally, I need integrate data collecting code with web pages to collect user access data. Bases on this, I need design a UI to show user profiles. After this, we can try to sell the product to customers to help them analyze user behaviors and do online sales promotion. Probably need use Hadoop or other big data platforms as data process engine.
>
> BigData and algorithms integration is something we are looking at in both the standard at OASIS (CXS) and here. The idea is that the internal events sent to Unomi could then serve as input to BigData systems such as Hadoop or Apache Spark.
>
>> Glad to know you can accept my documents:) once I have more, will send you to review.
>
> Sure thing. The more we have the better.
>
> Best regards,
> Serge…
>
Using Unomi (was Re: Talking about versions)
Posted by Serge Huber <sh...@jahia.com>.
> On 2 déc. 2015, at 11:23, Wentao Liu <wl...@welikecloud.com> wrote:
>
> Hello Serge,
>
> Thanks for the response.
> First of all, I need set up the UNOMI server and get it running!
Should be rather simple. We are working on building a release, but in the mean time you can simply checkout the code, build using the following command :
mvn clean install -P generate-package
and you should have the generated packages in
package/target
Simply deploy one of them and then launch using :
bin/karaf
> Generally, I need integrate data collecting code with web pages to collect user access data. Bases on this, I need design a UI to show user profiles. After this, we can try to sell the product to customers to help them analyze user behaviors and do online sales promotion. Probably need use Hadoop or other big data platforms as data process engine.
BigData and algorithms integration is something we are looking at in both the standard at OASIS (CXS) and here. The idea is that the internal events sent to Unomi could then serve as input to BigData systems such as Hadoop or Apache Spark.
> Glad to know you can accept my documents:) once I have more, will send you to review.
Sure thing. The more we have the better.
Best regards,
Serge…
Re: Talking about versions
Posted by Wentao Liu <wl...@welikecloud.com>.
Hello Serge,
Thanks for the response.
First of all, I need set up the UNOMI server and get it running!
Generally, I need integrate data collecting code with web pages to collect user access data. Bases on this, I need design a UI to show user profiles. After this, we can try to sell the product to customers to help them analyze user behaviors and do online sales promotion. Probably need use Hadoop or other big data platforms as data process engine.
Glad to know you can accept my documents:) once I have more, will send you to review.
Thanks,
Wentao
Sent from my iPad
> On 02 Dec 2015, at 18:02, Serge Huber <sh...@jahia.com> wrote:
>
>
> Hello Wentao,
>
> Sounds interesting can you tell us more about what you’re trying to achieve ?
>
> Also don’t hesitate to contribute any documentation you might produce while learning, and of course don’t hesitate to ask questions, we need to get this community jump-started :)
>
> cheers,
> Serge…
>
>> On 2 déc. 2015, at 10:58, Wentao Liu <wl...@welikecloud.com> wrote:
>>
>> +1. Mapping version number to CXS spec is a good idea. I am still in the learning process and hope can bring
>> UNOMI to China as a product. UI end needs build on server end, I think.
>>
>> Thanks,
>>
>> Wentao
>>
>> Sent from my iPad
>>
>>> On 02 Dec 2015, at 17:36, Abdelkader Midani <amidani@jahia.com <ma...@jahia.com>> wrote:
>>>
>>> +1 for 1.0.0-incubating-SNAPSHOT
>>>
>>> is incubating needed (is an Apache requirements) ?
>>>
>>> 1.0.0-SNAPSHOT would be more sexy
>>> Cordialement / Best regards
>>>
>>> Abdelkader Midani
>>> Senior Software Engineer
>>>
>>> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
>>> 8 rue du Sentier | 75002 Paris | France
>>> jahia.com <http://www.jahia.com/>
>>> SKYPE <skype:abdelkader.midani?add> | TWITTER <https://twitter.com/M_Abdel> | VCARD <http://www.jahia.com/vcard/MidaniAbdelkader.vcf>
>>>
>>> <unknown.png>
>>>
>>>> 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 2 Dec 2015, at 10:27, Serge Huber <shuber@jahia.com <ma...@jahia.com>> 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 <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 :)
>> <unknown.png>
>
>
Re: Talking about versions
Posted by Serge Huber <sh...@jahia.com>.
Hello Wentao,
Sounds interesting can you tell us more about what you’re trying to achieve ?
Also don’t hesitate to contribute any documentation you might produce while learning, and of course don’t hesitate to ask questions, we need to get this community jump-started :)
cheers,
Serge…
> On 2 déc. 2015, at 10:58, Wentao Liu <wl...@welikecloud.com> wrote:
>
> +1. Mapping version number to CXS spec is a good idea. I am still in the learning process and hope can bring
> UNOMI to China as a product. UI end needs build on server end, I think.
>
> Thanks,
>
> Wentao
>
> Sent from my iPad
>
> On 02 Dec 2015, at 17:36, Abdelkader Midani <amidani@jahia.com <ma...@jahia.com>> wrote:
>
>> +1 for 1.0.0-incubating-SNAPSHOT
>>
>> is incubating needed (is an Apache requirements) ?
>>
>> 1.0.0-SNAPSHOT would be more sexy
>> Cordialement / Best regards
>>
>> Abdelkader Midani
>> Senior Software Engineer
>>
>> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
>> 8 rue du Sentier | 75002 Paris | France
>> jahia.com <http://www.jahia.com/>
>> SKYPE <skype:abdelkader.midani?add> | TWITTER <https://twitter.com/M_Abdel> | VCARD <http://www.jahia.com/vcard/MidaniAbdelkader.vcf>
>>
>> <unknown.png>
>>
>> > 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 2 Dec 2015, at 10:27, Serge Huber <shuber@jahia.com <ma...@jahia.com>> 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 <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 :)
>>
> <unknown.png>
Re: Talking about versions
Posted by Wentao Liu <wl...@welikecloud.com>.
+1. Mapping version number to CXS spec is a good idea. I am still in the learning process and hope can bring
UNOMI to China as a product. UI end needs build on server end, I think.
Thanks,
Wentao
Sent from my iPad
> On 02 Dec 2015, at 17:36, Abdelkader Midani <am...@jahia.com> wrote:
>
> +1 for 1.0.0-incubating-SNAPSHOT
>
> is incubating needed (is an Apache requirements) ?
>
> 1.0.0-SNAPSHOT would be more sexy
> Cordialement / Best regards
>
> Abdelkader Midani
> Senior Software Engineer
>
> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
> 8 rue du Sentier | 75002 Paris | France
> jahia.com
> SKYPE | TWITTER | VCARD
>
> <unknown.png>
>
> > JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is a leading User Experience Platform (UXP) for Digital Transformation.
>
>> On 2 Dec 2015, at 10:27, Serge Huber <sh...@jahia.com> 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 :)
>
Re: Talking about versions
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
You're welcome ;)
Regards
JB
On 12/02/2015 10:53 AM, Abdelkader Midani wrote:
> Hi Jean-Baptiste,
>
> Thanks, it makes more sense for me
>
>
> Cordialement / Best regards
>
>
> Abdelkader Midani
> Senior Software Engineer
>
> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
> 8 rue du Sentier | 75002 Paris | France
> jahia.com <http://www.jahia.com/>
> SKYPE <skype:abdelkader.midani?add> | TWITTER
> <https://twitter.com/M_Abdel> | VCARD
> <http://www.jahia.com/vcard/MidaniAbdelkader.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 2 Dec 2015, at 10:50, Jean-Baptiste Onofré <jb@nanthrax.net
>> <ma...@nanthrax.net>> wrote:
>>
>> Hi Abdelkader,
>>
>> yes, it's an Apache requirement: as we are in incubator podling, the
>> release version has to contain *incubating* to indicate we are in the
>> incubator.
>>
>> Regards
>> JB
>>
>> On 12/02/2015 10:36 AM, Abdelkader Midani wrote:
>>> +1 for 1.0.0-incubating-SNAPSHOT
>>>
>>> is incubating needed (is an Apache requirements) ?
>>>
>>> 1.0.0-SNAPSHOT would be more sexy
>>>
>>>
>>> Cordialement / Best regards
>>>
>>>
>>> Abdelkader Midani
>>> Senior Software Engineer
>>>
>>> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
>>> 8 rue du Sentier | 75002 Paris | France
>>> jahia.com <http://jahia.com> <http://www.jahia.com/>
>>> SKYPE <skype:abdelkader.midani?add> | TWITTER
>>> <https://twitter.com/M_Abdel> | VCARD
>>> <http://www.jahia.com/vcard/MidaniAbdelkader.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 2 Dec 2015, at 10:27, Serge Huber <shuber@jahia.com
>>>> <ma...@jahia.com>
>>>> <ma...@jahia.com>> 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é
>> jbonofre@apache.org <ma...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Talking about versions
Posted by Abdelkader Midani <am...@jahia.com>.
Hi Jean-Baptiste,
Thanks, it makes more sense for me
Cordialement / Best regards
Abdelkader Midani
Senior Software Engineer
T +33 1 44 79 37 99 | M +33 6 72 57 93 40
8 rue du Sentier | 75002 Paris | France
jahia.com <http://www.jahia.com/>
SKYPE <skype:abdelkader.midani?add> | TWITTER <https://twitter.com/M_Abdel> | VCARD <http://www.jahia.com/vcard/MidaniAbdelkader.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 2 Dec 2015, at 10:50, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi Abdelkader,
>
> yes, it's an Apache requirement: as we are in incubator podling, the release version has to contain *incubating* to indicate we are in the incubator.
>
> Regards
> JB
>
> On 12/02/2015 10:36 AM, Abdelkader Midani wrote:
>> +1 for 1.0.0-incubating-SNAPSHOT
>>
>> is incubating needed (is an Apache requirements) ?
>>
>> 1.0.0-SNAPSHOT would be more sexy
>>
>>
>> Cordialement / Best regards
>>
>>
>> Abdelkader Midani
>> Senior Software Engineer
>>
>> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
>> 8 rue du Sentier | 75002 Paris | France
>> jahia.com <http://www.jahia.com/>
>> SKYPE <skype:abdelkader.midani?add> | TWITTER
>> <https://twitter.com/M_Abdel> | VCARD
>> <http://www.jahia.com/vcard/MidaniAbdelkader.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 2 Dec 2015, at 10:27, Serge Huber <shuber@jahia.com
>>> <ma...@jahia.com>> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: Talking about versions
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Abdelkader,
yes, it's an Apache requirement: as we are in incubator podling, the
release version has to contain *incubating* to indicate we are in the
incubator.
Regards
JB
On 12/02/2015 10:36 AM, Abdelkader Midani wrote:
> +1 for 1.0.0-incubating-SNAPSHOT
>
> is incubating needed (is an Apache requirements) ?
>
> 1.0.0-SNAPSHOT would be more sexy
>
>
> Cordialement / Best regards
>
>
> Abdelkader Midani
> Senior Software Engineer
>
> T +33 1 44 79 37 99 | M +33 6 72 57 93 40
> 8 rue du Sentier | 75002 Paris | France
> jahia.com <http://www.jahia.com/>
> SKYPE <skype:abdelkader.midani?add> | TWITTER
> <https://twitter.com/M_Abdel> | VCARD
> <http://www.jahia.com/vcard/MidaniAbdelkader.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 2 Dec 2015, at 10:27, Serge Huber <shuber@jahia.com
>> <ma...@jahia.com>> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Talking about versions
Posted by Abdelkader Midani <am...@jahia.com>.
+1 for 1.0.0-incubating-SNAPSHOT
is incubating needed (is an Apache requirements) ?
1.0.0-SNAPSHOT would be more sexy
Cordialement / Best regards
Abdelkader Midani
Senior Software Engineer
T +33 1 44 79 37 99 | M +33 6 72 57 93 40
8 rue du Sentier | 75002 Paris | France
jahia.com <http://www.jahia.com/>
SKYPE <skype:abdelkader.midani?add> | TWITTER <https://twitter.com/M_Abdel> | VCARD <http://www.jahia.com/vcard/MidaniAbdelkader.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 2 Dec 2015, at 10:27, Serge Huber <sh...@jahia.com> 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 :)