On 11/22/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > As a Struts project, once Shale gets to a General Availablility release > (which *definitely* won't be true for at least the first few milestones), it > will share the Struts community passion for backwards compatibility. > However, even today, the documentation will include an indication of API > stability for each individual package, so you can focus on the parts of > Shale you plan to take advantage of. (This section seems to have gotten > dropped from the javadocs, so I'm going to pull it out as a separate page in > the website.) >
Just added the API stability page to the website: http://struts.apache.org/struts-shale/api-stability.html It also attempts to categorize the packages based on whether they are appropriate for *application* developers versus those that are trying to extend the *framework* itself. Craig
