Hi,

I agree with Simon that it seems to be a bit rush to have the next release in one or two weeks. Getting user feedback from 0.90 release and figuring out what's next would take some time. But if we have specifc features that can be achieved soon, I'm OK with it. One thought: would it be possible that we add such features to 0.90 branch instead of creating a new one out of the trunk?

Thanks,
Raymond

----- Original Message ----- From: "Simon Nash" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, May 31, 2007 5:10 AM
Subject: Re: 0.91 release?


It's good to do more frequent releases than we did in the past.  I'm not
sure about cutting a branch only a week or 2 after delivering the previous
release.  Maybe we should let 0.90 get out there and give it enough time
for people to download and use it and give their reactions, so that we
have some user feedback on 0.90 before we decide what should be in the
next release.

  Simon

ant elder wrote:

With the 0.90 release almost out how about starting on 0.91? Its been almost
3 weeks since the code chill for 0.90, be good if we could start doing
releases much more regularly and 4 - 6 weeks for a small point release seems good to me, so how about aiming for cutting an 0.91 branch in a week or 2?
The main things I'd like to get out are the improvements to the scripting
scripting support with optional .componentType sidefiles and dynamic
interfaces, and the ajax binding and jsonrpc binding simplification and
unification. With those, the new feed binding and the port of the aggregator
sample that would give 0.91 a sort of web20/scripting focus, and doing it
quick like this should make it relatively easy to get done by using the
trunk stability from 0.90.

  ...ant




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to