On Dec 30, 2006, at 5:56 AM, whit wrote:
I think representing releases as binarily UI focussed or
infrastructure focused does a bit of disservice to past
discussions. The idea was more to have release that focused on new
feature alternate with ones that did the needful and cleaned up
accr
Personally, I never liked the separation of infrastructure/UI-focused
releases, and it was also something that was never voted on or
accepted as the way to go — it was just suggested. But if there is an
alternating schedule, 3.0 is definitely the UI release, not the
infrastructure release. ;)
Wichert Akkerman wrote:
- January 7th : final bundles merged
- January 21st : first beta release
- March 11th : first release candidate
- April 23rd : release
And here is a problem: I learned this week thatthere is a UI sprint
scheduled for February. I do not want to see any non-small
On 12/29/06, Wichert Akkerman <[EMAIL PROTECTED]> wrote:
Talking with limi he appears to be in favour of the second option: he
considers it critical that 3.0 has a very polished modern UI. Personally
I have a slight preference for the first option: we have landed an
awesome amount of changes and
Previously Martin Aspeli wrote:
> I guess my counter-proposal would be:
>
> - January 7th : final bundles merged
> - January 21st : first beta release
> - March 11th : first release candidate
> - April 23rd : release
And here is a problem: I learned this week thatthere is a UI sprint
sch
