[Cosmo-dev] 0.6 model changes on a branch

[Randy Letness]

I've been making changes and making sure tests (functional/unit) keep 
passing.  I would never check in anything that would break the trunk.  
Also, when would we merge(because there is a lot of work to be done)?  I 
can foresee problems after the merge to work out kinks with new stuff on 
the trunk, and additional changes being done after the merge.  It just 
seems like extra work, but if it will help others out then I'm game for 
anything.

-Randy

Brian Moseley wrote:
> we're going to have extensive model changes in 0.6 that will have
> direct impact on a majority of the server code. to keep the trunk
> building and passing all tests, i propose that randy's model changes
> and all dependent changes (updating the dav and rpc layers, etc) be
> done on a svn branch.
>
> the benefit of course is that we can break features on the branch and
> not worry about the build failing or the tests not passing while we're
> working out all the kinks and then merge everything, once its working,
> back to the trunk.
>
> the drawback is having to perform the merge. i did this last time for
> the much more substantially different hibernate branch and it wasn't a
> big deal. i'm happy to merge this branch as well.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev