Hi,
On Thu, Apr 24, 2014 at 7:08 AM, <titilamb...@titilambert.org> wrote:
> Ok ...
>
> So, if I understand there is no clear (or followed) rules for now...
>
There is just one: "it's up to the maintainer". I don't think I need to
take their hand and explain them how they need to tag their repo or
package, it's their job :)
>
> 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...)
>
I saw a 0.6 version in production yesterday on a big french company ;)
> 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).
>
Ok clear: maintainer decide what they prefer for their own package. For my
packages I'll keep the rule:
* if code didn't changed: 1.4
* if we update the code (like lately mongodb retention) : => 2.0
but it's just for my own package and feel free to take this for yours. But
I repeat: there is no rule and it's far better like this. Shinken.io is
done to not depend on me or way for my direction. I think coders are smart
enough to take their decision on the way their name their packages and
versions, and it's ok like that. The less rules there are, the better it
will be.
>
> 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 ?
>
You can review the repo if you want and propose version update for my own
package, but feel free to directly fix your own and publish them.
>
> Also, maybe shinken.io should display the commit hash/revision used for
> the tarball (I don't know if this is possible...)
>
shinken.io is not done for this and is only designed to work for the
shinken cli currently. Adding hash or commit is only useful for packagers
and I think it's better to rely on the source for them, not on
shinken.iothat is only designed for users.
>
> What do you think about ?
>
Here it is :)
>
> And thanks for all your answers !!!
>
>
> --
>
>
>
> Sent from my Nokia N950
>
Such a long mail with a "phone"? Congrats :)
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
