Array

Ted Leung wrote:
>
> Brian and Randy have a lot of work for the sharing
format, and I think 
> (they can correct me if I am wrong) that they have a
good idea of what 
> their mutual dependencies are.    What I am not as
clear on is at what 
> point we are going to run into needing to integrate
their work with 
> the work in the rest of Cosmo.   I think that at some
point the 
> sharing format work is going to go onto a branch and
then merge 
> back.   Do we need to plan ahead in order to minimize
disruptions when 
> that happens?

I think we should branch after maven2 work is completed, and
after I 
check in changes to use hibernate annotations.  Then I (and
others) can 
begin migrating code (on the branch) to use the new model
changes.  This 
includes daos, services, rpc, and dav layers.  Once this is
done, we can 
merge back and continue to work on sharing as this work
shouldn't affect 
anyone else.

-Randy
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

>
> I think we should branch after maven2 work is
completed, and after  
> I check in changes to use hibernate annotations.  Then
I (and  
> others) can begin migrating code (on the branch) to use
the new  
> model changes.  This includes daos, services, rpc, and
dav layers.   
> Once this is done, we can merge back and continue to
work on  
> sharing as this work shouldn't affect anyone else.
+1

To make things just a little more complicated, the account
activation  
work I'm doing requires a very small model change. I already
have it  
implemented in my working copy at the xml-file model and  
o.o.c.model.User levels, and don't imagine it would be too  
complicated to implement using hibernate annotations (it's
just an  
extra boolean property named "activated").

Given that, I'd propose the following ordering:

1. maven2/ hibernate annotations
2. "activated" field model change
3. branch

-Travis
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 11/16/06, Travis Vachon <travisosafoundation.org>
wrote:

> 1. maven2/ hibernate annotations
> 2. "activated" field model change
> 3. branch

+1

i'll be working on the subscription api on the trunk today,
but i
won't add any persistent behavior until after hibernate
annotations
have landed, so that will probably be on the branch.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev