Hi all,

And a related question; currently we only use 1 project in JIRA called 
"Amdatu". Do we want to define a separate project for each subproject? If each 
subproject should have its own lifecycle, it is kind of mandatory...
And if so, what JIRA projects should we create? Something like:

Amdatu (for all overall issues)
Amdatu Core
Amdatu Web
Amdatu Auth (? Or split into authentication/authorization or even 
authentication/authorization/oauth?)
Amdatu Cassandra
Amdatu Semantic
Amdatu OpenSocial
Amdatu Provisioning (?)

I think it may be a better idea to start with the split off of only 1 
subproject, see how this works, learn of the problems, fix & improve and then 
split of the other subprojects. My suggestion would be to start with the 
Cassandra subproject.

Regards, Ivo

GX Software | Ivo Ladage-van Doorn | Product Architect | Wijchenseweg 111 | 
6538 SW Nijmegen | The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 388 
86 21 | 
[email protected]<mailto:[email protected]> | 
www.gxsoftware.com<http://www.gxsoftware.com> | 
twitter.com/GXSoftware<http://twitter.com/GXSoftware>

_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to