Is that really a comparable project? I know next to nothing about Postgresql, but their change log only lists 13 changes over a 3 month time period between 7 people, all of which I would imagine have umpteen years of experience in just database coding.
In any case, they're maintaining 4 versions (7.2, 7.3, 7.4, 8.0). I don't think that OFBiz's structure (directory, file sturcture, etc) is set in stone enough for maintained release points to be of very much use to anyone outside of marketing endeavors. Everytime OFBiz deletes a file because of reuse, it becomes impossible to maintain any release prior to that delete (OFBiz SVN will fix one bug, the release points would have to find both bugs). Just my .02 --- Si Chen <[EMAIL PROTECTED]> wrote: > Postgresql is a good example. > > On Jul 24, 2006, at 1:52 PM, David E Jones wrote: > > > > > Chris, > > > > Exactly. If anyone knows of any I'd love to see > how they're doing > > things... it's not an easy course in general, and > I'm not sure if > > there are really many community driven enterprise > level projects. > > > > -David > > > > > > Chris Howe wrote: > >> Are there any open source projects that are not > driven > >> by a single company that successfully implement > >> feature freeze releases AND would have the > complexity > >> of feature advancements that OFBiz does (this > would > >> exclude most, if not all, Apache projects as most > of > >> them are one trick ponies, so to speak)? If > there > >> are, maybe we should see how they best accopmlish > >> this. > >> --- Si Chen <[EMAIL PROTECTED]> > wrote: > >>> David, > >>> > >>> Without coordinating a feature freeze between > the > >>> major contributors, it would be very very > difficult, especially > >>> for less > >>> experienced "volunteers", to maintain the > release branches and > >>> fix the bugs. From my personal experience > trying to create the > >>> opentaps releases, a good release can only be > created if the > >>> original > >>> version is reasonably stable and if the core > developers > >>> significantly support the effort by helping to > push the bug > >>> fixes from > >>> trunk to the release branch. > >>> > >>> On the issue of stability: > >>> > >>> 1. I propose that we put this > >>> http://jira.undersunconsulting.com/ > browse/OFBIZ-500 back into > >>> the main code base. It > >>> addressed a typecast issue with field-to-field. > >>> > >>> 2. I think we should take a vote: how many > people > >>> would like to keep current code "as is", so the > "OID" data type > >>> (used > >>> for storing images and content) works with > Derby and not > >>> PostgreSQL, > >>> versus making a change which would make it work > with PostgreSQL and > >>> not Derby? > >>> > >>> 3. I'll just keep my fingers crossed about the > >>> Geronimo transactions manager then. > >>> > >>> Si > >>> > >>> > >>> On Jul 24, 2006, at 10:13 AM, David E Jones > wrote: > >>> > >>> > >
