Hi Everybody,
From my point of view, we should have a separate versioning for each module or
packet. And all versions should based on a simple semantic versioning ->
http://semver.org/
For example: The WebUI
The WebUI is now tagged and available as WebUI 1.0, the *first* stable version
for the production environment. But we have also 1.1.0-dev.X releases, based on
the WebUI roadmap for extra features.
Technically we should tag all packages as "1.0" with a creation date Jul 30,
2013. Because it is a first official release as stand-alone module or packet.
The way I see it, there is no reason why we have a modules etc. without a Git
tag and a 1.4 version on shinken.io.
> Am 22.04.2014 um 09:27 schrieb nap <napar...@gmail.com>:
>
>
>> On Mon, Apr 21, 2014 at 8:56 PM, Thibault Cohen
>> <titilamb...@titilambert.org> wrote:
>> Hello everyone !
>>
>> I'm currently packaging Shinken 2.0.1 for Debian and this is practically
>> done ! (I just have to fix some lintian errors ...)
>> I'm also working on module packages. And I have a problem concerning module
>> tarball and version.
>> I'm not sure which tarball I have to use (github/shinken.io (I think use
>> shinken.io)) and I don't know which version I have to use.
>> For example, the WebUI :
>> On github master branch (version 1.1 dev), I see version 1.0
>> (https://github.com/shinken-monitoring/mod-webui/blob/master/package.json)
>> On github 1.0 tag, I see version 1.4
>> (https://github.com/shinken-monitoring/mod-webui/blob/1.0/package.json)
>> On ShinkenIO, I see version 1.4 (http://shinken.io/package/webui)
>>
>> Was the "1.4" for the Shinken 1.4 version ? If yes, the "version" attributes
>> is false, isn't it ?
>> Do we have to add a tag in ALL Shinken modules repos ?
>>
>> Maybe we could define/write something about all of this ?
>> This could be helpfull for users and developpers...
>>
>> So, do you have any ideas/points to make things more clear ?
>>
>> Thanks !
>
> Users will stick to shinken.io, but it's a problem for packagers, especially
> with the auto-uri check.
>
> I asked to change the version number on the 1.4+ way on the webui repo so it'
> easier to understand, I hope Andreas saw it :)
>
> For the global rule, even if I'm not a big fan of modules as packages,
> because it in the end it will conflicts with the shinken.io role, use repo
> tags. The rule in shinken.io is "publish the lastest stable", but version tag
> is up to the repo maintener :)
>
>
> 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
------------------------------------------------------------------------------
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
