> I don't think its a good idea announce a specific day in advanced,
> which we wont make anyway.
>
A concrete date would be too specific. What's about a month?
Camel 2.9.5 -> Dez. 2012
Camel 2.10.4 -> Jan. 2013
Camel 2.11.0 -> Jan. 2013
We have some conceivabilities about the next release dates.
On Nov 23, 2012, at 2:16 AM, Claus Ibsen wrote:
> On Thu, Nov 22, 2012 at 10:24 PM, Christian Müller
> wrote:
> The advantage for me to have a new minor release every 3 - 4 month is:
>> - the earlier availability of changes which are not backwards compatible.
>> But to be honest, I don't think
On Thu, Nov 22, 2012 at 10:24 PM, Christian Müller
wrote:
> I suppose we have a silence consensus here to announce the releases in
> advance. So far so good...
>
Not really. I think people expressed that their favored more what we do now.
I am not really sure we have consensus.
Though I may have
I suppose we have a silence consensus here to announce the releases in
advance. So far so good...
The advantage for me to have a new minor release every 3 - 4 month is:
- the earlier availability of changes which are not backwards compatible.
But to be honest, I don't think we have much of them.
We did not try to release every 3 months after we started to issue patch
releases. I agree with Claus that what we have now is a better model,
and I prefer it as well.
That said, I agree the release cycle should be more predictable and
announced in advance. I like for instance the Ubuntu model
Hi
I think the current model is fine.
If you look at other projects they don't release minor releases more
quickly than we do.
Having the current scheduled with a patch release every 4-6 weeks is good.
Then bug fixes gets into a stable branch in timely manner, and allow
people to upgrade easily (
I really like the idea of having major releases more often. It makes transition
between releases faster and easier, even for users.
There was a talk few months ago about git usage in camel (instead of svn) few
months ago:
http://camel.465427.n5.nabble.com/DISCUSS-force-switching-from-SVN-to-GIT-
What's your opinion about determining our next Camel release dates in JIRA
in advance?
I think this could help us to synchronize our planning (from each
committer). It will also help us to work more in the RERO (release early -
release often) mode because it makes it more difficult to miss a releas
