Noah Kantrowitz wrote:
> On Sep 16, 2006, at 7:16 PM, Ilias Lazaridis wrote:
> > Christian Boos wrote:
> >> Norbert Unterberg wrote:
> >>> 2006/9/14, Christian Boos <[EMAIL PROTECTED]>:
> >>>
> >>>> The syntax would be [#Title1 See section 1], as this would work
> >>>> anywhere, not only on Wiki pages.
> >>>>
> >>>> This change has no adverse effects, AFAICT.
> >>>
> >>> Does that mean you could add that patch to trunk and the upcoming
> >>> 0.10? It would be nice if it could be included in the latest
> >>> versions.
> >>
> >> We try to be conservative about new features close to a release.
> >> But in
> >> this case, one must really try hard to see that change as a
> >> disruptive
> >> one ;)
> >> So yes.
> >
> > The functional addition discussed here  (sidenote: I welcome this
> > addition) is non-disruptive, and _can_ go into 0.10..
> >
> > But: The following ticket discusses a defect within the html
> > presentation and _cannot_ go into 0.10, even if it is totally
> > non-disruptive. I was even asked to not file tickets for 0.10:
> >
> > http://trac.edgewall.org/ticket/3730
> >
> > Is there any reason for this "selective ruling"?
>
> This neither removes nor changes any existing functionality, and so
> is hard to see that anyone would object to it. I list the 'Trac' tag
> in the title of each page, and would argue against its removal. One
> is also a functional issue that breaks an existing convention, the
> other is purely aesthetic.

I understand your point of view.

My question subjects the "feature freeze", which should be applied
_strictly_.

Possibly the team can point me to a document which describes the
feature-freeze for 0.10 and the related rules.

.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to