I placed the 1.0 version in the files section as p5.zip. This version is identical to the one on the web site, and is considerably older than the source here reflects. However, placing it here means all of the files for P5, including releases, are available here. The plan is to remove it from the web site.
You will note the website terms this version 1.1, even though it is labeled 1.0. It in fact probably is version 1.0 with fixes, and thus more properly labeled 1.1. However, I am going to be conservative and leave the 1.0 label.
As with all versions, 1.0 is fully tested using the included test suite.
1.0 is archived as p5_1_0.zip.
1.2:
The best way to get progress on 1.2 is to look over the tickets. I have been getting better about having the tickets reflect actual work to be done, although I admit some bogus tickets had to be retracted.
In short, we are down to 3 remaining issues on the PRT (Pascal Rejection Test). There are, however, other issues that have been opened up during that work. I think we are slipping towards a September release.
As with all releases, the 1.2 release will reflect a completely tested implementation. I fully well expect, as always happens with releases, for there to be further issues discovered that will lead to a 1.3 release. Although 1.2 is the final release of P5, I plan to correct any bugs or documentation errors in the system and issue further releases based on that work. The rule going forward is that even documentation changes will get release numbers, so expect that doc fixes will be collected for a while before a release. As usual, if you want beta fixes, you need to look at the current source tree.
Please note that the source code bears the 1.2 label now. The convention has been to immediately change the version number to the next candidate after a release. Thus the source bears the label it will be released under in the next release. This perhaps would be fixed with a nice build numbering system, but that is the way it is for now.
Last edit: Scott Franco 2014-08-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
News for August 7, 2014
1.0:
I placed the 1.0 version in the files section as p5.zip. This version is identical to the one on the web site, and is considerably older than the source here reflects. However, placing it here means all of the files for P5, including releases, are available here. The plan is to remove it from the web site.
You will note the website terms this version 1.1, even though it is labeled 1.0. It in fact probably is version 1.0 with fixes, and thus more properly labeled 1.1. However, I am going to be conservative and leave the 1.0 label.
As with all versions, 1.0 is fully tested using the included test suite.
1.0 is archived as p5_1_0.zip.
1.2:
The best way to get progress on 1.2 is to look over the tickets. I have been getting better about having the tickets reflect actual work to be done, although I admit some bogus tickets had to be retracted.
In short, we are down to 3 remaining issues on the PRT (Pascal Rejection Test). There are, however, other issues that have been opened up during that work. I think we are slipping towards a September release.
As with all releases, the 1.2 release will reflect a completely tested implementation. I fully well expect, as always happens with releases, for there to be further issues discovered that will lead to a 1.3 release. Although 1.2 is the final release of P5, I plan to correct any bugs or documentation errors in the system and issue further releases based on that work. The rule going forward is that even documentation changes will get release numbers, so expect that doc fixes will be collected for a while before a release. As usual, if you want beta fixes, you need to look at the current source tree.
Please note that the source code bears the 1.2 label now. The convention has been to immediately change the version number to the next candidate after a release. Thus the source bears the label it will be released under in the next release. This perhaps would be fixed with a nice build numbering system, but that is the way it is for now.
Last edit: Scott Franco 2014-08-11