Ok ...
So, if I understand there is no clear (or followed) rules for now...
I agree, we have to keep module versionning different from Shinken versionning.
I think starting module versionning from 1.4, could be more confusing with
shinken version than starting from 1.0 (Shinken 1.0 is very old ... Nobody use
it today...)
Also, if I understand, you think that a lot of users will never look which
version they are using, so they are not a problem here => I agree
If some poweruser/packager have questions they can understand alone (A quick
read of package.json then all it's clear) or we can also help them to
understand.
But, I don't really care about which way we will follow.
I just want a clear decision which will be written somewhere. I really think we
need to write something to guide devs and users (Tags/versions are mandatory to
report bugs).
After, my next question is :
What can I do for help ?
- I can create a tag 1.0 on each module and adapt package.json if needed
Or
- I can create a tag 1.4 on each module and adapt package.json if needed
Then push all of this (first) new versions on shinken.io if needed
- An other idea ?
Also, maybe shinken.io should display the commit hash/revision used for the
tarball (I don't know if this is possible...)
What do you think about ?
And thanks for all your answers !!!
--
Sent from my Nokia N950
On 22/04/14 10:22 nap wrote:
On Tue, Apr 22, 2014 at 2:53 PM, Sébastien Coavoux <s.coav...@free.fr> wrote:
True, but people will asked if the 1.0 means "first prod for this module", or
"was the module from the 1.0 shinken version". With starting by 1.4 there is no
more problem with this :)
I disagree : there is already a dependency variable that specifies shinken
>=1.4 so the version variable is not realted to shinken IMO. See
https://github.com/shinken-monitoring/mod-webui/blob/master/package.json
It depends on the shinken core version >= 1.4, but its not used currently (as
we only got one version :) ). I don't see the conflict there in fact. it's not
a problem to put 1.0 for webui, it's just that the user/packager will ask if
it's related to the 1.0 of shinken (so an old version) or 1.4.
I think 1.0 or 1.4 version is just a detail, as LOT of users will never ever
look at it, and we can just put it on a webui page (like to ask user its
version for a bug report). Let's stick with the actual 1.0 version, it's
already done and I think Anread prefer to take time to code than re-version a
tag :)
Jean
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
