cancel
Showing results for 
Search instead for 
Did you mean: 

Alfresco Labs 3 Beta is Here!

nancyg
Champ in-the-making
Champ in-the-making
All,

Everyone around Alfresco has been hard at work over the past several months on our latest release, Labs 3. We invite you to download it, kick the tires and send us your feedback.

You can find a lot of info in the wiki, the starting page is http://wiki.alfresco.com/wiki/Alfresco_Labs_3, a list of features is at http://wiki.alfresco.com/wiki/Alfresco_Labs_3_Feature_List and the download and install instructions at http://wiki.alfresco.com/wiki/Installing_Labs_3. You can read what John Newton, our co-founder and CTO, has to say on his blog, http://newton.typepad.com/content/2008/07/introducing-alf.html.

Enjoy the new release and stay tuned for more exciting developments!

Nancy
49 REPLIES 49

dozyarmadillo
Champ on-the-rise
Champ on-the-rise
I have to agree with Martin on this. The Labs releases are basically betas. The Enterprise release are final/stable releases. I can't think of any other Open Source project where you have to pay to get access to the stable code. Even RHEL is available in source code form for free.

xerox
Champ in-the-making
Champ in-the-making
I have to agree with Martin on this. The Labs releases are basically betas. The Enterprise release are final/stable releases. I can't think of any other Open Source project where you have to pay to get access to the stable code. Even RHEL is available in source code form for free.
You can find a blogpost about this: http://nheylen.wordpress.com/2008/08/04/alfresco-open-source-or-not/

andnyg
Champ in-the-making
Champ in-the-making
zaizi wrote: "The bug fixes and patches for this new functionality will be available in enterprise 3.x."

This (again?) raises the question in what pace the patches bug fixes will be available in the Labs version. If this isn't very clearly explained there is an obvious risk that the labs users will be less motivated to report bugs at this point.

/Anders

bgl
Champ on-the-rise
Champ on-the-rise
Hi,

Could you tell us which svn revision (of public repository of course Smiley Wink ) was used to produce this version ?

thank you !

Boris

pmonks
Star Contributor
Star Contributor
Anders wrote: "This (again?) raises the question in what pace the patches bug fixes will be available in the Labs version."

This has been answered previously (see http://forums.alfresco.com/en/viewtopic.php?f=20&t=8993#p43677 for example).

Cheers,
Peter

mikeh
Star Contributor
Star Contributor
Hi,

Could you tell us which svn revision (of public repository of course Smiley Wink ) was used to produce this version ?

thank you !

Boris
Should be rev 2575.

Many fixes and additions have already been added since then though, so you'd be better off getting the latest if you're testing 3.0

Thanks,
Mike

hvyas
Champ in-the-making
Champ in-the-making
["Are there Labs users who favour stability over innovation? Of course, and we encourage them to consider the Enterprise edition."]

Of course, they favor stable (not supported) code….otherwise what’s the point of experimenting/testing new features and providing valuable feedback.


["Are there Enterprise users who favour innovation over stability? Of course, and we encourage them to experiment with the innovative new features included in the Labs edition."]

Are you kidding ……It seems that sole purpose of the Alfresco lab is to save your enterprise customers of testing new features in the upcoming releases.


I think Alfresco should make it clear that community (Lab) releases are not at all for any production use and is unstable. So that community people won’t mislead by thinking that it is a true open source product like others and can get stable (unsupported) code.

callermd
Champ in-the-making
Champ in-the-making
Peter,

As a model the 'labs open/enterprise closed' model is marginally better than a proprietary model, in that you can examine the source code and make patches; however you are not adopting the traditional commercial open source model - where an identical product (or identical for a given subset of features) is released under a GPL type license with no support, warranty (i.e.  If it bursts into a ball of flame and burns down your building - tough luck) and a commercial license is concurrently released which includes technical support, warranties, etc.  In your case you have an unstable product under Open Source, never stabilized or tested, and a stable commercial product - so for any given subset of features the products are not identical.

For document management applications, given that the focus is BUSINESS with complex enough processes that require a document management solution, ALL users are interested in stability.  Experimental features are nice, but that is why we have Betas.  For those of us who started using to Alfresco Community WHEN IT WAS POSITIONED AS A STABLE (NON-BETA), we have really been left high and dry. 

There are a few ways to remedy our situation:
1)  Alfresco changes gears and does concurrent stable releases between Enterprise and Community editions.  Labs continues or not (we don't really care).  Best outcome from our perspective (and there is some evidence to suggest that other users on the board feel similarly).
2)  Third party forks and creates a stable community release.  Better outcome.  Even better outcome is getting this branch then packaged and included into Fedora, Debian, etc. so that Alfresco becomes the de facto content management solution for the open source world.
3)  We buy enterprise licenses simply to get a stable version.  Bad outcome - leaving us not feeling great about Alfresco.
4)  We are forced to apply our own fixes and maintain our own branch.  Worst outcome.

dhalupa
Champ on-the-rise
Champ on-the-rise
3)  We buy enterprise licenses simply to get a stable version.  Bad outcome - leaving us not feeling great about Alfresco.
and you get the source, I do not see what is the problem here. Try buying some Documentum licenses from EMC and see whether you will get a commented source code. It seems to me that you are more interested in getting the product free of charge than in having source code available.

Kind regards,

Denis

fselendic
Champ in-the-making
Champ in-the-making
Documentum doesn't even pretend to be open source Smiley Very Happy

It is not so simple. Let's not mix established players with disruptive newcomers. Well known fact is that in open source world there will be lots of people who don't want to pay for the license. All people want stability (which is why I find Peters damage control post comical), but just some are willing or able to pay for it. And number of paying customers depends more on pricing strategy than on having two versions, stable and broken one.

When someone like Alfresco has strategy based on open source, it is usually because it attacks already formed market, taken by big players. Open source enables to rapidly take and retake parts of that market. It is all about distribution. Which is what worries me with this approach. Basically, Alfresco is opting for 10k installations with 10k paying customers, instead of 1mil installations with 10k paying customers. Not having stable OS edition will do nothing about number of paying customers, but it will slaughter potential huge volume of installations that free (or even non free but much cheaper solution) would have. From what I've seen so far, clever pricing strategies always win against "we are open, but aren't really open" tricks that pop up now and then on open source scene.

Also, you make it sound bad when someone wants Alfresco for free Smiley Very Happy Alfresco itself uses tons of free and opensource products and components, and wouldn't be possible in this form if they would pay for every single one of them (and especially if every single one of those had same "innovative" aproach to packaging software). Being open source brings some advantages to the table, bug cleansing and testing being the most talked about, but, personally, i think that biggest plus for VC funded company like Alfresco is huge installation volumes, evangelizing and free marketing that it gets from people who don't pay licenses.

After all, biggest acquisitions of open source companies had absolutely nothing to do with number of paying customers, yearly revenue or profit: it is all about market share and presence. This model kills those, and I would like Alfresco to rethink approach once again, because I don't feel right balance is achieved.

Note: I do think Alfresco was more than fair and brave up until now, with full suite GPLed. Even with this model, those who want and know, will be able to manage and take the most out of it. Just am a little bit worried about bad press this decision is already starting to get, and impact of not having stable OS version on installed base.