Well as soon as a major release is out the door, in that branch only bugfixes are added that have agreat effect on the application. So I am sure that mostly 2-3 Modules change. I know that in general updating a client with about 20mb doesn't sound that bad in our days, but imagine the load on the servers if hundreds of clients all over the worls start updating simultaneously. And there are quite some uses with analog modems ... updating them every time would mean a downtime of hours for them (I was told). So the company tries to keep the number of updated modules to a minimum.
Chris ________________________________________ Von: Wayne Fay [[email protected]] Gesendet: Dienstag, 16. Oktober 2012 01:26 An: Maven Users List Betreff: Re: Independent module release strategies > The project consists of about 50 Maven artifacts. A lot of people are > using this project all over the world. The client is distributed by some > web-start similar solution. > > The problem is whenever a bugfix-release is done, we don’t want to release > all modules in a new version because then all of these would have to be > downloaded by the clients. Have you performed any analysis of previous changes to give you an indication of the relative stability of one module vs the rest? Is it true that most changes are happening in one or two modules while the rest is stable -- or are changes found in most any module with no obvious pattern? I would expect that suggested approaches for "solving" your problem may depend a bit on the answers to these questions. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
