|
From: <jue...@we...> - 2003-03-24 19:06:55
|
Quoting from a previous mail of mine, with slight modifications: <quote> Finally, in terms of distribution: Should there be a separate examples = download, or should they be included in the main download? Do we like to = separate binary and source distribution (analogous to Tomcat), or offer = a combined one (analogous to Log4J)? Do we include all the third-party = libraries or just give respective download URLs? Or do we include all = but specific larger ones that not everyone will need, like Velocity? Personally, I tend to prefer a combined download for developers, = including sources, third party libs, and Spring binaries (usable = out-of-the-box for both application and framework development) - = provided that it is of reasonable size (currently just ~1500 KB, without = Velocity). Of course, it would make sense to offer a binary-only = download too, with just the libraries needed for application development = (i.e. no Clover, etc - currently ~650 KB, again without Velocity). So = even with generated JavaDocs, some additional docs, and an example app, = the combined download will probably not exceed 2 MB, and the binary = download will clock in around 1 MB. The only drawback is that users have to copy some framework and third = party JARs to WEB-INF\lib if they want to run the example app, but this = should be easy to document. Of course, we could go the Struts/WebWork = way of providing preassembled WARs and EARs that duplicate all the = libraries - but look at their distribution file sizes, ~20 MB/~17 MB for = the zipped versions... I believe that Spring's distribution size should = express Spring's general slimness and clearness, thus I vote for a = "normalized" distribution. </quote> Juergen > -----Original Message----- > From: Rod Johnson [mailto:rod...@in...]=20 > Sent: Sunday, March 23, 2003 5:09 AM > To: spr...@li... > Subject: [Springframework-developer] Release? >=20 >=20 > Guys, >=20 > As we had planned a release for late this month, what do you=20 > think we need to do to get 0.8 out? I think the biggest=20 > problems are probably some of the Javadoc, the lack of code=20 > examples and the lack of a tutorial. >=20 > I think the AOP stuff, except the unfinished transaction=20 > interceptor, should probably go into a release. I think it=20 > can now make 1.0, and this is worth doing, because I've had a=20 > bit of time to spend on it in the last week. >=20 > How should we structure the release? I remember there were=20 > some suggestions--were there any popular choices? >=20 > Regards, > Rod >=20 > ____________________________________________________ > Rod Johnson > J2EE Consultant and Author > +44 7973 409 132 > rod...@in... >=20 > Author of "Expert One-on-One J2EE Design and Development"=20 > (October 2002).=20 > http://www.amazon.com/exec/obidos/tg/detail/-/> 1861007841/ >=20 >=20 > Founder, Spring Framework:=20 > http://sourceforge.net/projects/springframework >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open!=20 > Get cracking and register here for some mind boggling fun and=20 > the chance of winning an Apple iPod:=20 > http://ads.sourceforge.net/cgi-> bin/redirect.pl?thaw0031en >=20 >=20 > _______________________________________________ > Springframework-developer mailing list=20 > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |