[Netarchivesuite-devel] Plans for NetarchiveSuite after the 4.4 release

[Mikis Seth Sørensen]

Hi

Are a short summary for our current NetarchiveSUite development  plans after we wrap up the 4.4  release. Discussion this detail would be a natural item for our NetarchiveSuite friday talk in Paris.

As I mentioned on the last meeting, we have plan to use a couple of months to update and improve the NetarchiveSuite codesetup, so we hopefully afterwards can use more of our time producing new feaures, instead of trying to get the NetarchiveSuite system to work as expected. Currently we're spend a lot of time trying to fix stuff we break during development, because the current NAS codebase is somewhat difficult to maintain. Nicolas identified a lot of opertunities for improvement before he left, and we have also build up a list of things we would like to improve on.

So the current things we would like to work on for the next month or two are:

 *   Switch from the current Subversion repository on SBForge to git host on Github. See NAS-2041<https://sbforge.org/jira/browse/NAS-2041> Switch to git as the NetarchiveSuite SCM.
 *   Switch from using Ant to build NAS to using Maven. See NAS-8<https://sbforge.org/jira/browse/NAS-8> Switch to Maven as build tool,
 *   Reduce the complexity of the current DB maintenance setup. This includes a number of more concrete tasks:
    *   Decide whether we are continuing with our current DB specific SQL or switch to a using a DB abstraction layer like Hibernate
    *   Improve our DB upgrade mechanisme. See NAS-2265<https://sbforge.org/jira/browse/NAS-2265> DAO refactoring - Drop programmatic DB updates and versioning table.
    *   Replace the current Derby test with a test DB which doesn't come with it's own SQL flavour. See NAS-2268<https://sbforge.org/jira/browse/NAS-2268>  Switch to H2 as TestDB.
    *   Reduce the current host of DB dumps and DB creation scripts used in testing to a single DB schema definition + some DB enrichment/migration scripts.
    *   Perhaps drop MySQL support, if ONB switch to PostgreSQL. This would bring the number of SQL flavours we need to supprt to 1.

 *   Extend the number of automatic system test, to enable us to cheap and continuously run tests on deployed NetarchiveSuite systems. See
 *   NAS-1859 Create automatic and continuous sanity test of the NAS system<https://sbforge.org/jira/browse/NAS-1859>. This can hopefully be made test system independent so the tests may be run on the environments used at ONB and Bnf. The work has already started on this as I would like to continuously deploy and test the Quickstart system, besides the current DK testenvironment tests.
 *   NAS-2276<https://sbforge.org/jira/browse/NAS-2276> Switch to more modern unit test framework<https://sbforge.org/jira/browse/NAS-2276>.
 *   NAS-2124<https://sbforge.org/jira/browse/NAS-2124> Switch to slf4j as logging framework.

Thorbjørn is already deeply involved in preparing for the Git and Maven migration, and we plan to perform this switch shortly after the 4.4 codefreeze is lifted (next week perhaps?). Have a look at the two issues related to these migrations for details.

Any thoughts on these ideas or other pressing stuff we should look at? Would BnF or ONB be interested in participation in any of these improvement efforts?


After this we plan to start working towards supporting H3. We'll hopefully have both Nicholas and Thorbjørn available full time to work on this. But we would of course also very much like to have BnF and ONB involved is this effort, as this is a pretty fundamental change in the NetarchiveSystem. We hope to have initial experimental H3 support ready for a November? Devel release, with a Prod release at the end of the year perhaps ??

Best
Mikis


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.sbforge.org/pipermail/netarchivesuite-devel/attachments/20140501/0ba29402/attachment.html>