Hello,

There was a discussion thread a few months back where someone made
note that the `highlights` in the 'Trac 0.11.5 Released' email [1]
could have included some additional fixes/features to make upgrading
much more appealing.  I can't find that message thread, but I have a
few suggestions:

 1. Include a link in the email that directs to a custom query showing
all tickets closed for the 0.11.5 milestone.  I have made an attempt
at creating the proper query [2].  Even better, perhaps include one
link to defects [3] and another to enhancements [4].

 2. I went through the list of defects and enhancements today for the
0.11.5 milestone.  As someone who is a primarily an end-user and admin
(which probably accounts for the majority of those who would be
looking at the release notification and considering whether or not to
upgrade), I found the following issues [5 - 12] most interesting,
because they affect functionality or behavior in Trac from a user or
administrator standpoint.  In contrast, there are several issues that
only a developer would care about because they don't result in a
feature or behavior change, and there where several issues for bugs
that I wasn't experiencing (e.g. specific to a database back-end).
Finally, there where a few security related permissions issues that
interested me.

I wouldn't have know about them if I did not a) run the aforementioned
query and read through the tickets OR b) follow the Trac user and
developer mailing lists, and timeline, on a daily basis (therefore I'm
probably considered a 'power user' or 'power admin' and more of an
exception in terms of amount of time spent per week following the Trac
project).  Of course, the developers put in much more time, but just
considering the typical admin, user, or someone responsible for user
training ...

Just my thoughts ...

- Ryan

[01] http://groups.google.com/group/trac-dev/browse_frm/thread/1bb933250097404a
[02]
http://trac.edgewall.org/query?status=closed&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&milestone=0.11.5
[03]
http://trac.edgewall.org/query?status=closed&order=priority&col=id&col=summary&col=milestone&col=status&col=owner&col=type&col=priority&milestone=0.11.5&type=defect
[04]
http://trac.edgewall.org/query?status=closed&order=priority&col=id&col=summary&col=milestone&col=status&col=type&col=owner&col=priority&milestone=0.11.5&type=enhancement
[05] http://trac.edgewall.org/ticket/8309
[06] http://trac.edgewall.org/ticket/5718
[07] http://trac.edgewall.org/ticket/7209
[08] http://trac.edgewall.org/ticket/8252
[09] http://trac.edgewall.org/ticket/8234
[10] http://trac.edgewall.org/ticket/8290
[11] http://trac.edgewall.org/ticket/8253
[12] http://trac.edgewall.org/ticket/8410

--~--~---------~--~----~------------~-------~--~----~
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