[dotNetRDF-Develop] 0.8.0 to 1.0.0 Plans

[Rob V. <rv...@do...>]

Hi All

Per Tom's suggestions here is a quick summary of what I have planned for 0.8
through to 1.0.0 right now.

0.8.0 is intended to be the first release candidate for a stable 1.0, so the
features I plan to work on are primarily clean up and hardening related.
Fluent Query API is the only real new feature I have planned for the
release.

The aim is to get 0.8.0 out as a first release candidate by the end of
November, have a short release cycle to 0.9.0 as a second release candidate
with bug fixes only at the end of December and then have a stable 1.0.0
release again with bug fixes only at the end of January.  After that we can
start talking new features again and considering a more major refactor which
would be the 1.9/2.0 I talked about in a previous email.

Specifically for 0.8.0 I have the following planned:

Code Clean Up and Refactoring
* Follow deprecation policy, anything to be deprecated is marked obsolete
usable, stuff currently marked obsolete usable becomes obsolete unusable,
stuff marked obsolete unusable gets removed (In Progress ­ Mostly Complete)
* Some refactoring and clean up in MimeTypesHelper to make usage more
consistent and safer (In Progress)
* Some refactoring in the SPARQL engine about how aggregates and project
expressions are applied to make the code more consistent and maintainable
(Planned)

New Features
* Fluent Query API ­ Tom working on this (In Progress)
Tests
* Refactor old non-unit tests from dotNetRDFTest project into
dotNetRDFUnitTest project
* Remove dotNetRDFTest project once done
* Add more unit test coverage for existing features as appropriate

Full Text Library
* Upgrade dependency to Lucene.Net 3.0.3, this gives a more .Net like API
and allows us to sign the packages, use proper NuGet dependency for the
NuGet package and use the same version of Lucene.Net across all builds
Any further suggestions are welcome

Rob