AW: [Shale] API Stability vs. V1.0

2006-02-01 Thread Bernhard Slominski
> -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag > von Craig > > Of course right now it's not possible to tell which release > it is or when > > this is. > > Not really at this point ... but feedback on that topic, as > well as general > usage comm

Re: [Shale] API Stability vs. V1.0

2006-01-31 Thread Craig McClanahan
On 1/31/06, Bernhard Slominski <[EMAIL PROTECTED]> wrote: > > > > -Ursprüngliche Nachricht- > > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag > > von Craig > > McClanahan > > > > Shale follows the same version branding policy that the rest > > of Struts does > > (along with Tomca

AW: [Shale] API Stability vs. V1.0

2006-01-31 Thread Bernhard Slominski
> -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag > von Craig > McClanahan > > Shale follows the same version branding policy that the rest > of Struts does > (along with Tomcat and some other projects). An "x.y.z" > release is first > issued with

Re: [Shale] API Stability vs. V1.0

2006-01-31 Thread Craig McClanahan
On 1/31/06, Bernhard Slominski <[EMAIL PROTECTED]> wrote: > > Hi all, > > I am a bit confused about the versioning and the API stability. > So the current Version of Shale is 1.0.1 (according to the API > documentation), so a 1.0 version. Shale follows the same version branding policy that the re

[Shale] API Stability vs. V1.0

2006-01-31 Thread Bernhard Slominski
Hi all, I am a bit confused about the versioning and the API stability. So the current Version of Shale is 1.0.1 (according to the API documentation), so a 1.0 version. However the API stability (http://struts.apache.org/struts-shale/api-stability.html) tell a different story, from the 32 package