X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass.pm;h=c3be35063b999d01dbfefa6b219b0c83254c474b;hb=1e4f9fb3b8bd1f54518bc2942554099356fa6524;hp=0b74025f739ad900463b0df5236e29fbaacf1305;hpb=a93441f2e2e22127602b7c24e05237ffc10ab786;p=dbsrgits%2FDBIx-Class.git diff --git a/lib/DBIx/Class.pm b/lib/DBIx/Class.pm index 0b74025..c3be350 100644 --- a/lib/DBIx/Class.pm +++ b/lib/DBIx/Class.pm @@ -11,7 +11,7 @@ our $VERSION; # $VERSION declaration must stay up here, ahead of any other package # declarations, as to not confuse various modules attempting to determine # this ones version, whether that be s.c.o. or Module::Metadata, etc -$VERSION = '0.08205'; +$VERSION = '0.08241'; $VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases @@ -99,43 +99,67 @@ sub _attr_cache { DBIx::Class - Extensible and flexible object <-> relational mapper. -=head1 GETTING HELP/SUPPORT +=head1 WHERE TO START READING -The community can be found via: +See L for an overview of the exhaustive documentation. +To get the most out of DBIx::Class with the least confusion it is strongly +recommended to read (at the very least) the +L in the order presented there. + +=head1 HOW TO GET HELP + +Due to the complexity of its problem domain, DBIx::Class is a relatively +complex framework. After you start using DBIx::Class questions will inevitably +arise. If you are stuck with a problem or have doubts about a particular +approach do not hesitate to contact the community with your questions. The +list below is sorted by "fastest response time": =over =item * IRC: irc.perl.org#dbix-class =for html -(click for instant chatroom login) +(click for instant chatroom login) =item * Mailing list: L -=item * Twitter L +=item * RT Bug Tracker: L -=item * Web Site: L +=item * Twitter: L -=item * RT Bug Tracker: L +=item * Web Site: L =back -The project is maintained in a git repository, accessible from the following sources: +=head1 HOW TO CONTRIBUTE + +Contributions are always welcome, in all usable forms (we especially +welcome documentation improvements). The delivery methods include git- +or unified-diff formatted patches, GitHub pull requests, or plain bug +reports either via RT or the Mailing list. Contributors are generally +granted full access to the official repository after their first patch +passes successful review. + +=for comment +FIXME: Getty, frew and jnap need to get off their asses and finish the contrib section so we can link it here ;) + +This project is maintained in a git repository. The code and related tools are +accessible at the following locations: =over -=item * git: L +=item * Official repo: L -=item * gitweb: L +=item * Official gitweb: L -=item * github mirror: L +=item * GitHub mirror: L -=item * authorized committers: L +=item * Authorized committers: L -=item * Travis-CI log: L +=item * Travis-CI log: L =for html - +
↪ Stable branch CI status: =back @@ -273,11 +297,6 @@ The test suite is quite substantial, and several developer releases are generally made to CPAN before the branch for the next release is merged back to trunk for a major release. -=head1 WHERE TO GO NEXT - -L lists each task you might want help on, and -the modules where you will find documentation. - =head1 AUTHOR mst: Matt S. Trout @@ -303,6 +322,8 @@ amiri: Amiri Barksdale amoore: Andrew Moore +andrewalker: Andre Walker + andyg: Andy Grundman ank: Andres Kievsky @@ -341,6 +362,8 @@ clkao: CL Kao da5id: David Jack Olrik +davewood: David Schmidt + debolaz: Anders Nor Berle dew: Dan Thomas @@ -419,6 +442,8 @@ michaelr: Michael Reddick milki: Jonathan Chu +mithaldu: Christian Walde + mjemmeson: Michael Jemmeson mstratman: Mark A. Stratman