Recently I have received many new feature requests and enhancements ideas for Retrospectiva. Some of them are really important and I simply don’t want to wait any longer to implement these. My basic goal for v1.0 was to stabilise the code base to remove legacy overhead and to create a solid but simple application that should be able to meet all the basic user requirements. I think I am now able to say that all the major issues have been solved and that Retrospectiva is now mature enough to get the RC status.

For these reasons (and to get back to the actual point of this posting) I created a new branch in the repository called branches/1-0, so all changes (bug-fixes only) related to the upcoming v1.0 release will end up in this directory. All changes made to the trunk will from now target the 1.1 version. Please remember to switch your installation to the new branch if you want to stick to v1.0 by executing:

svn sw svn://dvisionfactory.com/retrospectiva/branches/1-0

To make my point clear, once again:

• If you use Retrospectiva productively and are happy with the current feature set, so please switch to the newly created 1.0 branch using the command above!
• But, if you require additional features and use Retrospectiva for non-critical purposes or are just adventuresome don’t do anything (except svn up once in a while)!

Plans

My general goal for Retrospectiva v1.1 is to make the application more flexible while keeping the base simple following my run straight away – configure by and by principle. After installing users should be able to run Retrospectiva without any further interferences while more advanced operators should be able to easily adapt the application to their personal needs. Furthermore I want to keep the application as general as possible, too specific functionalities will not be part of the main distribution but can be added as plugins if they are required. To cut a long story short, here are my concrete plans for the first features:

• I am going to create a trigger-indipendent ticket subscription system [#37]. The actual mail delivery will primarily be done by cron, other more sophisticated solutions (eg. backgrounDRb) can be added later.
• Another hight priority issue is i18n [#43], this one should be available quite soon.
• Last but not least I also would like to make the ticketing system more flexible. Partial ideas are already summarised in [#104], but I plan to go step further (but without violating the run straight away – configure by and by principle).

Dimitrij

PS: I simply cannot stop reminding all users who want to stick to the 1.0 version to switch their Subversion working directory to the new branch. Please read the information above for more details.