- * here.'); ?> + * here.'); ?>
- here.'); ?> + here.'); ?>
- CakePHP. By finding and reporting issues in the code you notify the maintainers of any issues and help get them resolved. Tickets for all CakePHP projects are located at Lighthouse.'); ?> + CakePHP. By finding and reporting issues in the code you notify the maintainers of any issues and help get them resolved. Issues for all CakePHP projects are located on GitHub.'); ?>
- new tickets need to be triaged and have the correct tags, as well as having a milestone assigned to them. You can help by looking at new tickets and adding the correct tags. Additionally, confirming or asking for more information on unclear tickets doesn\'t take much time, and helps speed up the process.'); ?> + new issues need to be triaged and have the correct tags, as well as having a milestone assigned to them. You can help by looking at new issues and adding the correct tags. Additionally, confirming or asking for more information on unclear issues doesn\'t take much time, and helps speed up the process.'); ?>
- defect, enhancement and rfc move tickets into related bins.'); ?> + Defect, Enhancement and RFC move issues into related bins.'); ?>
- here.'); ?> + here.'); ?>
- open unresolved issues is a great way to get involved with CakePHP, and is one of the first steps to becoming a core contributor. If you\'re interested in a particular version, there are lists of open unassigned tickets for.'); ?> + open unresolved issues is a great way to get involved with CakePHP, and is one of the first steps to becoming a core contributor.'); ?>
+- 3.0 milestone. There are still a number of incomplete tasks and unresolved tickets. If a ticket has been moved into the 3.0 milestone it is planned for inclusion in the release. Tickets are moved into this milestone based on community feedback and the core team\'s plans. If you plan on contributing a feature, please also include relevant test cases for the feature. We want to keep CakePHP as bug free as possible, and test cases have proven to help immensely. If you submit features without test cases, and no documentation it is highly unlikely it will be merged in.'); ?> + 3.0 milestone. There are still a number of incomplete tasks and unresolved issues. If an issue has been moved into the 3.0 milestone, it is planned for inclusion in the release. Issues are moved into this milestone based on community feedback and the core team\'s plans. If you plan on contributing a feature, please also include relevant test cases for the feature. We want to keep CakePHP as bug free as possible, and test cases have proven to help immensely. If you submit features without test cases, and no documentation it is highly unlikely it will be merged in.'); ?>
CakePHP is continuously integrated, so you can check the status of the various builds on the Jenkins server at any time.'); ?> @@ -185,7 +187,7 @@
- CakePHP. We have two primary forms of documentation, the API and the CookBook. The API is generated from the source code, so if you find an inaccuracy or issue with the API documentation, you can file a patch against the source code. The CookBook is a community edited and moderated wiki. Once you have a Bakery account you can edit and add any documentation you think is useful. Also, submitting an article to the Bakery is a good way to share your code, processes, and experiences with CakePHP. Submissions are moderated and reviewed before publishing.'); ?> + CakePHP. We have two primary forms of documentation, the API and the CookBook. The API is generated from the source code, so if you find an inaccuracy or issue with the API documentation, you can file a patch against the source code. The CookBook is a community managed documentation source which can also be found on GitHub. Guidelines on contributing to the documentation can be reviewed here.'); ?>