As I think victor knows from my private email’s last weekend, I’m really passionate about fixing the Database Layer properly. I’m also really passionate about getting it out to users in a stable and well tested way.
We have a habit of not getting releases out, or not testing them properly. Therefore, I’m keen to set a fixed date for a 2.0 release – my proposal for that is 30th April. This is a date that I think is realistically achievable, given what I believe we would need to do before that point.
To avoid feature creep and not getting a release out at this point, I’d like to suggest we stick to 5-10 changes.
· New Db Layer
I’ve got an infinite amount of time to get this merged, and fully tested. It’s not fair on users who are struggling to make Mantis work on non-mysql DB’s not to do this. As already promised, I’ll send a daily update on progress of this feature, so we can focus testing and ensure this is 100% stable and tested.
We need to ensure api changes that plugin authors may need to follow are well documented.
I will be taking some common plugin’s and generating a 2.x version as part of the testing, so this should ensure that end users are not caught out with a non-working plugin.
· Testing Coverage Improvements
To aid in ensuring that we can state the above db layer is stable and tested
· Once 1-2 above are done, work with Victor to ensure we have a decent notification API/framework
Whilst there are other things I’d like to add/improve in Mantis, for now, the above 3 things are my primary focus (in pretty much the order listed above)
Would be useful to know if anyone else would be able to commit to finishing any other new features before 30th April…?
Timeline to achieving above goals:
· Weekend 4th-6th April
o Ensure schema generation on MSSQL
o Ensure schema generation on PGSQL
o Ensure schema generation on mysql
o Ensure schema generation on Oracle
o Provide Benchmark figures to mantisbt-dev list of memory/performance improvements of new db layer
o Identify edge cases from previous bugs that may need testing. Clone previous bugs on mantisbt.org/bugs to keep history but allow us to re-test and confirm they are still fixed.
· 6th-7th April
o Generate Tarball that some select/keen end users of pgsql/mssql/oracle and help confirm functuality
o Email Word/PDF document to mantisbt-dev list highlighting steps to install our 4 database engines with PHP so that we all have a chance to test future database layer changes in a Virtual Machine or whatever prior to sending to master. Hopefully this will help ensure we don’t end up with ‘bad schema’ updates in the future – especially given some of us are not familiar with some of our database backends
· 8th-11th April
o Db Layer testing / work out how to handle any db-unique ‘issues’ without requiring plugin author’s etc to understand full details of our 4 database platforms.
· 12th-13th April
o Get notification API changes merged in
· 14th April
o 2.0.0a1 ?
· 15th – 20th April
o Update any remaining Plugins with new db api support
· 21st-30th April
o Improve Mantis Documentation
· 30th April