Hi, I wanted to get some feedback on CVS/Mail infrastructure for commons so I asked a bunch of people who are not subscribed here. All of them were java people, some were from jakarta, some from xml and some were non-Apache peeps (but who use Apache stuff). Basically I asked them what they would be most comfortable with and gave em a bunch of options. It was interesting to see how the results turned out.
* 9 out of 11 said they wanted the CVS structure separated out based on language. The main reason was to do with minimum amount of work they can do to build a project. ie Say we have a java component X that depends upon Y (which may depend upon Z). To be able to build this in commons or excalibur you update the whole repo and then build as normal. If there was mixed codebases (C/C++/java/perl/python) you would update a lot more stuff than is necessary. While it is still true when it is all java (several people complained that excalibur was too big to update), mixing all sorts of languages in there would be prohibitively expensive. The other option of only updating the projects you know you will use requires that end users know all the dependencies and remember to update all of them everytime they need an update. This is painful for new users and a little error prone. * 5 out of 11 said they wanted mail separated based on language * 6 out of 11 said they wanted mail separated based on concept * All of the non-Apache people wanted per-component announce lists. Anyways - thats java peeps. I am not sure if it is similar in other places. What do non-java people think of this? -- Cheers, Peter Donald ------------------------------------------------------- To fight and conquer in all your battles is not supreme excellence; supreme excellence consists in breaking the enemy's resistance without fighting. - Sun Tzu, 300 B.C. -------------------------------------------------------
