From: Ronald J Kimball Date: Wed, 20 Apr 2011 01:07:10 +0000 (-0400) Subject: DevelopProcess.pod should mention git before svn, deep-link to git repo X-Git-Tag: 5.8008~8^2 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=commitdiff_plain;h=6d4f27bd7f72bd3e66d952a37301ca09a20f97b3;hp=0ed0d69a27f35ca1ead675135ae9cdecaf457ddb DevelopProcess.pod should mention git before svn, deep-link to git repo May want more text under repositories explaining the state of the subversion repository. --- diff --git a/lib/Catalyst/Manual/DevelopmentProcess.pod b/lib/Catalyst/Manual/DevelopmentProcess.pod index f7edbfe..83245c9 100644 --- a/lib/Catalyst/Manual/DevelopmentProcess.pod +++ b/lib/Catalyst/Manual/DevelopmentProcess.pod @@ -33,17 +33,17 @@ will talk you through how to submit a patch, or get a "commit bit". =head2 Repositories -The Catalyst subversion repository can be found at: - - svn: http://dev.catalyst.perl.org/repos/Catalyst - browser: http://dev.catalyst.perl.org/svnweb/Catalyst - -and the git repository can be found at: +The Catalyst git repository can be found at: read: git://git.shadowcat.co.uk/catagits/PROJECTNAME write: catagits@git.shadowcat.co.uk:PROJECTNAME browser: https://git.shadowcat.co.uk/gitweb/gitweb.cgi +The Catalyst subversion repository can be found at: + + svn: http://dev.catalyst.perl.org/repos/Catalyst + browser: http://dev.catalyst.perl.org/svnweb/Catalyst + =head2 Schedule There is no dated release cycle for Catalyst. New releases will be made @@ -53,12 +53,12 @@ significant feature addition, is completed. =head2 Roadmap for features The Catalyst Roadmap is kept at -L +L =head2 Bug list The TODO list with known bugs / deficiences is kept at -L +L =head1 The Catalyst Core Team @@ -121,9 +121,9 @@ current members. Any change to the Catalyst core which can not be conceived as a correction of an error in the current feature set will need to be accepted by at least 3 members of the Core Team before it can be -committed to the trunk (which is the basis for CPAN releases). Anyone +committed to master (which is the basis for CPAN releases). Anyone with access is at any time free to make a branch to develop a proof of -concept for a feature to be committed to trunk. +concept for a feature to be committed to master. =head2 Organizational and Philosophical Decisions.