List view
This milestone brings some bug fixes including the performance issues relating to documents and also strong-naming of the assemblies.
No due date•8/8 issues closedThis is a single-issue milestone for `v1.0.5`.
Due by February 19, 2018•1/1 issues closedThis will be a backwards-compatible bugfix release.
No due date•1/1 issues closedThis is a bugfix milestone, it will be backwards-compatible.
No due date•1/1 issues closedThis is a bug fix release. It won't contain much.
No due date•3/3 issues closedThis is a backwards-compatible bugfix release of ZPT-Sharp.
No due date•5/5 issues closedAs of a yet-undecided version number, I would like to have ZPT-Sharp packaged for Debian, meeting the DFSG. The primary barrier to this is that all dependency software packages must also be packaged themselves. There are a number of such dependencies (documented in the project in the file *`DEPENDENCIES.md`*) - many of which are not yet available in the Debian ecosystem.
No due date•10/10 issues closedThis milestone indicates version `0.9.0`. It marks the second major beta release (albeit that it will actually be beta-3), and contains issues which are not important enough to block the first beta, but should be done before going to a first release.
No due date•19/19 issues closedThis milestone indicates version number `0.8.0`. It marks the first public beta release (the point at which we can start publicising ZPT-Sharp). Note that originally version `0.8.0` was earmarked as an alpha release, with its own milestone. This beta milestone is the result of merging that alpha milestone with this and taking over the `0.8.0` version number.
No due date•19/19 issues closedFirst stable release
No due date•6/6 issues closedThis milestone is mainly large feature enhancements and "epic" tasks which have up-to-now been deferred.
No due date•21/21 issues closedThis sprint splits between two things. A few are left-over tasks which will bring extra/improved functionality to the project. Others are hardening tasks which will make the project more robust and reliable.
No due date•44/44 issues closedThis is a 'tidy up technical debt' and 'make less important improvements' milestone. Additionally, some hardening and more thorough test coverage should go in here.
No due date•19/19 issues closedThis is a purely value-added milestone. No optional tasks which don't have a direct improvement to the final 'product'.
No due date•18/18 issues closedThis is the first testing version of the rewritten codebase, which has enough features to be reasonably useful.
No due date•32/32 issues closed