cancel
Showing results for 
Search instead for 
Did you mean: 

Enterprise version

uf766086
Champ in-the-making
Champ in-the-making
Hi all!!

Maybe I'm a bit disoriented but I cannot find the way to checkout Alfresco Enterprise source code. Is it possible?? Or the only Open Source versión it's Community version?

Thx in advance
16 REPLIES 16

gavinc
Champ in-the-making
Champ in-the-making
You can only check out the community version from SVN.

uf766086
Champ in-the-making
Champ in-the-making
Ok, thanks. I thought all versions were Open Source, and Alfresco sells support, something similar to Liferay business model.

Any plan to open all the platform in near future?  :wink:

gavinc
Champ in-the-making
Champ in-the-making
The only way the enterprise edition is different is in bug fixes, the functionality and features are exactly the same, so by purchasing the enterprise edition you get a more fully tested, stable and QA'ed version plus all the services and support as you mention.

uf766086
Champ in-the-making
Champ in-the-making
Hi again,

So if the functionality is exactly the same this infoon the wiki should be wrong

Also, within Alfresco Workflow JavaScript, the following "root" objects are available:

1.4 Enterprise only:

person
    Node (type cmSmiley Tongueerson) representing the person who is executing the script.

userhome
    Node (type cm:folder) representing the home folder of the person who is executing the script.

On that paragraph it seems that some functionality is only available on Enterprise version.

Thx in advance

davidc
Star Contributor
Star Contributor
All the "root" objects are available in 2.0 community & enterprise.

I'll fix up the WIKI.

uf766086
Champ in-the-making
Champ in-the-making
Thx for the flash response

edgar
Champ in-the-making
Champ in-the-making
Hi Gavin,

The only way the enterprise edition is different is in bug fixes, the functionality and features are exactly the same

just to understand your license model better: are you saying that these bug fixes do not make it into the Community Edition? You seem to be saying that the functionality and features are the same in all versions, yet you only fix bugs in the commercial editions? So you guys will not have any bugs that impact functionality and features? 😉

What I can imagine that you guys would do is something like creating a separate branch in Subversion for the commercial Alfresco releases starting from the HEAD version (= the Community Edition) and do all the bug fixing on that branch. This branch would not be available for public usage in the Alfresco Subversion repository. And at some stage you guys would merge these bug fixes back onto the HEAD and thereby fixing these bugs in the Community Edition as well.

Am I close? Am I right in assuming that bug fixes would become available sooner to the commercial editions of Alfresco then for the Community Edition?

kevinr
Star Contributor
Star Contributor
What I can imagine that you guys would do is something like creating a separate branch in Subversion for the commercial Alfresco releases starting from the HEAD version (= the Community Edition) and do all the bug fixing on that branch. This branch would not be available for public usage in the Alfresco Subversion repository. And at some stage you guys would merge these bug fixes back onto the HEAD and thereby fixing these bugs in the Community Edition as well.

Am I close? Am I right in assuming that bug fixes would become available sooner to the commercial editions of Alfresco then for the Community Edition?

You are exactly right with your assumptions on how we perform the branch, bug fixing and merge back to Community HEAD - all bug fixes make it into the Community version at a later date.

Thanks,

Kevin

paulhh
Champ in-the-making
Champ in-the-making
There are also maintenance updates to the Enterprise releases, so if a significant issue is found, then we'll fix that on the Enterprise branch and make it available to support subscribers.  That keeps the Enterprise side stable while new stuff is happening in the Community code line.

Cheers
Paul.