2012/3/6 Nicolas LE BAS <[email protected]>: > On 12-03-01 05:53 PM, Mick Semb Wever wrote: >> >> On Wed, 2012-02-29 at 17:10 -0500, Nicolas LE BAS wrote: >>> >>> - Another aspect is the web site, with 2 kinds of documentation: dev and >>> user. Dev doc needs to account for the new spin-off projects autotag and >>> request, as well as minor updates (Java 6.0...). User doc should need >>> some writing for new "request" and "autotag" projects, and only a simple >>> review for the main "framework" project. >> >> >> Can this be done post 3.0 release? Or is too much of it part of the >> maven built site which becomes fixed once 3.0 is released? > > > This is indeed the maven built site I'm talking about. But even if it were > not built by maven, IMHO documentation is an important part of a public > release. > But since release quality is determined by vote, I suppose the answer really > depends on the voters. > > >>> - updating tiles-showcase: have we even had a look at it? >> >> >> no :-/ >> Does it also need to be *in* the 3.0 release, or can it be done >> afterwards? > > > Well, it can probably be postponed. There is no technical reason to release > it at the same time, but it could help providing good examples for the doc. > I didn't look into the effort involved either. It might be easy.
Sorry for jumping in only now, but I've been really busy for both work and non-work stuff. Anyway, I suggest to release 3.0.0 as ALPHA and not beta. The reason is that, this way, an alpha release can be surely less complete than a beta and the API can change a lot because an "alpha" quality means that. About the showcase, ignore it. I tried to move it from Struts-Tiles to Tiles 2 but never managed it to do it completely. Antonio P.S. Thanks to Nicolas for the heads up.
