Jeroen Ruigrok van der Werven wrote:
> -On [20071128 19:54], Christian Boos ([EMAIL PROTECTED]) wrote:
>   
>> ... that means we're getting closer to a beta1 release. I think trunk 
>> will stabilize a bit now, as there's no big remaining code changes that 
>> should really go in before the beta1 (correct me if I'm wrong).
>>     
>
> Can't we just declare a formal feature freeze on trunk now until 0.11 has been
> released

We could, but I think everyone is already aware of the informal freeze...

I take this opportunity to summarize the "big remaining changes" that 
are still scheduled for 0.11:

#5954      Can't use prototype in plugins as $ conflicts with jquery

There's a patch, but its somewhat big and I would have liked to get some 
feedback on it. I'm somewhat reluctant to commit as-is, as I have the 
feeling it can be done in a better way. So it'll probably be a 0.11.1 or 
even 0.12 thing.

#6374      [PATCH] Provide a cleaner way to override macros

This would require quite some work and probably introduce some 
instabilities.
So like the above one, probably be a 0.11.1 or 0.12.

#6185      Trac could be released with a different color and logo theme

It could... but I'm somewhat -0 on that, as I think it risks to disturb 
a lot the people who are used to (and like) the default look'n'feel. 
Changing that at the last minute will upset many. If we insist on a 
different visual identity, let's do that on t.e.o. Anyway, I think #6059 
will do a lot more for preventing "Wrong Trac" tickets than this.

#4716      Prepare documentation for 0.11

Of course that will still involve lots of changes, but none that should 
introduce instabilities. Part of the documentation updates, I'll try to 
merge soon my apidoc work, as it contains lots of docstring updates.


In addition to that, I'd like to add #5979 to the lot, which together 
with with the components restructuring discussed before, will allow us 
to list all ticket subsystem related ticket, all versioncontrol related 
ones, etc.

Finally, I'd like to propose a minor cosmetic fix, which is to set the 
border width of the query filters / column selector fieldsets to 0 when 
collapsed. I think this looks much nicer than an empty fieldset page wide.

-- Christian


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to