cancel
Showing results for 
Search instead for 
Did you mean: 

Alfresco 2.9C release date

hvyas
Champ in-the-making
Champ in-the-making
Is there any set date/time frame for Alfresco 2.9C release?
Will there be any changes related to the Kofax integration part?
Any input would be appreciated.
8 REPLIES 8

hbf
Champ on-the-rise
Champ on-the-rise
Me, too, I am interested in this. Will there be a 2.9x commnunity release at all or will we see 3.0 community right away?

I am asking because I am using SVN r1676 and would like to hop onto an "official" commnunity release again. (Right now, SVN trunk is at 3.0 and I don't dare to update to this…)

Thanks,
Kaspar

mikeh
Star Contributor
Star Contributor
As I understand it, the current plan is to release v2.9 Community Final in June.

Thanks,
Mike

hbf
Champ on-the-rise
Champ on-the-rise
Great. Thanks a lot for the info, Mike.

ftoth
Champ in-the-making
Champ in-the-making
Kaspar,

I am using SVN r1676

What's the significance of r1676? You may have seen my recent posts
about whether or not 2.9b is production-ready or if I should stick with
2.1. I've also been asking about the rev number for 2.9b in case I
need the source.

Thanks,

Fred

hvyas
Champ in-the-making
Champ in-the-making
This would not be an issue if Alfresco people allow bug fix releases for community without support like other open source project do instead of community release that contains mixture of bug fixes and upcoming features, makes it hard to use in production.

hbf
Champ on-the-rise
Champ on-the-rise
I agree: it is not at all easy to use the SVN HEAD code as it contains – as you say – a mixture of bug fixes and new features.

I very much hope that 2.9C will, however, correspond to a particular SVN revision (in a branch or whatever)!

If community release do not correspond to fixed SVN revisions, working with the SVN code is really hard: you can never hop onto a "stable" version anymore!

ftoth
Champ in-the-making
Champ in-the-making
Plus, we are all finding the same bugs over and over. Many times I find
a bug in 2.1 community, spend lots of time researching it, only to find out
it's fixed in some later enterprise version.

I've resorted to applying my own patches to 2.1 because there is no other viable choice.

How nice for Alfresco to have community users find these bugs so that the
enterprise users can reap the benefit.

Fred

hvyas
Champ in-the-making
Champ in-the-making
It may be their business strategy to force people to consider enterprise but in my opinion this would discourage the use. I am pretty sure Alfresco would like to rule the ECM space, but I just don’t believe that would happen with such a “restrictive open source” approach. 

One of the major strength of the open source software is the community who contributes and uses/recommends the open source software. For instance when a consultant like me recommends open source software to the organization, I am indirectly acting as a marketing person for that software. Some Organizations will pay for the support and some just don’t but in any case they will use the software thus increase the exposure (which is I think the most important aspect). I just don’t think I can do that with the current Alfresco policy for the community software.