From: Matthias B. <inf...@mb...> - 2003-08-26 21:13:17
|
Hi Tony, one reason against putting them into 2.x: I want to be able to release a new 2.x version at any given time. All the cartridges in 2.x always have to be fully functional. This is not the case for new cartridges. Cheers... Matthias -----Original Message----- From: Tony Mowers [mailto:to...@am...] Sent: Tuesday, August 26, 2003 7:28 PM To: Matthias Bohlen; 'Wouter Zoons' Cc: 'Developers AndroMDA'; 'Users AndroMDA' Subject: RE: Elaborate sample model for the new struts cartridge Matthias, What would you think of putting these new cartridges into AndroMDA 2.x instead of AndroMDA 3.0. and then eventually merging them into AndroMDA 3.0 at the appropriate time? I am thinking it would be easier for a cartridge developer to work on their cartridge using an AndroMDA core that they know is unchanging. The reason I am asking is that there is nothing specific about the cartridges that require any new 3.0 features. What I am worried about is that we'll put the cartridge(s) in 3.x and then start to add a few core enhancements to AndroMDA that will almost certainly break the cartridges and in turn slow down the new cartridge development temporarily. Tony |