I understand Patrick's stand. Tapestry 4.0 is still changing its API from beta to beta. I understand different projects have different policies on betas and RCs. Does Tapestry have a stated policy somewhere? What's the milestone for an API freezing? I can feel the frustration that a big chunk of work has to be rewritten due to an API change or deprecation.
On 11/29/05, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > > On 11/29/05, Patrick Casey <[EMAIL PROTECTED]> wrote: > > [..] > > I have to debug the Beta as well, doubling my search space. > > These are usual phrases, and this is an argument of usual debate. > Every project has different ways of thinking (which just reflect the > leading developers ideas), the general meaning around betas are > probably the one you describe but not all projects follow this path, > walk thorough the sources changes and user/developers experience and > you get the real status of a project in that precise time despite the > naming currently used. > > Didn't mention that if you found a bug and maybe even help to fix it > or you're experience help correcting a wired behaviour, you could > contribute something back to the project as well. > > Regards > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
