Hi all, As Amdatu we already have several projects building on our core. At the same time, we're a project that is still growing, refactoring and optimizing fast. I'm starting this thread to try to come to some kind of consensus about how do deal with change in such a way that people using Amdatu can still build on it whilst we can still innovate.
I think recent initiatives such as restructuring the build, making sure Bamboo is up and running, adding tests and code coverage and our roadmap [1] already help a lot here, but nevertheless we need to make sure we all work in a predictable way. That means that changes in general should be initiated by creating a task for it in JIRA, especially if they involve some kind of feature/API change. This way people using Amdatu can learn about them in advance and voice their concerns if appropriate. At the same time, users of Amdatu have two options. They can either uses released versions, as found in our downloads section [2], or they can use our "bleeding edge" trunk. In any case it is probably advisable for them to register to our mailing lists to learn about what's going on in the project, as that's our only official way of making decisions and discussing features and changes [3]. WDYT? Greetings, Marcel [1] http://amdatu.org/confluence/display/Amdatu/Roadmap [2] http://amdatu.org/confluence/display/Amdatu/Downloads [3] http://amdatu.org/confluence/display/Amdatu/Project+information -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.amdatu.org/pipermail/amdatu-developers/attachments/20101011/147b9066/attachment.html
