Hi Chad, Wouter,
the release management has actually nothing to do with the "distribution" management - gee I hate to use those "management" words ;-) AndroMDA can still distribute everything in one zip file like today. And this makes sense, since many people don't like to download many zip files (at the end this is what I've done in EJOSA ;-))... What I meant with the release management is more on the APIs development of the AndroMDA core... It is important to have stable APIs on the AndroMDA core. It would be very hard to follow if you release AndroMDA cartridges very offen (which is very good) and at the sametime always change the AndroMDA core APIs and metafacades (which is not very good, since many cartridges out there are based on this). Alltogether: 1. AndroMDA core APIs should be stable. 2. AndroMDA cartridges should be released often. Example from the "distribution perspective": something like andromda-bin-core3.1-cartridges3.3.zip contains AndroMDA core 3.1 and AndroMDA cartridges 3.3 ... andromda-bin-core3.1-cartridges3.7.zip contains AndroMDA core 3.1 and AndroMDA cartridges 3.7 ... So the version number of the core and the cartridges does not have to be the same. I hope I can make my self clear with this :-) Regards, Lofi. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=769#769 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
