Camelot versions?

[Lionel Roubeyrie]

Hi all,

is it possible to have a little explanation about Camelot releases and versions, as in the "Get It" section of the website there's 3 ways to install it but it's hard to understand.

For now, we can get Camelot from :

- the python package index where the last update is at 2012-06-29. Normally it's a stable and fixed version,

- gitorious, where the master branch get commits every days but Camelot's version is 2012.06.29, and the stable banch is also 2012.06.29

- github, just a gitorious clone with the same versions mixes

I understand you use the stable release date as the Camelot version and if you don't have a next planned date you can't set a version in the master branch, but when we switch to differents camelot versions (stable is great but some bugs remain) is sometimes hard to find where we are (and to remind if we need Elixir or not).

Thanks

[Jeroen Dierckx]

Hi Lionel,

Since Erik is on holiday, i'll try to answer this. He can
correct/complete later on.

We make a lot of effort to keep the master branch as "stable" as
possible. We use the master in our own commercial projects.

A release is made from master when we feel that enough changes
(features, improvements, rewrites, ...) warrant one. That's basically
the reason why the current release is somewhat old; we believe that
Camelot is pretty feature complete at the moment. I guess the most
prolific change that has been done in the meantime, is switch from
Elixir to Declarative (the no-elixir branch was merged into master
late last year). We are still thoroughly testing this, because there
are a lot of subtile differences, Declarative is mainly more strict,
so we want to cover everything. When this process has run its course,
a new release will probably be made.
We are a very small team (development is mainly done by Erik himself),
so we tend not to predict/announce upcoming releases due to very busy
schedules. We already have enough pressure from other aspects of life
;). By the way, contributions are of course very welcome, that's one
of the main reasons Camelot is open source.

We are indeed on Gitorious at the moment, with a mirror on Github,
simply to reach more people. Git is still an experiment for us; We
mainly use Mercurial and Bitbucket for other projects, and might move
Camelot to Bitbucket as well, though nothing has been decided yet.

Bottom line, i think using master is fairly safe, but stable is stable
of course, it should be free of major bugs, you at least know what you
get.

I hope this makes it clear for you.
We always remain open to suggestions of course.

Best regards,
Jeroen

> --
> --
> You received this message because you are subscribed to the "Project
> Camelot" group.
> Visit www.python-camelot.com for more information
>
> To post to this group, send email to project...@googlegroups.com
> To unsubscribe from this group, send email to
> project-camel...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/project-camelot?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Project Camelot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to project-camel...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Lionel Roubeyrie]

Ok, thanks Jeroen for the clarifications