The discussion in #38 lead to the idea that it could be beneficial to start working on a v2 of PHPTAL. The scope would be limited to removing features that have been marked deprecated (or are not needed because of improvements in newer PHP versions), cleaning up the code/folder structure (Quality Assistance), and have things use Composer (autoloader/install/dependency constraints/etc.).
To get an idea of what we might be getting ourselves into, it would be wise to have a look at the code and analyze exactly how much work a v2 would require.
Hence this ticket.
This issue can then be closed once a fixed set of items has been reached (and agreed upon) and issues have been made for each item. Progress can then be measured using the v2 milestone.
Version 2.0.0
All of the following would need to be done: separate issues should be created for each item
[ ] Improve/update the documentation - #41
[X] Composer only install Composer - #43
[ ] Improve code-coverage/risky code checks by making the PHPUnit config more strict and annotating tests with @coversQuality Assistance
[ ] PHP 5.5+ support Quality Assistance
Although changes/additions might be useful, those are not the focus of this issue and should be added to a v3 milestone.
Introduction
The discussion in #38 lead to the idea that it could be beneficial to start working on a v2 of PHPTAL. The scope would be limited to removing features that have been marked deprecated (or are not needed because of improvements in newer PHP versions), cleaning up the code/folder structure (Quality Assistance), and have things use Composer (autoloader/install/dependency constraints/etc.).
To get an idea of what we might be getting ourselves into, it would be wise to have a look at the code and analyze exactly how much work a
v2
would require.Hence this ticket.
This issue can then be closed once a fixed set of items has been reached (and agreed upon) and issues have been made for each item. Progress can then be measured using the v2 milestone.
Version 2.0.0
All of the following would need to be done: separate issues should be created for each item
@covers
Quality AssistanceAlthough changes/additions might be useful, those are not the focus of this issue and should be added to a
v3
milestone.Version 3.0.0