Von: rmacian
I agree with you. I have been adding my “bugfixes” in my blog but is not the best way to share them. Alfresco JIRA has both a CE and EE bug list but usually the fixes are proposed in terms of EE...
View ArticleVon: Andreas Steffan
Seems, we are not alone. Isolating and/or backporting a fix can get quite a bit of effort, and even frustrating when you get the feeling other people have been there before or will get there...
View ArticleVon: Jeff Potts
Definitely, you should be submitting patches through Jira. But of course the problem is that those patches will never result in an Alfresco-supported maintenance release or hotfix for Community, at...
View ArticleVon: Andreas Steffan
Hallo Jeff, I don’t have a definite answer to your question, as I cannot really judge the whole situation (legally, politically and technically). As a community contributor, I personally would...
View ArticleVon: Jeff Potts
Definitely, I agree that the “two flavors” with no easy way to “commit and share” is the root of the problem. Based on the recent community survey, I think there are actually a smaller number of people...
View ArticleVon: Andreas Steffan
Thanks for commenting, Jeff. The approach to choose surely depends on the scale of the problem (amount of community contributors interested in core code change management). SpringSource projects surely...
View ArticleVon: Alfresco Community R/W-Source Repository Available (Bugfixes) |...
[…] my post Alfresco Community Bugfixing I stated I wish we (as the community) had something — a system and/or process to […]
View Article