-----Original Message----- From: amdatu-developers-bounces at amdatu.org [mailto:[email protected]] On Behalf Of Marcel Offermans Sent: maandag 11 oktober 2010 23:42 To: amdatu-developers at amdatu.org Subject: Re: [Amdatu-developers] Roadmaps, releases and building on Amdatu...
On 11 Oct 2010, at 17:26 , Bram de Kruijff wrote: >> WDYT? > > I'm all for working in a standardized way of working and taking great care in > making decisions about API(isch) changes. At the same time at this point I > guess it will be very difficult to keep bwc without any (integration) tests > in place so maybe we should prio that? Agreed, we need tests so we can be more confident about refactoring our codebase and checking if we broke backward compatibility. [Ivo Ladage-van Doorn] Agreed, as discussed before we can use the Pax Exam framework for that. Created a JIRA issue for it; http://jira.amdatu.org/jira/browse/AMDATU-107 > Also think users that are on the trunk should def register to the developer > list. All others will be on the user list and we should publish release > message and changes there. +1 [Ivo Ladage-van Doorn] Of course; +1 > Finally, with regard to the deployment, provisioning, topology and > clustering discussions we just started I am a little skeptical as to how long > we can maintain bwc for 0.x applications. Don't wanna scare anybody (yet), > but we should definitely discuss how this will affect the application model > soon so we can get a feel for the impact. I agree that we probably don't want to commit to any API just yet. The main point is making sure we are predictable. Users have the option to stick with a released version or go with trunk. They should be able to make an informed decision about what they want by following the project, and we should make it as transparant as possible for them. [Ivo Ladage-van Doorn] Indeed, I'm quite sure the current API is not final yet and we do need the possibility to change it along the way. Fixing the API before it had the time to become mature would be a very bad idea. So we need to make sure that each release is accompanied with very clear release notes about the changes regarding API, configuration, etc. That should make sure developers know what needs to be changed in their project when upgrading to a new version. Greetings, Marcel _______________________________________________ Amdatu-developers mailing list Amdatu-developers at amdatu.org http://lists.amdatu.org/mailman/listinfo/amdatu-developers
