Trac 1.0.13 Released

19 views
Skip to first unread message

Ryan Ollos

unread,
Sep 11, 2016, 5:59:05 AM9/11/16
to Trac Users, trac...@googlegroups.com
Trac 1.0.13 Released 
====================

Trac 1.0.13, the latest maintenance release for the
current stable branch, is available. 

You will find this release at the usual places: 


Trac 1.0.13 provides around a dozen fixes and minor
enhancements.

You can find the detailed release notes for 1.0.13
on the following pages:

Now to the packages themselves: 

URLs:


MD5 sums: 

7c6d32a6f65f27d372b0a29a8b3227e5  Trac-1.0.13-py2-none-any.whl
739dd6c2bd4aa09904cc667c41bc151c  Trac-1.0.13.tar.gz
e4cd4866dc2d203e5f903d7331ebf59f  Trac-1.0.13.win32.exe
3ed8d0c5a9502d0dbb8b249c225d1a39  Trac-1.0.13.win-amd64.exe
dd2d31b4cc1c5ea7bf05fd46ac30732e  Trac-1.0.13.zip

SHA1 sums: 

95c4dc332236f99d198a8e9887c32d513d1a08d2  Trac-1.0.13-py2-none-any.whl
3157f38233c80fe76246e8a30584ca0efac89e51  Trac-1.0.13.tar.gz
c3e9a86ebbf2c19e4e8caad039ddf323667b0677  Trac-1.0.13.win32.exe
df51a19ffd208bd5664a667e239b2ba63fdeced0  Trac-1.0.13.win-amd64.exe
694d994e0f904639f55b1e7ed1e2bd611fb71f93  Trac-1.0.13.zip

Acknowledgements 
================ 

Many thanks to the growing number of people who
have, and continue to, support the project. Also
our thanks to all people providing feedback and bug
reports that helps us make Trac better, easier to
use and more effective. Without your invaluable help,
Trac would not evolve. Thank you all. 

Finally, we hope that Trac will be useful to like-minded
programmers around the world, and that this release will
be an improvement over the last version.

Please let us know.

Greg Troxel

unread,
Sep 11, 2016, 11:46:38 AM9/11/16
to Ryan Ollos, trac...@googlegroups.com

Thanks for making the release.

I am cleaning up notes in pkgsrc's control file, and wonder a few
things:

Trac 1.0 is documented not to support python 3, and the package notes
this in a comment. Still true?

The package supports sqlite3 and pgsql via pyscopg2. I use pgsql.
The package notes that mysql is not recommended by upstream. Is that
still a fair statement?
signature.asc

RjOllos

unread,
Sep 11, 2016, 3:42:56 PM9/11/16
to Trac Development, rjo...@gmail.com


On Sunday, September 11, 2016 at 8:46:38 AM UTC-7, Greg Troxel wrote:

Thanks for making the release.

I am cleaning up notes in pkgsrc's control file, and wonder a few
things:

  Trac 1.0 is documented not to support python 3, and the package notes
  this in a comment.  Still true?

There is still not support for Python 3. Python 3 support may be coming with Trac 1.3.x.
 
  The package supports sqlite3 and pgsql via pyscopg2.  I use pgsql.
  The package notes that mysql is not recommended by upstream.  Is that
  still a fair statement?

 I can see why MySQL was not recommended at one time, but support is pretty good now so I think you could remove that statement.

- Ryan

Greg Troxel

unread,
Sep 11, 2016, 7:33:44 PM9/11/16
to RjOllos, Trac Development

RjOllos <rjo...@gmail.com> writes:

>> Trac 1.0 is documented not to support python 3, and the package notes
>> this in a comment. Still true?
>
> There is still not support for Python 3. Python 3 support may be coming
> with Trac 1.3.x.

Thanks. I didn't mean to complain -- more that I was checking that I was
not confused.

>> The package supports sqlite3 and pgsql via pyscopg2. I use pgsql.
>> The package notes that mysql is not recommended by upstream. Is that
>> still a fair statement?
>
> I can see why MySQL was not recommended at one time, but support is pretty
> good now so I think you could remove that statement.

OK - I have softened it:

# Upstream has MySQL support but there are significant caveats:
# https://trac.edgewall.org/wiki/MySqlDb
# Anyone is welcome to add a (tested!) mysql option.

The bit about charsets scares me slightly, so I'm leaving it for someone
who wants to run it to test on NetBSD. I find that pgsql works great
(and has for a really long time), so I'm personally sticking with it.
signature.asc

RjOllos

unread,
Sep 12, 2016, 1:33:03 AM9/12/16
to Trac Development, rjo...@gmail.com
I'd be interested to hear what other have to say, but I haven't any significant problems in the two MySQL sites that I've run with recent Trac 1.0.x releases. In most cases I think users will be okay if they run with the recommended storage engine, charset and collation. My understanding is that the options will just be expanded with #12363.

The number of PostgreSQL issues (1) is comparable to the number of MySQL issues (2). The only major issue I've run into is #12390; it can be worked around and is probably rarely encountered.

I would rather run PostgreSQL, but that's just a personal preference and matter of familiarity.

- Ryan

Reply all
Reply to author
Forward
0 new messages