Results 1 to 7 of 7

Thread: Code base for core modules

  1. #1
    salesagility's Avatar
    salesagility is offline Sugar Community Member
    Join Date
    Aug 2006
    Location
    UK
    Posts
    2,379

    Default Code base for core modules

    There's an interesting thread over at alfresco about the differences between the code base for the open source and proprietary versions of alfresco.

    The code bases between the two are different with the code base for the open source version deliberately left less stable than the paid for versions. This is an obvious strategy to drive people from open source to proprietary.

    I am VERY curious to discover if SugarCRM employs a similar strategy.

    Would anyone from the SugarCRM team like to answer this question:

    "Is the core code base for community edition modules such as accounts, contacts etc. the same as the code base for the same enterprise edition modules?"

    or

    "does SugarCRM do what Alfresco does and deliberately deploy less stable and more buggy community releases?"

    I think I know the answer and really hope that I'm right :-)

  2. #2
    andopes's Avatar
    andopes is offline A Sugar Hero | Help Forum Moderator
    Join Date
    Jul 2006
    Location
    São Paulo - Brazil
    Posts
    8,335

    Default Re: Code base for core modules

    Quote Originally Posted by salesagility
    There's an interesting thread over at alfresco about the differences between the code base for the open source and proprietary versions of alfresco.

    The code bases between the two are different with the code base for the open source version deliberately left less stable than the paid for versions. This is an obvious strategy to drive people from open source to proprietary.

    I am VERY curious to discover if SugarCRM employs a similar strategy.

    Would anyone from the SugarCRM team like to answer this question:

    "Is the core code base for community edition modules such as accounts, contacts etc. the same as the code base for the same enterprise edition modules?"

    or

    "does SugarCRM do what Alfresco does and deliberately deploy less stable and more buggy community releases?"

    I think I know the answer and really hope that I'm right :-)
    Hi salesagility

    SugarCRM CE is not a buggy version of SugarCRM application.
    There are differences between the three flavors, but not bug.

    Think on SugarCRM ENT as the most complete flavor, containing all features.
    SugarCRM PRO has no some features, but these missed features does not introduce bugs.
    SugarCRM CE has no some additional features, but likely does not has bugs other than faced on licensed flavors.

    You can prove it this way:
    Browse on bugs.sugarcrm.com and look for a bug found into CE flavor.
    Take the same version for CE, PRO and ENT. You will be able to reproduce that bug into all.

    Regards
    André Lopes
    DevToolKit / Project of the Month - June 2009
    Lampada Global Services- Open Source Solutions
    Avenida Ipiranga, 318
    Bloco B - CJ 1602
    São Paulo, SP 01046-010
    Brazil
    Office: +55 11 3237-3110
    Mobile: +55 11 7636-5859
    e-mail: andre@lampadaglobal.com

    Lampada Global delivers offshore software development and support services to customers around the world.
    Lampada is proud to be a SugarCRM Gold Partner, revolutionizing Customer Relationship Management.

    I DO NOT answer questions through PM and Email. If you need some help post your question into SugarForum.

  3. #3
    salesagility's Avatar
    salesagility is offline Sugar Community Member
    Join Date
    Aug 2006
    Location
    UK
    Posts
    2,379

    Default Re: Code base for core modules

    Quote Originally Posted by andopes
    Hi salesagility

    SugarCRM CE is not a buggy version of SugarCRM application.
    There are differences between the three flavors, but not bug.

    Think on SugarCRM ENT as the most complete flavor, containing all features.
    SugarCRM PRO has no some features, but these missed features does not introduce bugs.
    SugarCRM CE has no some additional features, but likely does not has bugs other than faced on licensed flavors.

    You can prove it this way:
    Browse on bugs.sugarcrm.com and look for a bug found into CE flavor.
    Take the same version for CE, PRO and ENT. You will be able to reproduce that bug into all.

    Regards
    Uh, doh .... "ENT as the most complete flavor" ... s'cuse me....after three years of hacking SugarCRM that counts as a platitude.

  4. #4
    SugarDev.net is offline Sugar Community Member
    Join Date
    Feb 2008
    Posts
    1,401

    Default Re: Code base for core modules

    The answer is no. Twice.

    PS You shouldn't hack SugarCRM. It does not like...
    Developers go here
    Businesses go there (Dutch)

    Modules:
    SugarDev.net Developer Tools | Config | Dutch Language Pack
    "Nothing gets fixed unless there is a bug"

  5. #5
    eggsurplus's Avatar
    eggsurplus is offline Sugar Community Member
    Join Date
    Dec 2005
    Location
    Minnesota
    Posts
    2,343

    Default Re: Code base for core modules

    Yes, the codebase is the exact same for all editions. What they do is tag certain areas as being Pro or Ent. Then when they do a build for something like CE they strip out those code sections for Pro and Ent. When doing a Pro build they strip the Ent code sections out. So generally, if there is a bug in CE the bug exists in all versions.

  6. #6
    salesagility's Avatar
    salesagility is offline Sugar Community Member
    Join Date
    Aug 2006
    Location
    UK
    Posts
    2,379

    Default Re: Code base for core modules

    Quote Originally Posted by eggsurplus
    Yes, the codebase is the exact same for all editions. What they do is tag certain areas as being Pro or Ent. Then when they do a build for something like CE they strip out those code sections for Pro and Ent. When doing a Pro build they strip the Ent code sections out. So generally, if there is a bug in CE the bug exists in all versions.
    Cheers, thanks for that very clear answer eggsurplus ...we have avoided the Pro and Ent versions because we don't do non-Open Source software so didn't have anything to compare CE with ... so it's great to know that Sugar aren't doing the Alfresco thing .... WELL DONE SUGARCRM!!!

  7. #7
    Join Date
    Feb 2007
    Location
    San Jose, CA
    Posts
    1,169

    Default Re: Code base for core modules

    Hi all,

    Sorry I'm late in replying to this discussion (I don't manage the forums any more so I'm not in here as often as I used to be).

    We had a podcast that we published a while ago that describes our build process... you're right, we do have one code base with Pro and Enterprise layered on top of CE. You can hear all about it in this podcast, or read the transcript. The recording is kind of fun, so check it out!
    Susie Williams

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Code customizations to custom modules created by module builder
    By SanderMarechal in forum Developer Help
    Replies: 8
    Last Post: 2009-03-20, 02:40 PM
  2. Storing HTML code in Knowledge Base
    By dsmithies in forum Help
    Replies: 9
    Last Post: 2008-04-08, 07:11 AM
  3. Run multiple installs from single code base - can it be done?
    By gunner1095 in forum Installation and Upgrade Help
    Replies: 5
    Last Post: 2008-03-10, 04:38 PM
  4. need code for remote recursive chmod for modules
    By wookie in forum Feature Requests
    Replies: 3
    Last Post: 2005-07-31, 01:53 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •