i am not aware of any "show-stopping" bugs, so i am ok if the next release is an RC1.
-igor On 10/20/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > alright, then we should somehow make it official. > also to communicate to "potential" users that the final release is getting > closer. > > anyway, what do the others think? (weekends are a bad time to have a lively > discussion ;) ) > > Gerolf > > On 10/20/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > > i am already in ff mode. except optimalisations like we did this few > > days. optimisations should always be right after major changes and > > freezzz > > > > On 10/20/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > > > On 10/20/07, dtoffe <[EMAIL PROTECTED]> wrote: > > > > > > > > It's not about specific bugs, it's this little "beta4" that my > > boss > > > > don't like. Stable as in "no new features or breaking changes" is > > enough, > > > > and as some less important bugs are found, some bugfix could be > > released > > > > as > > > > 1.3.01 for example. > > > > > > > > > > thank you daniel, that's exactly what i meant. even though there already > > > people using the betas to build great applications, > > > a final release could allow even more folks to use wicket and thus a > > higher > > > adoption and penetration of the market. > > > > > > and as johan said: > > > > I am really curious what bugs are really stopping people for using the > > > current build... > > > > > > so how about the feature freeze and 2-3 RCs? > > > bugs can be fixed for 1.3.1 and api breaks go directly into TNG. > > > > > > let's hop on the 1.4-train ;) > > > > > > Gerolf > > > > > >
