[Dbix-class] Info for DBIx-Class developers (svn layout)

[Matt S Trout]

Yay! Three-tier layout -

trunk/DBIx-Class : main codebase. bar a marge prior to a major version 
release, nothing bar bug fixes goes here (minor feature additions are ok but 
talk it over with people first and make sure there's a consensus)

branches/DBIx-Class-current : main merging/stabilisation point. Stuff 
mostly-complete and ready for live testing gets merged back here

branches/DBIx-Class/* : feature-specific branches made from -current. Heavy 
development takes place here, then merge back to -current when it's done

Basic rationale: People can create a branch for the feature highest on their 
TODO list and hack on it, but -current doesn't have half-finished stuff in it. 
I want to be able to put a time-limit on -current as we approach a major 
version release (and that'll apply to my features too) so if a feature we were 
intending to put in a release isn't ready in time we can just leave it in its 
own branch rather than having to finish it off in order to make -current 
shippable.

Anybody with a DBIC commit bit will have commit to all three of these. I'd ask 
that people keep to the guidelines I've sketched above for trunk and -current, 
and co-ordinate with whoever created a subbranch about whether to commit stuff 
to there. If you have something you want to work on that isn't already in 
progress, feel free to create your own subbranch and get hacking.

-- 
      Matt S Trout       Offering custom development, consultancy and support
   Technical Director    contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +