Hello again,
This is the last part of the examination of the remaining
tickets for 0.11.
jonas tickets
=============
Well, as jonas is still the "default" owner for most
components, he gets the bunch of tickets that nobody wants
:-)
#4716: Prepare documentation for 0.11
--------------------------------------
A big topic in itself, which was rehashed many times...
Well, whatever form takes the documentation for 0.11, there's
a big effort to make in that area. Anyone can contribute.
#5573: "is not" option in ticket query not functioning
------------------------------------------------------
Well, I can't reproduce that one.
#6135: Enhancement for trac-post-commit-hook.py for
Enterprise Workflow
---------------------------------------------------
Propose to postpone to 0.11.1, as it's a valid enhancement
idea, but it should be done in the default script in a more
modular way, like associating keywords to states.
#3965: emailed ticket footers don't have url info in them.
----------------------------------------------------------
Mainly a documentation issue about the need for the setting
[trac]
base_url = ...
which became mandatory. For this usage ("reference" URL for
a ticket within an e-mail), I think there's a consensus that
this setting has to be specified explicitly and not deduced
from the req.
Related to #5064.
#4315: Project should use it's own results (0.11dev should be
on t.e.o)
-------------------------------------------------------------
Well, there shouldn't really be a ticket for that... but
let's talk about that point as well. I suggest that we do
the switch to 0.11dev as soon as the context refactoring is
done and #5025 is fixed.
#5595: [PATCH] Errors in the log file for optional components
-------------------------------------------------------------
Has a trivial patch:
http://trac.edgewall.org/attachment/ticket/5595/log_spam_fix.patch
Not to nit pick, but I nevertheless think a ''warning'' level
would be more appropriate, as it's somewhat difficult to know
from within Trac if the package was not installed on purpose
or because there was some installation issue.
#6013: [PATCH] Support X_FORWARDED_PROTO header
-----------------------------------------------
Has a patch, but there's been some arguments provided by
cmlenz that this shouldn't be necessary. The topic is also
somewhat related to #5064. Whatever is the final word on the
subject, I think this can be safely postponed to 0.11.1.
#6043: Trunk jQuery crashes safari 2.0 and older
------------------------------------------------
... which boils down to the question of which jQuery version
we should pick. The latest as of this writing is 1.2.1. If
there are compatibility issues with 1.2.x, there's also a
1.1.4 release (currently we bundle 1.1.3.1). And by looking
at:
http://docs.jquery.com/Release:jQuery_1.2#Removed_Functionality
it seems that we're hit by compatibility issues in a few
places. So I see 3 options:
1. fix the compatibility issues
2. use the compatibility plugin
3. stay with 1.1.4
I'd say 1. can wait for 0.11.1 and 3. seems the easiest
option at this point. Any of those would require extensive
testing, of course.
#6059: Add stricter user guidelines for creating new tickets
on t.e.o
------------------------------------------------------------
This is something that is really badly needed, and could have
been done since a long time already by making the big red box
<blink> :P
But a nicer solution would be possible once t.e.o gets
upgraded to 0.11dev: the ''View Tickets'' tab could be
redirected to a NewTicketGuidelines wiki page.
http://trac.edgewall.org/ticket/6059#comment:3
#6112: Update InterTrac definition list on t.e.o. to support
edgewall.org -hosted projects
------------------------------------------------------------
cmlenz? jonas?
I'd suggest using:
[intertrac]
Babel.title = The Babel project at Edgewall
Babel.url = http://babel.edgewall.org/
Babel.compat = false
Bitten.title = The Bitten project at Edgewall
Bitten.url = http://bitten.edgewall.org/
Bitten.compat = false
ba = Babel
bi = Bitten
Also, given the 0.9 Tracs tend to be rare now, I'd suggest
that the default value for .compat should now be "false"
(.compat=true means stay compatible with targeted Trac older
than 0.10, i.e. don't create /intertrac/... URLs).
#5535: [inherit] not working for me
-----------------------------------
Has a patch, but it probably be needs to be updated to recent
trunk. From the comment of osimons, it looks like the ticket
has to be focused to only emit the appropriate warnings when
the specified inherited .ini files are not found.
#6185: Trac could be released with a different color and logo
theme
-------------------------------------------------------------
This ticket is two fold. First, the general topic of
"theming" would be interesting to deal with in a more
comprehensive way, like described in Armin Ronacher's
ThemePlugins proposal
(http://trac.edgewall.org/wiki/TracDev/Proposals/ThemePlugins).
But this is probably not something that can be addressed for
0.11, as Noah and Manu reminded me ;-)
So, there could be some simpler changes done in the meantime,
like simply shipping a different Trac Logo.
(There was also #5941 in the list, but I'm currently working
on it and it should be fixed in the meantime)
Finally, special mention to #5064 (base_url considered
harmful), which is currently scheduled for 0.10.5, but which
should be sorted out for 0.11 as well, I think. Hopefully
it's only a setup problem and once we have a correct
documentation in place, we can trust the 'HTTPS' setting
again and revert r5642.
See http://trac.edgewall.org/ticket/5064
Et voilà ! Thanks for reading so far and thanks in advance
for the feedback.
Oh, I nearly forgot: there *might* still be untriaged tickets
and 0.11.1 tickets that would be really worth doing for 0.11.
Don't hesitate to bring the discussion up if you have such
a ticket in mind.
-- 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
-~----------~----~----~----~------~----~------~--~---
