On Tue, Apr 22, 2014 at 11:17 AM, Frescha <fres...@unitedseed.de> wrote:
>
> 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.
>
>
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 :)
But in the end users that will just "shinken install webui" don't have to
know which version they are using, they know it' the latest stable.
It's just about packagers and maintainers here, and so if we are all ok for
going to "1.0" for webui it's ok after all, especially the tags are already
done :p
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
