[Xerte-dev] Re: Development Plan for next release

[Julian Tenney]

The titan pad isn't the right place for discussions, so I'm moving that here:

>We've never really cracked the modularisation problem, but it is possible to add new templates if you know what you're doing. It would be good to have an example / walk though of building a new template and adding it to the install.
>Does the app store not do this? I thought it did? It downloads the code from github and sets it up (or it did)

My question to everyone is whether this is i) working and ii) well understood? Perhaps it is me that missed something?

J

From: Tenney Julian
Sent: 09 February 2015 10:47
To: For Xerte technical developers (xerte-dev at lists.nottingham.ac.uk)
Subject: Development Plan for next release

Hi,

I'd like to draw up a plan of all the work we need, or want, to complete before the next release - then we can figure out the current status of each piece of work, who is owning it, how much work remains and so on. There is a titanpad here: https://titanpad.com/xerteDev. I'll write down as much as I can think of, but could you all check I've got everything you're working on, and anything else you'd like to see added. I'll then tidy it up into a more detailed plan before the end of this week if you can all put down your thoughts before end of Thursday?

We really want to get the release done in time for the Apereo conference in Baltimore: that is the first week in June, so we have something like 15 weeks to get the next release fixed up. Perhaps we need to work through a  few phases: a good first phase would be to get a running install with the bleeding edge code running on it so we can all run the latest code; then to work to finish the development, and then we need to have a decent amount of time for testing and fixing up the final codebase.

It might also be sensible to break the work down into sub-projects and divide responsibility for those between us? I'm happy to put some effort behind managing the whole thing, and to put some time into testing - and to help out wherever I can as well, obviously,

Julian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20150209/e905520e/attachment.html>