Saturday, May 7, 2005, 9:35:03 PM, Chad Brandon wrote: CB> Martin West wrote:
>>Have we given any thought to how we maintain version 3. If users use it >>in production they may not be able to upgrade to a new release. >> >>So we should think about how we distribute fixes for version 3. >> >>One technique I have used in the past is to have a service pack jar. For >>maven/mda it would mean adding a dependency for andromda-servicepack >>jar. >> >> CB> Why wouldn't we just have release 3.0.1, 3.0.2, etc?...that's what CB> we're planning on....and that's how other projects handle it. yes, we should create a branch after 3.0final where we can make small fixes for versions 3.0.1, 3.0.2 and so on (similar to what we did after version 2.0). On the HEAD branch, we should proceed with version 3.1.0, 3.1.1, etc. until we decide to switch to 4.0.0. Martin's question inspired me to think about extensibility, however. In July, I'd like to start to prototype the propagation of model changes to code (see my Confluence page for that). To be able to do this, I'd like to have an extension point (similar to the Eclipse architecture) where I can plug in something, without breaking the official distribution. We should discuss this subject in a separate thread, though. Cheers... Matthias --- Matthias Bohlen "Beratung, die Projekte erfolgreich macht..." Internet: http://www.mbohlen.de/ [EMAIL PROTECTED] Post: Luise-Albertz-Str. 25 D-53340 Meckenheim Tel: 0170 / 772 8545 Fax: 02225 / 945189 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
