by kurzedmetal » 29 Nov 2011, 15:23
Ohhh, i didn't know that, awesome :D maybe you should say that somewhere in the website too, i doubt it but there may be coders trying to add features to the old version, and their efforts would be in vain.
I still think you should encourage the community to get involved in the project and the new version, show your future plans, feature roadmap, your progress, the partial code repository of this new version, and you may get some positive feedback, early bug reports (if there any alpha version running), contributors may arise and code features you planned or didn't even expect/planned. You don't need a complete working version for that.
I'm just saying this because from my point of view (as a user and possible contributor), it seems the project is dead (no new versions, low forum/community activity, few project news), when actually it isn't the case at all (the main dev is working in a complete rework!).
I'm no expert in the subject, i'm just trying to give you my point of view, maybe you would benefit a lot from reading some texts about how to manage an open source project. i've read this a few weeks ago, pretty interesting: http://wiki.pentaho.com/display/OpenScrum/Home it first talk about open source project characteristics and then about using scrum (agile development) to manage an open source project
Good luck :)