+0 : I'm ok with the out-of-core implementation, but I think the
related discussion about "official" vs. "unofficial" plugins must be
discussed first and a decision should be made.
For a plugin as important as this one ("important" in terms of how
many users need/use it - I don't), the Trac project should guarantee
somehow that the MasterTicket plugin will be updated and maintained,
especially when some Trac API is broken.
I'd favor moving "official" plugins back to t.e.o. so they have a
status close to the WebAdmin plugin - before it got merged to the core
- and they can be closely managed through a dedicated Trac ticket
component, along with Trac Core.
>From my perspective, there are at least 3 majors plugins out there:
AccountManager, MasterTicket and XmlRpc.
XmlRpc plugin has been broken or half-working for most of the 0.11
development cycle, and this should not happen again (and again) for
0.12.
To sum up: let's take a statement about "official" plugins before
closing those ones.
Cheers,
Manu
On Mon, Feb 25, 2008 at 5:00 PM, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:
> Are there objections to closing #31 and #886? MasterTickets implements
> the feature fairly well I think, and its big enough that I'm not yet in
> favor of core inclusion.
>
> --Noah
>
>
--
Manu
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
