i dont see how you expect to get traction when people know there are big api breaks coming soon? why try something that will be completely broken in a week?
the people who are interested are the people who build from source, so i dont see any reason to create any publically accessible artifact. -igor On 3/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Agreed. However I think we should publish the release to the @dev crowd. So we will get some traction for our 1.3 effort. However, before we can go public with the release it should pass the ipmc, so whatever happens, it won't happen before the end of the week ;-) Martijn On 3/10/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > this is of course only for the "public" release. we should continue forward > with the ipmc release to check our legal stuff. > > -igor > > > On 3/10/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > i think we should hold off on this vote because now there is a possibility > > of all 2.0 backports making it into this branch after this release. > > > > so for now i am changing my vote to -1 until we have decided on the > > roadmap for the 1.3 branch. > > > > -igor > > > > > > On 3/7/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > > > this vote is to release 1.3beta > > > > > > -igor > > > > > > > > -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
