Re: Tasks for a release

Posted by BJ Freeman on Jul 24, 2006; 8:16pm
URL: http://ofbiz.116.s1.nabble.com/Re-Tasks-for-a-release-tp170046p170063.html

Basically we have the Framework and the application.
so why not have an RC for the framework first, then RC for each application.
I know the problem with applications is interdependence. I believe this
method will bring about a better design that will allow one application
to go thru its process without worrying about what the dependencies on
the other app will do.



Si Chen sent the following on 7/24/2006 11:33 AM:

> 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:
>
>>
>
>