Re: [Trac-dev] Authentication Issue

[Ryan Ollos]

On Mon, Jun 26, 2023 at 10:21 PM Mahima Khandagale <
mahima.khandag...@abmra.in> wrote:

> How to fix authentication issue if we running  project on standalone
> server ?
>

and please explain in more detail the issues you are encountering. It's
really hard to help with you just say you have an authentication issue
without any additional information about your configuration or the behavior
encountered.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CA%2BBGpn8DmLS82tQm_sCQ1LU7e16W7ZeVSAm%2BLyZGXiUjsqkd%2Bg%40mail.gmail.com.

[Trac-dev] Trac 1.5.3 Released

[Ryan Ollos]

Trac 1.5.3, the latest development release leading up to Trac 1.6, is
available.

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#LatestDevRelease

You can find the detailed release notes for 1.5.3 on the following
pages:
https://trac.edgewall.org/wiki/1.5/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.5#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.5.3.tar.gz
https://download.edgewall.org/trac/Trac-1.5.3-py3-none-any.whl
https://download.edgewall.org/trac/Trac-1.5.3.win32.exe
https://download.edgewall.org/trac/Trac-1.5.3.win-amd64.exe

MD5 sums:

439699f9a2317408f5f69f93770635d1  Trac-1.5.3.tar.gz
724aa9b64607b63755765017942b01fa  Trac-1.5.3-py3-none-any.whl
54d5bbe6e56dabd110e8867e0815d0d8  Trac-1.5.3.win32.exe
902f2b0f8ccbe99ec191ac8c72f6e836  Trac-1.5.3.win-amd64.exe

SHA256 sums:

699f5dd3ce82fb7138c726ef55a653f09531823e26170a1fb4d71d31b4adeaa5
 Trac-1.5.3.tar.gz
48278ef2c4bc2cf3c6f01e010602aa761c63051494fc222a10d5ed72e84162b5
 Trac-1.5.3-py3-none-any.whl
165f78f416f12c8a39ee026107c48597f0f85e9922195d15ba0f4c8226a3cb8e
 Trac-1.5.3.win32.exe
636da3243c1941a5fa6e5d69c959764e3af2a9a5fd406024332c03fdcdb9a71c
 Trac-1.5.3.win-amd64.exe

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 help 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.

/The Trac Team https://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CA%2BBGpn-i1_1hYQKSUUVjybcUo8%3D_kBA367T10iueQ1JPfx01dw%40mail.gmail.com.

[Trac-dev] Trac 1.4.3 Released

[Ryan Ollos]

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

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#Trac14StableRelease

You can find the detailed release notes for 1.4.3 on the following
pages:
https://trac.edgewall.org/wiki/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.4#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.4.3.tar.gz
https://download.edgewall.org/trac/Trac-1.4.3-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.4.3.win32.exe
https://download.edgewall.org/trac/Trac-1.4.3.win-amd64.exe

MD5 sums:

c0c154ae596f2d84fc520055a26aaaef  Trac-1.4.3.tar.gz
43f933322b8055d2f5f1b5e300c90f6c  Trac-1.4.3-py2-none-any.whl
60828276e33c5ffe8fddda9317313f9d  Trac-1.4.3.win32.exe
6a09a47847347eda1214b1e4de8ab82b  Trac-1.4.3.win-amd64.exe

SHA256 sums:

c93ceed9abee6e3c7789f469862e82a3b9bf3405be73aae3221b5c259e062d21
 Trac-1.4.3.tar.gz
9ccd0b998e41e6c989b0ae8d61ed2f8d5ad62616d430eed8d1f20d0e34446700
 Trac-1.4.3-py2-none-any.whl
ea8d17502957edf8ab437b6cc16d6c5e6e77f9df88238e02146427a179489a16
 Trac-1.4.3.win32.exe
2f8b77570a389334220470febc88f8121852240be4e350ae5da054246dc7a7e8
 Trac-1.4.3.win-amd64.exe

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 help 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.

/The Trac Team https://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CA%2BBGpn_fEycJ2keYbSsG8Pih1xzR0pEawD_ux5zL%2BhwDCb%2BxLQ%40mail.gmail.com.

Re: [Trac-dev] Selenium GUI tests

[Ryan Ollos]

On Fri, May 29, 2020 at 11:40 AM Bhavesh Patel  wrote:

> Hello,
>
> Sorry about mass reply to release email. I have development environment
> setup and ran the tests. I am thinking of writing Selenium
> driven GUI tests for Trac if there is any value in it that Twill can't
> provide.
>
> If Selenium tests are a good idea then, I welcome thoughts on what to test
> first or where to focus my efforts so that product is made better.
>
> Thanks,
> Bhavesh Patel
>

Thanks for your interest and offer to help.

We've switched to Selenium in our Python 3 branch. We're working out a few
issues and the work should land on trunk soon.

https://trac.edgewall.org/ticket/11988

If you are interested in improving Trac, the "bitesized" issues might be a
good place to start:
https://trac.edgewall.org/query?status=assigned=new=reopened=~bitesized=id=summary=status=type=priority=milestone=component=priority

I haven't reviewed the list in a while. Some of those may be incorrectly
classified. If something looks interesting, it might be good to discuss on
mailing list before proceeding to produce a patch.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CA%2BBGpn-CWTCw653aLMueHb1OrnQu1PhcAtgK8O6mYxO94WhLRg%40mail.gmail.com.

[Trac-dev] Trac 1.4.1 Released

[Ryan Ollos]

Trac 1.4.1 Released


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

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#Trac14StableRelease

You can find the detailed release notes for 1.4.1 on the following
pages:
https://trac.edgewall.org/wiki/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.4#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.4.1.tar.gz
https://download.edgewall.org/trac/Trac-1.4.1-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.4.1.win32.exe
https://download.edgewall.org/trac/Trac-1.4.1.win-amd64.exe

MD5 sums:

0a785e0c7a50f81ae571f7ddb98b9cc0  Trac-1.4.1.tar.gz
633dbb6258199570f69535bef7dcd256  Trac-1.4.1-py2-none-any.whl
71c0cc64f8e992787ff0ed03d7c106cc  Trac-1.4.1.win32.exe
8d605056297a6438c96fa37eb8c0edcd  Trac-1.4.1.win-amd64.exe

SHA256 sums:

dfab4660df2b4d912e4ae36b40dbf4d2718df49177c89542408b2709ecf5c134
 Trac-1.4.1.tar.gz
306aa895fbb33958b5b58b3a4265d2437cadb84387d65bb68bd0f6259a0c5948
 Trac-1.4.1-py2-none-any.whl
b5b15175a70ce4e145980c07cba043e37d4a1025cbd2688c97a2511213ed7628
 Trac-1.4.1.win32.exe
abebec234200ac7f9aaa08ac220a32d235dcee009d1814929ecea927bd6fa339
 Trac-1.4.1.win-amd64.exe

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.

/The Trac Team https://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CAOKhaj3H60cZzz15gpf8yp4CVeoEdoJCndgJkzcvReg_NMM5fQ%40mail.gmail.com.

Re: [Trac-dev] How to remove the adoption request box

[Ryan Ollos]

On Sat, Nov 23, 2019 at 8:12 AM Theodor Norup 
wrote:

> Hi
>
> How can I remove the adoption request box from the top of
> https://trac-hacks.org/wiki/TracBacklogPlugin?
>
> BR Theodor
>

I added you as the project owner and the message is gone now.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CA%2BBGpn-ZbOEOLRL%2BGSaJtxLEE%3Dxng%3D853PkpgLUa0W_DBy6Ybg%40mail.gmail.com.

Re: [Trac-dev] Trac 1.3.6 and Trac 1.4 releases

[Ryan Ollos]

On Wed, Aug 14, 2019 at 8:31 AM Tawanda Gwena  wrote:

> I can test the 1.3.6 if you detail what you would like to see in the
> testing.
>

Ideal would be some real-world testing. Mirror production environment to
staging and upgrade to 1.3.6. Evaluate the new Trac, looking for anything
incorrect or abnormal and test plugins.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/trac-dev/CA%2BBGpn_THyCdy82PLHZ-fOFUpzTNzo349Av-_55JY5-EzpwVLw%40mail.gmail.com.

Re: [Trac-dev] Plans

[Ryan Ollos]

On Sun, Mar 3, 2019 at 2:33 PM 'Brian DeRocher' via Trac Development <
trac-dev@googlegroups.com> wrote:

> Hey Folks,
>
> I've been using Trac for over 10 years.  There are a few things I need to
> know as I decide if I'll continue to use it.
>
> 1. Any plans for switching the codebase from subversion to git?
>

The codebase has multiple Git mirrors:

https://trac.edgewall.org/browser/mirror
https://bitbucket.org/edgewall/trac/commits/all
https://github.com/edgewall/trac


> 2. Any plans for making the website mobile friendly (responsive)?
>

No concrete plans that I've seen.


> 3. Any plans for moving PullRequestsPlugin into core?
>

No concrete plans that I've seen.


> I see the plans for Python 3 in the previous thread.
>
> Thanks,
> Brian
>
> --
> You received this message because you are subscribed to the Google Groups
> "Trac Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to trac-dev+unsubscr...@googlegroups.com.
> To post to this group, send email to trac-dev@googlegroups.com.
> Visit this group at https://groups.google.com/group/trac-dev.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.2.3 Released

[Ryan Ollos]

Trac 1.2.3 Released
===

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

You will find this release at the usual places:

*https://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
*
https://pypi.python.org/pypi/Trac/1.2.3

You can find the detailed release notes for 1.2.3
on the following pages:
https://trac.edgewall.org/wiki/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.2#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.2.3-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.2.3.tar.gz
https://download.edgewall.org/trac/Trac-1.2.3.win32.exe
https://download.edgewall.org/trac/Trac-1.2.3.win-amd64.exe

MD5 sums:

340d90177a00f7a9a4ebfad221375155  Trac-1.2.3-py2-none-any.whl
7d430c8769cd21bdbcd7222e4cabc9ee  Trac-1.2.3.tar.gz
be7186dfb0428a381f4d75383d9c9ea9  Trac-1.2.3.win32.exe
88129a2397ce78eebd86de3a67671359  Trac-1.2.3.win-amd64.exe

SHA1 sums:

d29f715aa9421cb7496d4c70dbdd363ac6a397ca  Trac-1.2.3-py2-none-any.whl
b426e8af41adef1d82709e23b771e24dbff8a0b2  Trac-1.2.3.tar.gz
6c7681edf6c2642bd5c621db1b2521e74d5d13ce  Trac-1.2.3.win32.exe
6288cbed2bbd574aad252160764ba5d9dbdc1d57  Trac-1.2.3.win-amd64.exe

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.

/The Trac Team https://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.3.3 Released

[Ryan Ollos]

Trac 1.3.3 Released


Trac 1.3.3, the latest development release leading up
to Trac 1.4, is available.

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#LatestDevRelease

You can find the detailed release notes for 1.3.3
on the following pages:
https://trac.edgewall.org/wiki/1.3/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.3#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.3.3-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.3.3.tar.gz
https://download.edgewall.org/trac/Trac-1.3.3.win32.exe
https://download.edgewall.org/trac/Trac-1.3.3.win-amd64.exe

MD5 sums:

22a4af92055f6aa3aab455dae6a9ec32  Trac-1.3.3-py2-none-any.whl
ad156bfb7ac1ae04265fd81c4c64f333  Trac-1.3.3.tar.gz
41d88efa8e30dee3d75ea0473856700d  Trac-1.3.3.win32.exe
f40f10c3ea42dd51c3792d9568885fd6  Trac-1.3.3.win-amd64.exe

SHA1 sums:

b9029a5b552d3b6ea7d103f2f735c4d3d8a885a9  Trac-1.3.3-py2-none-any.whl
9ec984ee4a6e84af5eed999ec62c2a87f651c6aa  Trac-1.3.3.tar.gz
27a77680214e9e989b505ff67beeea4d173298be  Trac-1.3.3.win32.exe
c2fcd37e2d558cc3895edc7905effb4a4a379200  Trac-1.3.3.win-amd64.exe

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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.17 Released

[Ryan Ollos]

Trac 1.0.17 Released


Trac 1.0.17, the latest maintenance release for the
older stable branch, is available.

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#PreviousStableRelease
https://pypi.python.org/pypi/Trac/1.0.17

You can find the detailed release notes for 1.0.17
on the following pages:
https://trac.edgewall.org/wiki/1.0/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.0.17-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.0.17.tar.gz
https://download.edgewall.org/trac/Trac-1.0.17.win32.exe
https://download.edgewall.org/trac/Trac-1.0.17.win-amd64.exe

MD5 sums:

9628385ce962ed6e0fc96eb70596ffbe  Trac-1.0.17-py2-none-any.whl
11cb40155bb7f52baf1b7ea93cdef326  Trac-1.0.17.tar.gz
d70777c292827c406ce95a8598183a10  Trac-1.0.17.win32.exe
a976a1c065374c3137dac84f4b91264f  Trac-1.0.17.win-amd64.exe

SHA1 sums:

1245b872ec298c8996c20f0cdb334259ae4059ff  Trac-1.0.17-py2-none-any.whl
98f2b5d9b7ff7230b18ea47b6f82220dd59b6a92  Trac-1.0.17.tar.gz
4ad5745c509fa19436241f28fa3d9e9b7f6f7eb6  Trac-1.0.17.win32.exe
2c2ed51f598e9ee6fe9b5c28de4a4e947833cd63  Trac-1.0.17.win-amd64.exe

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.

/The Trac Team https://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trying to set up development environment

[Ryan Ollos]

On Sat, Jun 2, 2018 at 11:50 AM, Fred Leeflang  wrote:

> Hi guys,
>
> I'm trying to set up a development environment and following https://trac.
> edgewall.org/pysqlite.org-mirror/wiki/TracDev/DevelopmentEnvironmentSetup
>
> I got stuck on creating the Trac environment. After the bunch of
> pip/svn/git checkouts there's apparently no trac-admin in my pve
> environment. Is there perhaps a step missing in the doc?
>
> -Fred
>

The doc looks correct to me.

If the following doesn't work:
$ pip install -e trac-trunk

Try:
$ cd trac-trunk
$ python setup.py develop


If that doesn't work, please describe your platform and the steps you
performed.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Translator introduction

[Ryan Ollos]

On Fri, May 18, 2018 at 6:28 PM, Lucas Larson 
wrote:

> Hi all,
>
> Ryan J Ollos  saw that
> I’d requested to join the Esperanto Trac translation team and asked that I
> introduce myself. My participation to works using Trac has been low, but
> I’ve been lurking on WebKit’s Trac  for over 10
> years now and I know how Trac works.
>
> Saluton al ĉiuj,
>>
>
>
> Ryan J Ollos  vidis ke
>> mi petis aliĝi la teamon de tradukistoj de Trac al Esperanto, kaj petis, ke
>> mi min prezentu. Mia partopreno al laboroj, kiuj uzas Trac‑on estis
>> malalta, sed mi kaŭris ĉe la Trac de WebKit  ekde
>> nun pli ol 10 jaroj, kaj scias mi, kiel Trac funkcias.
>
>
> Thank you,
>
> Lucas
>

Welcome, Lucas, and thank you for contributing to the translation on
Transifex!

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Dutch and Vietnamese Translations

[Ryan Ollos]

On Thu, May 17, 2018 at 3:10 AM, Fred Leeflang  wrote:

> Hi,
>
> I recently volunteered and signed up for transifex. We, 3DN, are a (very)
> small company in the Netherlands with a daughter company in Vietnam.
>
> I think it would be very nice to have Dutch and Vietnamese locales for
> Trac.
>
> -Fred
>

Hi Fred,

Welcome to the Trac project via Transifex. I'm not too familiar with
Transifex, but I hope you will raise any questions that come up and we'll
try to help. Adding any additional languages would be welcome.

Sometime in the near future we will start pulling the translations from
Transifex with each release, once again. It's long overdue.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Very quiet

[Ryan Ollos]

On Tue, May 22, 2018 at 6:16 AM, Samuli Seppänen  wrote:

> Il 22/05/2018 11:24, Fred Leeflang ha scritto:
> > Is it possible to have a bit of a status post on the Trac project? I
> have not read so much through the archives yet so I'm not sure what's up,
> but I get the impression that it's extremely quiet. I know from experience
> that doesn't always mean nothing is happening but am I right to assume that
> at least at this point in time it's mostly Ryan doing the work in Trac?
> >
>
> I see a reasonable amount of activity in SVN logs:
>
> https://trac.edgewall.org/log/
>
> Two core developers right now it seems. I guess development discussions
> happen mostly outside the Trac-dev list.
>
> Samuli


Additionally, the timeline presents a view of project activity:
https://trac.edgewall.org/timeline
https://trac-hacks.org/timeline

Next releases should be coming by end of this month or early June.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Running Trac as a Windows service

[Ryan Ollos]

I'd like to revise the "Installing as a Windows Service" section of
TracStandalone (1). In general, I think we should provide one good option
in the official documentation rather than several options. Users can
provide other ways of doing the same in the Trac CookBook.

I answered a question on Stack Overflow (2) and found the nssm tool was
easy tool use and works well for running tracd as a windows service. I
propose to replace "Option 1" and "Option 2" with a brief description of
how to use NSSM. Since I'm not a Windows expert, I wanted to get some
feedback on that change from any users that might have strong Windows
knowledge, or experience running Trac on Windows.

- Ryan


(1) https://trac.edgewall.org/wiki/TracStandalone#
InstallingasaWindowsService
(2) https://stackoverflow.com/questions/49412064/starting-
trac-server-with-multiple-independant-projects/49417090#49417090

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Poor rating of trac site on Mozilla Observatory

[Ryan Ollos]

On Thu, Dec 14, 2017 at 9:41 AM, Torge Riedel  wrote:

> Hi,
>
> I've set up a trac via https using latest stable trac (1.2.2).
>
> I've found a nice tool checking site configuration:
> https://observatory.mozilla.org/
>
> Checking my trac installation I got a poor "D" rating.
>
> Following is the list of tests failed resulting in a negative score:
>
> Test   Score Explanation
> Content Security Policy -25 Content Security Policy (CSP)
> header not implemented
> Contribute.json -10 Contribute.json file cannot be
> parsed
> X-Content-Type-Options-5   X-Content-Type-Options header not
> implemented
> X-Frame-Options   -20 X-Frame-Options (XFO) header not
> implemented
> X-XSS-Protection   -10 X-XSS-Protection header not
> implemented
>
> Since other sites hosted on my server get better ratings there must be a
> chance to fix this in the code. Another way is to add such headers to the
> apache config, but I'm not sure whether I am breaking something in trac and
> it's less flexible.
>
> Is there a chance to improve the headers trac is sending? Can I help with
> whatever is helpful?
>
> Regards
> Torge
>

Some of all of this may be best addressed through your web server
configuration. Are you running Apache?

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.3.2 Release

[Ryan Ollos]

Trac 1.3.2 Released


Trac 1.3.2, the latest development release leading up
to Trac 1.4, is available.

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#LatestDevRelease

You can find the detailed release notes for 1.3.2
on the following pages:
https://trac.edgewall.org/wiki/1.3/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.3#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.3.2-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.3.2.tar.gz
https://download.edgewall.org/trac/Trac-1.3.2.win32.exe
https://download.edgewall.org/trac/Trac-1.3.2.win-amd64.exe

MD5 sums:

b0ab068efc8d401d529519fa3a7c7359  Trac-1.3.2-py2-none-any.whl
27e8f357ea96c0cdd4d66e324729edca  Trac-1.3.2.tar.gz
afb5f30d360ef29a0a433b88a9658c8b  Trac-1.3.2.win32.exe
ce3add5b445c413c4ebd5860cde01afc  Trac-1.3.2.win-amd64.exe

SHA1 sums:

24f1f8ad0ec94280455f687d030f2efd0a3b98d4  Trac-1.3.2-py2-none-any.whl
267b6b8733aaf8899eb0cbb627d8d1926ad166c7  Trac-1.3.2.tar.gz
918b6144cd19ec98a67d299976b71515cbc696f9  Trac-1.3.2.win32.exe
7518302b3ef92897c8ede49cb2915432073c64b9  Trac-1.3.2.win-amd64.exe

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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Forced SSL

[Ryan Ollos]

On Thu, Jul 20, 2017 at 8:02 AM, Logan Anderson 
wrote:

> Hey guys,
>
>
> I have a list of custom plugins I wrote which I had to modify so urllib2
> would use SSL because I just forced my Trac install to SSL. Trac 1.2, for
> reference.
>
> My question is this:
> I see a few other plugins such as SimpleMultiProject using SSL to make
> calls which appear to be going back to the base URL for Trac. I am not
> currently seeing any major breakage or specific errors, but I was wondering
> if you guys have any insight on whether this would be handled correctly
> already within that plugin?
>
> This is basically the line I had to add to my plugin to make it function:
>
> gcontext = ssl.SSLContext(ssl.PROTOCOL_TLSv1)
>
> info = urllib2.urlopen(req, context=gcontext).read()
>
> Obviously straight out of stack overflow. Do you guys have any insight on
> running a site SSL only in this way? Have you run into any major issues in
> the past? So far everything seems functional after modifying my own
> plugins. Just trying to think of anything I may be missing.
>


I have never encountered a situation in which a plugin needed to be
concerned about whether the protocol was using SSL. To force SSL, you
should configure your webserver to redirect http:// -> https://. That is
how we've configured Apache for trac-hacks.org, trac.edgewall.org, etc ...

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.2.2 Released

[Ryan Ollos]

Trac 1.2.2 Released


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

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#PreviousStableRelease
https://pypi.python.org/pypi/Trac/1.2.2

You can find the detailed release notes for 1.2.2
on the following pages:
https://trac.edgewall.org/wiki/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.2#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.2.2-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.2.2.tar.gz
https://download.edgewall.org/trac/Trac-1.2.2.win32.exe
https://download.edgewall.org/trac/Trac-1.2.2.win-amd64.exe

MD5 sums:

38cb5480c35616d8ecb3f0968e454536 Trac-1.2.2.tar.gz
00fc918dbf08398ca30f337ce55f8cab Trac-1.2.2-py2-none-any.whl
b7b547b3d2bb4a0564a2dbf11ff7454c Trac-1.2.2.win32.exe
4535be0c9fc8ef670d9e1506e21dd6b7 Trac-1.2.2.win-amd64.exe

SHA1 sums:

815b4574c7eec8915f8b42b76d5f23a220951937 Trac-1.2.2.tar.gz
f0df88a5d5d7b6a84e929c9c61b2fbe1e4e2779e Trac-1.2.2-py2-none-any.whl
6774b70e6352b43aa8b1c4c7a35dce081877fbfb Trac-1.2.2.win32.exe
40af51a34cccd8758d31cd87292ad5b4d883caef Trac-1.2.2.win-amd64.exe

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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.15 Released

[Ryan Ollos]

Trac 1.0.15 Released


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

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#PreviousStableRelease
https://pypi.python.org/pypi/Trac/1.0.15

Trac 1.0.15 provides a few fixes that were found necessary following
the recent 1.0.14 release. See the change log for details.

You can find the detailed release notes for 1.0.15
on the following pages:
https://trac.edgewall.org/wiki/1.0/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.0.15-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.0.15.tar.gz
https://download.edgewall.org/trac/Trac-1.0.15.win32.exe
https://download.edgewall.org/trac/Trac-1.0.15.win-amd64.exe

MD5 sums:

06675fc27ff8536e3b31bde55748beb3  Trac-1.0.15-py2-none-any.whl
f0f498064fe295e1bd1993749f86d0ee  Trac-1.0.15.tar.gz
88b93841005dff28b0b1722f9b73894b  Trac-1.0.15.win32.exe
b8c8a96bb854d8f8729fce198aef47c8  Trac-1.0.15.win-amd64.exe

SHA1 sums:

e9a00f97a90477714edff67e48ec6f43359a4915  Trac-1.0.15-py2-none-any.whl
26a82e1659b867f8c36cc4619e95d18c5e1c8644  Trac-1.0.15.tar.gz
d9bd4d0e6edcf970928f41597a34e717d7268fad  Trac-1.0.15.win32.exe
745c356a80cfffcfaf406a1f0ca97a211b88a47d  Trac-1.0.15.win-amd64.exe

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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.14 Released

[Ryan Ollos]

Trac 1.0.14 Released


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

You will find this release at the usual places:

https://trac.edgewall.org/wiki/TracDownload#PreviousStableRelease
https://pypi.python.org/pypi/Trac/1.0.14

Trac 1.0.14 provides more than 3 dozen bug fixes and
minor enhancements.

You can find the detailed release notes for 1.0.14
on the following pages:
https://trac.edgewall.org/wiki/1.0/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.0.14-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.0.14.tar.gz
https://download.edgewall.org/trac/Trac-1.0.14.win32.exe
https://download.edgewall.org/trac/Trac-1.0.14.win-amd64.exe
https://download.edgewall.org/trac/Trac-1.0.14.zip

MD5 sums:

4fbac9b81d9cfc4a790111491a04858c  Trac-1.0.14-py2-none-any.whl
590b4fc2eac41a774bd25792f878a674  Trac-1.0.14.tar.gz
e59c0a7d620a3470f4ca9c4a2f62fc7c  Trac-1.0.14.win32.exe
2ec6706295c667f88b0d493dfcaf78ad  Trac-1.0.14.win-amd64.exe
620f2bcfd67205fa66b657b3f91a666f  Trac-1.0.14.zip

SHA1 sums:

15cad79ca974fc7bbe7c8256b503c113abe902f5  Trac-1.0.14-py2-none-any.whl
d5c4034a5dc133abd91a278d7d39c5273d1a2ea7  Trac-1.0.14.tar.gz
c3c4d5b66090721b4dca97b1aa8783aa9196fad5  Trac-1.0.14.win32.exe
95edfee3fcfcfe21338d3a39baf0a04c78e12dd7  Trac-1.0.14.win-amd64.exe
4ff077fcd0a060a461551fca4d9fffccf08b139f  Trac-1.0.14.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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 1.0.3 / 1.1.3

[Ryan Ollos]

On Sun, Dec 4, 2016 at 3:18 PM W. Martin Borgert  wrote:

> On 2016-12-04 13:46, RjOllos wrote:
> > Debian 8 update 6 appears to still have Trac 1.0.2. Will the package be
> > updated anytime soon?
>
> That is unfortunagely true. I managed to update the package for
> Debian unstable on a regular base, but not for stable. I will,
> however, try to prepare an official backport to Debian 8 soon.
>

Thanks. Just for reference, we've been discussing here:
https://groups.google.com/d/msg/trac-users/jOyxkWLcwxQ/gI3m9Ie1BwAJ

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.2 Released

[Ryan Ollos]

Trac 1.2 is now available.

You can find the release at the usual place:
https://trac.edgewall.org/wiki/TracDownload#LatestStableRelease

Trac 1.2 is the first major release of Trac in more than 4 years.
The following are some highlights from the release:
* Extensible notification system (#3517)
* Notification preference panel (#4056)
* Usernames replaced with full names (#7339)
* Restyled ticket changelog (#11835)
* Workflow controls on the New Ticket page (#2045)
* Editable wiki page version comments (#6573)
* Datetime custom fields (#1942)

You can find the detailed release notes for 1.2 on the following pages:
https://trac.edgewall.org/wiki/1.2/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1

Now to the packages themselves:

URLs:
https://download.edgewall.org/trac/Trac-1.2-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.2.tar.gz
https://download.edgewall.org/trac/Trac-1.2.win32.exe
https://download.edgewall.org/trac/Trac-1.2.win-amd64.exe
https://download.edgewall.org/trac/Trac-1.2.zip

MD5 sums:
6ee8b4d749eba651d82019bb11cfdee0  Trac-1.2-py2-none-any.whl
ff3a7d78099a269ae2035a6cf8adccbb  Trac-1.2.tar.gz
29fb381b01554063e687f68e21582e96  Trac-1.2.win32.exe
973bae7da4de2dd8b94947b486344096  Trac-1.2.win-amd64.exe
1fcd80a33bc29be9e4b5cab0cee9e32b  Trac-1.2.zip

SHA1 sums:
8c47aa3de4111889e9b2b9f11885b1e6a01ec934  Trac-1.2-py2-none-any.whl
f4c2cca41f7e7d1def37b736a502bbb9db72df2b  Trac-1.2.tar.gz
96ec3b6662baa59ffaa6407de50be9c12fa525ef  Trac-1.2.win32.exe
44ad3efa7d70c6c7a186a53de46554e62bb57e99  Trac-1.2.win-amd64.exe
c1ad79e79ac8c3a6df91305ba6a12f931bab22b1  Trac-1.2.zip

/The Trac Team http://trac.edgewall.org

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 1.2rc1 available

[Ryan Ollos]

On Fri, Sep 23, 2016 at 5:13 PM anton  wrote:

> Hi,
>
> one question: is trac 1.2 python3 ready?
>
> I am asking because I am just moving my code
> (django projects) from python 2.7 to python 3.5
>
> Anton
>

Trac 1.2 will support Python 2.6 and 2.7. Trac 1.4 will probably support
Python 3.

https://trac.edgewall.org/wiki/1.1/TracInstall#MandatoryDependencies

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.2rc1 available

[Ryan Ollos]

Trac 1.2rc1 is now available and ready for testing. Please give it a try
in your test environments and report any issues you encounter.

You can find the release at the usual place:
https://trac.edgewall.org/wiki/TracDownload#LatestDevRelease

Trac 1.2rc1 is the culmination of nearly 4 years of development, with
more than 200 issue resolved.

You can find the detailed release notes for 1.2rc1 on the following pages:
https://trac.edgewall.org/wiki/1.1/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1

Now to the packages themselves:

URLs:
https://download.edgewall.org/trac/Trac-1.2rc1-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.2rc1.tar.gz
https://download.edgewall.org/trac/Trac-1.2rc1.win32.exe
https://download.edgewall.org/trac/Trac-1.2rc1.win-amd64.exe
https://download.edgewall.org/trac/Trac-1.2rc1.zip

MD5 sums:
4e056bc226d11e3d368da58789d3c960  Trac-1.2rc1-py2-none-any.whl
0e625f8f5ad4930a05445ec3b521c7e0  Trac-1.2rc1.tar.gz
d3e25ed5cfa4830ff8463fe8bb9ff717  Trac-1.2rc1.win32.exe
8b4b4c554537ae33e474690c02b3cb13  Trac-1.2rc1.win-amd64.exe
b096a6b4c75db5d154fde32ad7085f77  Trac-1.2rc1.zip

SHA1 sums:
99c56b1596236ba566287b9d3156239d1d527a28  Trac-1.2rc1-py2-none-any.whl
f59e9cd657ddef732c275eeb4a447c2854a9523a  Trac-1.2rc1.tar.gz
38f46ce9c8668227fdd8c9ff380f620e8df5ae4c  Trac-1.2rc1.win32.exe
827bba571c83c0a2ab03c22a31e1f4bfb3227c27  Trac-1.2rc1.win-amd64.exe
b1ad2f2b5231647b230fd53a54ea8be4667ac4e5  Trac-1.2rc1.zip


We look forward to your feedback on the release candidate.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.13 Released

[Ryan Ollos]

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:

http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
https://pypi.python.org/pypi/Trac/1.0.13

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:
https://trac.edgewall.org/wiki/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.0.13-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.0.13.tar.gz
https://download.edgewall.org/trac/Trac-1.0.13.win32.exe
https://download.edgewall.org/trac/Trac-1.0.13.win-amd64.exe
https://download.edgewall.org/trac/Trac-1.0.13.zip

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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.12 released

[Ryan Ollos]

Trac 1.0.12 Released


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

You will find this release at the usual places:

http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
https://pypi.python.org/pypi/Trac/1.0.12


Trac 1.0.12 provides around 20 bug fixes and minor
enhancements.

You can find the detailed release notes for 1.0.12
on the following pages:
https://trac.edgewall.org/wiki/TracChangeLog
https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

https://download.edgewall.org/trac/Trac-1.0.12-py2-none-any.whl
https://download.edgewall.org/trac/Trac-1.0.12.tar.gz
https://download.edgewall.org/trac/Trac-1.0.12.win32.exe
https://download.edgewall.org/trac/Trac-1.0.12.win-amd64.exe
https://download.edgewall.org/trac/Trac-1.0.12.zip

MD5 sums:

9db944eccaf104d097e131fb842161c6 Trac-1.0.12-py2-none-any.whl
941e333b0c0c81d5c4f4e086174a26e7 Trac-1.0.12.tar.gz
fb58c243355114c24d91f38964cfbbb4 Trac-1.0.12.win32.exe
9d3c4460cf05165add70a507ba6828bb Trac-1.0.12.win-amd64.exe
4f9bc8de1d4a22bbcd8454e6903148b5 Trac-1.0.12.zip

SHA1 sums:

75bccaee5af86f7994a52e0e83c40d1cf5fb0acb Trac-1.0.12-py2-none-any.whl
56534447e5c2f81fe43381e99468653c58d46670 Trac-1.0.12.tar.gz
49decdb9d2a7898e899c07d7e8edc13523fe1791 Trac-1.0.12.win32.exe
939cd197febe0e3f42a6086d5129749173f29c21 Trac-1.0.12.win-amd64.exe
1829c663124d137eddb2c92f8c11b0c7cb1ae571 Trac-1.0.12.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.

/The Trac Team http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.11 released

[Ryan Ollos]

Trac 1.0.11 Released


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

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.11

Trac 1.0.11 provides more than 30 bug fixes and minor
enhancements. As in 1.0.10, an area of focus has been to
eliminate tracebacks in the logs due to invalid requests.

You can find the detailed release notes for 1.0.11
on the following pages:
  https://trac.edgewall.org/wiki/TracChangeLog

https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.11-py2-none-any.whl
  http://download.edgewall.org/trac/Trac-1.0.11.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.11.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.11.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.11.zip

MD5 sums:

62057eb4f3000b5224ed781fd1b9fdbd  Trac-1.0.11-py2-none-any.whl
3154ef8cacf77ff59f81969c895c72cb  Trac-1.0.11.tar.gz
5cb6a80b780c6ed47f775cc3a411108c  Trac-1.0.11.win32.exe
2cbcf3cc3320142e1f9f211fae4cd689  Trac-1.0.11.win-amd64.exe
b3094a1de0842f198df6fbf54752c232  Trac-1.0.11.zip

SHA1 sums:

226ad3a4cde6e50b765a1e05c6984d8928f3b27e  Trac-1.0.11-py2-none-any.whl
709485af9479969a50fe384f74bba95adad3e8c1  Trac-1.0.11.tar.gz
724872d81cde43a4d1a5faae2baacdd7fe3a006f  Trac-1.0.11.win32.exe
881734d2bbc1564f63937761e2cacd6feb32627e  Trac-1.0.11.win-amd64.exe
faabfd34c70e57e81fcecfd50769d1836cb1f429  Trac-1.0.11.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 offer hope that Trac will prove itself
useful to like-minded programmers around the world,
and that this release will be an improvement over
the last version.

Please let us know.

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Re: Python3 question

[Ryan Ollos]

On Tue, Mar 15, 2016 at 5:30 PM, Tim Graham  wrote:

> If Python 3 support for Trac won't be released until 2017, I think there's
> no need to support Python 3.3 which is end-of-life in September 2017
> (already the most recent release of Django supports Python 3.4+, for
> example). I think Python 3.5+ would be a fine target, but if people feel
> that Python 3.4 support is important for some reason, it might not add much
> work. As long as we must maintain Python 2.7 support, we're fairly limited
> in the Python 3 features we can use anyway.
>

Thanks. I haven't worked with Python3 much, but I guess it's worth
considering supporting Python 3.4+.

If we do support Python 3.3 in Trac 1.4 though, and stick to a major
release every 12-18 months, we would extrapolate nicely on the pattern
Christian previously noted (1).

Trac 0.11 - last version to work with Python 2.3
Trac 0.12 - last version to work with Python 2.4
Trac 1.0  - last version to work with Python 2.5
Trac 1.2  - last version to work with Python 2.6
Trac 1.4 - last version to work with Python 3.3 (released Jun 2017?)
Trac 1.6 - last version to work with Python 3.4 (released Jan 2019?)

The release dates line up fairly nicely with the end-of-life for the Python
releases (2), preceding them by just a few months.

- Ryan

(1) https://groups.google.com/d/msg/trac-dev/nkMUY_8ILF0/xdGVywGqTkYJ
(2) https://docs.python.org/devguide/index.html#branchstatus

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.10 released

[Ryan Ollos]

Trac 1.0.10 Released
===

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

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.10

Trac 1.0.10 provides more than 30 bug fixes and minor
enhancements. Two areas of focus have been fixing test
failures on Windows and eliminating tracebacks in the logs
due to invalid requests.

You can find the detailed release notes for 1.0.10
on the following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.10.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.10.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.10.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.10.zip

MD5 sums:

b2081c744cdda2784ec6275d66a05763  Trac-1.0.10.tar.gz
c7830344033c6ad95530c3897031b3eb  Trac-1.0.10.win32.exe
98b6c1c0c2fd73d66e24a194da3f3284  Trac-1.0.10.win-amd64.exe
e8ae6d9e323820fbb89da9c3c75f7d71  Trac-1.0.10.zip

SHA1 sums:

e0283001fa545cb103a85ac6b2d265dd0e8b0f92  Trac-1.0.10.tar.gz
2ca1b70b5971c956bfb8ee4858abd84e374987e9  Trac-1.0.10.win32.exe
58d5e6bff57b88cbcd83e4a12a17ce75ac4e1160  Trac-1.0.10.win-amd64.exe
56411dee5333ef98985cbe97d63dba675ec3157b  Trac-1.0.10.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 offer hope that Trac will prove itself
useful to like-minded programmers around the world,
and that this release will be an improvement over
the last version.

Please let us know.

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Re: Trac in UCS

[Ryan Ollos]

On Thu, Oct 1, 2015 at 12:20 AM, figaro  wrote:

> Better to post a ticket on trac.edgewall.org:
> http://trac.edgewall.org/wiki/NewTicket
>

This is actually not appropriate for a new ticket. Ideally the question
would be submitted to the trac-users mailing list.
trac.edgewall.org/wiki/MailingList

I don't know what UCS is, so more information is needed.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.9 released

[Ryan Ollos]

Trac 1.0.9 Released
===

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

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.9

Trac 1.0.9 provides more than a dozen minor fixes
and enhancements, including significantly reduced
memory usage by the Git repository connector.

You can find the detailed release notes for 1.0.9
on the following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.9.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.9.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.9.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.9.zip

MD5 sums:

429d9aa79e3d939add7963ca9a7deb57  Trac-1.0.9.tar.gz
9801dbb0b93d22294d82ad7cc2d33829  Trac-1.0.9.win32.exe
db1c35aa95fda539e6b7365fb5af4780  Trac-1.0.9.win-amd64.exe
0bb8ceffe7dbe6211a3887e42a1be972  Trac-1.0.9.zip

SHA1 sums:

a22c4f648c2f0adf7ca166aa5c01b0142bccbef0  Trac-1.0.9.tar.gz
caa4d0c96a456c8a9427c9bd0db8d665b911d50a  Trac-1.0.9.win32.exe
3a82ccc0fdf3dc8ca9077cb3432464a3ff2547e6  Trac-1.0.9.win-amd64.exe
ac338b2fde74df9ab19948d1caf6d25cc0e37622  Trac-1.0.9.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 offer hope that Trac will prove itself
useful to like-minded programmers around the world,
and that this release will be an improvement over
the last version.

Please let us know.

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.8 released

[Ryan Ollos]

Trac 1.0.8 Released
===

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

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.8

Trac 1.0.7 was release on the 17th of July, but a
regression was discovered and fixed in this release.

 - the session for an authenticated username
   containing non-alphanumeric characters
   could not be retrieved, resulting in the user
   being denied access to every realm and resource.

You can find the detailed release notes for 1.0.8 on the
following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.8.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.8.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.8.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.8.zip

MD5 sums:

  a2fc666afd4e59a72ad76d8292d39111  Trac-1.0.8.tar.gz
  9f5b2257bddc6a28c6839e6936ebeddb  Trac-1.0.8.win32.exe
  e30d7ec90664ec43b0e58aec289e0584  Trac-1.0.8.win-amd64.exe
  4c3fd76b6fb63975b753fbd6a7cd4523  Trac-1.0.8.zip

SHA1 sums:

  4f31316a8bd16d7335f0c346dad85654ff5c4837  Trac-1.0.8.tar.gz
  4f585f07d1536e67ae0c1665efbec442ad249dd7  Trac-1.0.8.win32.exe
  4afeb0da8dde988f8a153454353a5ac5e41c6d3a  Trac-1.0.8.win-amd64.exe
  e1238237433d268762f731b4934d62a85fb40b8b  Trac-1.0.8.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 offer hope that Trac will prove itself
useful to like-minded programmers around the world,
and that this release will be an improvement over
the last version.

Please let us know.

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] offer to help with Python 3 support

[Ryan Ollos]

On Sun, Jul 19, 2015 at 10:56 AM, Tim Graham timogra...@gmail.com wrote:

 I put together a few initial patches (some is rebased from Jun's work)
 which should be fine to merge now, even if Python 2.6 is still supported.
 https://github.com/timgraham/trac/pull/1

 Is attaching patches to Trac tickets the best way to submit this work?
 That workflow seems painful from a code review perspective.

 I created a pull request to my own fork which seems like it would at least
 make review easier: https://github.com/timgraham/trac/pull/1


Providing a link to Git repository in a ticket is good.  Looks like you
have a good granularity to those changesets, which should make them easy to
review. Thanks!

I think it would be good to just create another ticket for Python3
compatibility, one that we can close at the end of this development
iteration even if we haven't obtained full Python3 compatibility. You can
then post comments about your work to that ticket, and we can integrate it
to the trunk.

When we finally have full Python3 compatibility we can close out #10083.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.1.6 Released

[Ryan Ollos]

Trac 1.1.6 Released
===

Trac 1.1.6, the final release on the 1.1.x
development line leading up to 1.2, provides
more than a half-dozen minor fixes and
enhancements.

Note that the 1.1.x releases are stable and
tested snapshots of the trunk.  They can be seen
as sub-milestones on the road towards Trac 1.2. As
opposed to maintenance releases, *we offer no
guarantees on feature and API compatibility from
one 1.1.x release to the next*.

However, by following 1.1.x you get a chance to
use new features earlier, and therefore be able to
contribute feedback when things are still in flux.
It's also less risky than just getting the latest
trunk, as we won't cut a 1.1.x release in the middle
of a series of changes (though we had and still intend
to have a good record of keeping things always working
on trunk).

The intended audience are therefore enthusiast Trac
users and Trac plugin developers. These packages should
*not* be integrated in distributions, for example.

The fixes made for 1.0.7 are also included.

You can find all the detailed release notes at:

 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#DevelopmentReleases
 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Download URLs:

  http://download.edgewall.org/trac/Trac-1.1.6.tar.gz
  http://download.edgewall.org/trac/Trac-1.1.6.win32.exe
  http://download.edgewall.org/trac/Trac-1.1.6.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.1.6.zip

MD5 sums:

  0f96a95a3e8a92e7a694883c929b2fa2  Trac-1.1.6.tar.gz
  55c9dbb5ee430d139d0195eb9a056146  Trac-1.1.6.win32.exe
  4d42dcbedafcfeba30a8be6d8a02ab4c  Trac-1.1.6.win-amd64.exe
  fdf6f5e7653ae84cd2c8f14ac6475dc2  Trac-1.1.6.zip

SHA1 sums:

  0f4b3cc3cb8a2ee6b649ee5c4cf502f4f1f213e3  Trac-1.1.6.tar.gz
  d1273671ab354ea97efbc0a78bf03a0b86125399  Trac-1.1.6.win32.exe
  13e5f23e940bf9eaef9cb9261e0e6b5b87da21c6  Trac-1.1.6.win-amd64.exe
  99b98f716f38eda3fdacf4ab7221e0d381d41418  Trac-1.1.6.zip


Enjoy!

- The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Fwd: Trac 1.0.7 Released

[Ryan Ollos]

Trac 1.0.7 Released
===

Trac 1.0.7, the latest maintenance release for the
current stable branch, is now available!

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.7

Trac 1.0.6 was release on the 20th of May and we've
provided over a dozen fixes and minor enhancements since
then.

A few highlights from this release:

 - Custom svn:keywords definitions are expanded in
   Subversion 1.8 and later (#11364).
 - Fixed MySQL performance regression in query with
   custom fields (#12113).


You can find the detailed release notes for 1.0.7 on the
following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.7.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.7.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.7.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.7.zip

MD5 sums:

  3a985c743f3125f69f0334740b931f7d   Trac-1.0.7.tar.gz
  6e18cd990b44106f669b1db7b1c90aa6   Trac-1.0.7.win32.exe
  30ddeda925dec5757a80efd9f4e35e66   Trac-1.0.7.win-amd64.exe
  7c5a7361e565bd5d26b302f5857172aa   Trac-1.0.7.zip

SHA1 sums:

  d1dfb226b65b2b7e72f5da2d2a0bf6343f96728   Trac-1.0.7.tar.gz
  95287e736836f783f823e27ab7c84f833f8365a0  Trac-1.0.7.win32.exe
  d06ee85b59229b8567e427b96ba8f0d1978bc45f  Trac-1.0.7.win-amd64.exe
  987ed0a80438e6e14a56b0e4a1341daafdbc1ce7  Trac-1.0.7.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 offer hope that Trac will prove itself
useful to like-minded programmers around the world,
and that this release will be an improvement over
the last version.

Please let us know.

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 0.12.7 Released

[Ryan Ollos]

Trac 0.12.7 Released


Trac 0.12.7, a maintenance release for the long term
maintenance release line 0.12.x, is here.

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#PreviousStableRelease
  https://pypi.python.org/pypi/Trac/0.12.7

For the security conscious people, the md5sums of the packages are:

3abf3329989bbf9cbc581e3058dfa56e Trac-0.12.7.tar.gz
10a7d3c3bf801d7f7a46cfbb2b1af903 Trac-0.12.7.win32.exe
d888e4267602cf32abcf8e6d48eb8b07 Trac-0.12.7.win-amd64.exe
7bc761d3a234e130c729900f21dd2e26 Trac-0.12.7.zip


Trac 0.12.7 fixes a minor security issue, as well as a half dozen
other minor issues:
 - InterWiki filters links through `[wiki] safe_schemes` option if
   `[wiki] render_unsafe_content` is disabled (#12053).

You can find the detailed list of tickets at:

  http://trac.edgewall.org/milestone/0.12.7


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 offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will be
an improvement over the last version.

Please let us know.:-)

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] offer to help with Python 3 support

[Ryan Ollos]

On Tue, Jul 7, 2015 at 2:51 PM, Tim Graham timogra...@gmail.com wrote:

 I'm a developer on the Django team and we use Trac as our bug tracker. I'm
 interested in moving our infrastructure to Python 3, but need Trac to
 support Python 3 in order to do so. Django supports Python 2 and 3, so I
 have some experience in maintaining a code base that supports both. I
 started working on a patch (attached), but as it will be a non-trivial
 effort, I wanted to get an initial review and ensure this approach is
 agreeable to the Trac team. I also wanted to ensure that when I finish the
 patch, someone will be interested in reviewing and committing it relatively
 quickly so that it doesn't go stale. My strategy is to attempt to run the
 test suite on Python 3 and fix errors, while ensuring the tests pass on
 Python 2.7 as a I go. Thanks! Tim


(Peter beat me to it, so there's some redundancy in my message :)

I appreciate your offer to help us move to Python 3. We are going to
release Trac 1.2 soon. In the 1.3.x development line leading up to 1.4
we'll drop support for Python 2.6, only supporting Python 2.7 (1).
Supporting Python 3.3 or 3.4 in 1.3.x is a possibility, but we haven't
discussed it lately. The last time I recall discussing it was in (2) (see
comment:30 in that ticket).

I expect it will be a major effort to have Trac support Python 3. Jun has
done some work on it, so he can best comment on the effort required. You
may want to read through #10083 (3) to see a list of concerns previously
raised, and review the python3 tickets (4). I recall there being concerns
about some of our dependencies not supporting Python 3, such as MySQLdb.

With regard to the mechanics of proposing changes, you'll want to base your
changes off the current trunk. If you create one monolithic path, it will
be difficult for us to review, and will easily become stale, like you
suggest. If you were to fork Trac in your favorite DVCS and start stacking
up concise changes that lead to supporting Python 3, we can review and
incorporate those incrementally. For example, you could submit a patch to
fix #12046 (5). You could rebase regularly to avoid the changes that don't
get pushed right away from becoming stale.

I admit I'm not overly enthusiastic about supporting Python 2.7 and 3.x in
the same codebase. I have wanted to make progress towards Python 3 so that
we could jump to supporting a minimum of Python 3.3 or 3.4 in development
leading up to Trac 1.6. Whether explicitly planned or not, we've been
incrementing the minimum Python version supported with each major release
(6). Since I've mentioned versions - more about our versioning scheme and
roadmap can be found in (7).

(1) http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3
(2) http://trac.edgewall.org/ticket/11600#comment:20
(3) http://trac.edgewall.org/ticket/10083
(4) http://trac.edgewall.org/query?status=!closedkeywords=~python3
(5) http://trac.edgewall.org/ticket/12046
(6) https://groups.google.com/d/msg/trac-dev/nkMUY_8ILF0/xdGVywGqTkYJ
(7) http://trac.edgewall.org/wiki/RoadMap#TracsRoadAhead

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Re: Roadmap to Trac 1.2

[Ryan Ollos]

On Mon, Jun 29, 2015 at 8:39 AM, Mael Lavault moim...@gmail.com wrote:

 Just a quick question, does trac allow to be configured by environment
 variables ? It would greatly simplify Docker packaging. If not I will have
 to write a script that convert env var into corresponding ini file
 properties.

 Thx !


I think it's not possible yet, but discussed in this ticket:
http://trac.edgewall.org/ticket/11339

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Re: about starting point of contribution

[Ryan Ollos]

On Fri, Jun 12, 2015 at 5:41 PM, Walty Yeung wal...@gmail.com wrote:



 On Friday, May 15, 2015 at 8:05:24 AM UTC+8, Walty Yeung wrote:



 On Thursday, May 14, 2015 at 5:24:27 AM UTC+8, RjOllos wrote:

 On Mon, May 11, 2015 at 9:53 AM, RjOllos rjo...@gmail.com wrote:



 On Saturday, May 9, 2015 at 11:21:56 PM UTC-7, Walty Yeung wrote:

 and my question is, is the bite-sized tasks (
 http://trac.edgewall.org/query?status=newstatus=assignedstatus=reopenedkeywords=~bitesizedgroup=componentorder=priority)
 still the optimal entry point of contribution now? I asked only  because I
 saw most of the tickets there are actually pretty old, and I am not sure 
 if
 they are actually outdated now, however, I don't mind to start with the
 minor changes at all.


 In case you are looking for specific suggestions on where to start,
 #11937 should be fairly tractable:

 http://trac.edgewall.org/ticket/11937


 In case I've led you into a ticket that is more challenging than it
 seemed from the outset, please don't be afraid to work several tickets in
 parallel. That's usually what I do since I like the feeling of progress
 from knocking out a ticket or two each week, and not every ticket I pickup
 leads to immediate progress.

 - Ryan



 No problem, I would have a look of other bite-sized tickets under the
 milestone of  next-dev-1.1.x
 http://trac.edgewall.org/milestone/next-dev-1.1.x

 Thanks.



 hi,

 I am sorry that I bring up this thread again.

 I have recently made the patch for #10144 and #11937 about 3 weeks ago,
 and I still have no idea if such patches are fine or not.

 Please don't misunderstand me, I am not trying to push for anything, but I
 would like make sure I am on the right track (the patch format, style, and
 code quality etc...) before I move on to other tickets.

 thanks.


Hi Walty,

I'm sorry for the delay, and thank you for bearing with us. I'll try to
review your patches for tomorrow, and also suggest some tickets that are a
bit more straightforward to implement.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.6 Released

[Ryan Ollos]

Trac 1.0.6 Released
===

Trac 1.0.6, the sixth maintenance release for the
current stable branch, is now available!

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.6.post2

Trac 1.0.5 was release on 24th of March and we've
provided over 20 fixes and minor enhancements since
then.

A few highlights from this release:


 - Hash changeset ids and branch names can be used in
   revision ranges (#11050).
 - Improved rendering performance using chunked response
   when [trac] use_chunked_encoding is True (#11802).
 - Improved performance of Git repositories (#11971).
 - Header to send when [trac] use_xsendfile is True can be
   specified through the option [trac] xsendfile_header.
   X-Sendfile is supported in Nginx by specifying
   X-Accel-Redirect for the header (#11981).
 - Symbolic link can be used for conf/trac.ini in environment
   directory (#12000).
 - Hyphen character can be used in WikiProcessor parameter
   name (#12023).

Additionally, the fixes for 0.12.7 are included in this
release.

You can find the detailed release notes for 1.0.6 on the
following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.6.post2.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.6.post2.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.6.post2.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.6.post2.zip

MD5 sums:

  8ffd8dc24ddedfff0ec4d7d70c7f3a01  Trac-1.0.6.post2.tar.gz
  266160df714308dc5e808c0cf675fc32  Trac-1.0.6.post2.win32.exe
  3d615eb88b9d378afb306813ffa02d02  Trac-1.0.6.post2.win-amd64.exe
  bc464944f4799fb559e0ca6d05e61ffd  Trac-1.0.6.post2.zip

SHA1 sums:

  7740698da88cf415c4b27df362c753bfc61b0441  Trac-1.0.6.post2.tar.gz
  864376e575b1b53d7ab6fb0702033d5a434c9eda  Trac-1.0.6.post2.win32.exe
  fa93f861a3303fb7a3914cf2a52faf7fef25ce1d  Trac-1.0.6.post2.win-amd64.exe
  7a47a6e452a18d759a995bf64077d84d54c0802a  Trac-1.0.6.post2.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 offer hope that Trac will prove itself
useful to like-minded programmers around the world,
and that this release will be an improvement over
the last version.

Please let us know.

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.1.5 Released

[Ryan Ollos]

Trac 1.1.5 Released
===

Trac 1.1.5 continues the 1.1.x development line
leading to 1.2 with some new features and a few
not-so-disruptive changes.

Note that the 1.1.x releases are stable and
tested snapshots of the trunk.  They can be seen
as sub-milestones on the road towards Trac 1.2. As
opposed to maintenance releases, *we offer no
guarantees on feature and API compatibility from
one 1.1.x release to the next*.

However, by following 1.1.x you get a chance to
use new features earlier, and therefore be able to
contribute feedback when things are still in flux.
It's also less risky than just getting the latest
trunk, as we won't cut a 1.1.x release in the middle
of a series of changes (though we had and still intend
to have a good record of keeping things always working
on trunk).

The intended audience are therefore enthusiast Trac
users and Trac plugin developers. These packages should
*not* be integrated in distributions, for example.

Here are a few highlights:

 - Corrected highlighting of unmodified values in Config
   section of the About Trac page ([#6551).
 - New helper methods on `DatabaseManager` class for
   plugins to upgrade the database (#8172).
 - New `[notification-subscriber]` config section for
   general configuration of notification subscription
   defaults and `SubscriberList` macro (#11875).
 - Removed dependency on `ConfigObj` for
   TracFineGrainedPermissions (#11982).
 - `Image` macro supports InterWiki prefixes (#12025).

Besides the few issues listed here, the fixes made for
0.12.7 and 1.0.6 are also included.

You can find all the detailed release notes at:

 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#DevelopmentReleases
 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Download URLs:

  http://download.edgewall.org/trac/Trac-1.1.5.tar.gz
  http://download.edgewall.org/trac/Trac-1.1.5.win32.exe
  http://download.edgewall.org/trac/Trac-1.1.5.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.1.5.zip

MD5 sums:

  8f53ae0f9cd4b0a0b55f0e273dae3c37  Trac-1.1.5.zip
  c4547e2b6c7e1b174ccafa47227159e1  Trac-1.1.5.tar.gz
  3dd67a28440487742264d0f87ace26e2  Trac-1.1.5.win32.exe
  be7c34e53f429e90dc0bfd7840f6b3e1  Trac-1.1.5.win-amd64.exe

SHA1 sums:

  e00d8211cf558424efa98a36d90e9d39aad5e1b3  Trac-1.1.5.zip
  29ffaa71a5256c6b514a5e5442de78718e5be1ed  Trac-1.1.5.tar.gz
  5f6f851f662c7fbd1bd6d83e7b5953452b400fe1  Trac-1.1.5.win32.exe
  418f84f854c0059b7823152db2813620a03d7589  Trac-1.1.5.win-amd64.exe

Enjoy!

- The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] about starting point of contribution

[Ryan Ollos]

On Sun, May 10, 2015 at 7:50 PM, Walty Yeung wal...@gmail.com wrote:

 hi ryan,

 thanks for your detailed instructions. two quick questions, just to make
 sure I did fully understand the suggestions:

 1.  Where could I get the changes of review? should I read the timeline
 page (http://trac.edgewall.org/timeline)? Or is there some other places I
 could read the reviews?


Yeah, following the timeline (you can subscribe in an RSS feed reader) is
the way to keep track of progress on the project, as well as subscribing to
trac-users and trac-dev mailing lists.


 2. I currently checked out the trunk version of trac, and set up a
 development environment in my mac. So, would u suggest to set up virtualbox
 of ubuntu and windows to do a through testing before submitting the
 patches? Or I could do that a little bit later?


To start with I think it's perfectly fine to develop on just the Mac. We'll
review your patches for platform-related issues and run the tests before
committing. At least, I always intend to do that, but even when I introduce
issues on other platforms or even forget to run the tests, the issues are
usually caught by the other devs very quickly. We have automated testing
running on Linux via Travis CI, and eventually I hope we can setup to test
for Windows on AppVeyor (1). I think I recall seeing the other day a
similar service for OSX, but I'd have to dig in my notes to be sure.

As a first step, I suggest just trying to run the tests (2, 3) on your OSX
machine. Read the output and you'll probably find some tests being skipped,
suggesting that you need to install more dependencies. I imagine you'll run
into an unresolved issue I encountered when starting to develop on the Mac
a few weeks back (3), or perhaps you'll find an entirely new issue! Either
way, it's good to establish that baseline and know what to expect from the
tests on your platform before you start editing code.

Starting out with Trac development is also a great opportunity to show us
where we can improve the documentation for new developers. There are many
things we'll have overlooked after working on the project for some time.
Any suggestions are welcomed!

(1) http://www.appveyor.com/
(2) http://trac.edgewall.org/wiki/TracDev/UnitTests
(3) http://trac.edgewall.org/wiki/TracDev/FunctionalTests
(4) http://trac.edgewall.org/ticket/12022

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] about starting point of contribution

[Ryan Ollos]

On Sat, May 9, 2015 at 9:59 PM, Walty Yeung wal...@gmail.com wrote:

 hi,

 I have been using trac for 5+ years now, and I really love the simple and
 yet powerful design of whole thing.

 I have modified the source code of trac myself, to add some more tools for
 the use of our company (internally).

 and now I would like contribute back to the Trac project. I have read the
 wiki of http://trac.edgewall.org/wiki/HowToContribute, and briefly
 checked the coding style, unit test, and patch submitting mechanism.

 and my question is, is the bite-sized tasks (
 http://trac.edgewall.org/query?status=newstatus=assignedstatus=reopenedkeywords=~bitesizedgroup=componentorder=priority)
 still the optimal entry point of contribution now? I asked only  because I
 saw most of the tickets there are actually pretty old, and I am not sure if
 they are actually outdated now, however, I don't mind to start with the
 minor changes at all.

 thanks.


Hello Walty,

We would be very happy to have you contribute. Thank you for getting
started by seeking out and reading the right documents.

Bite-sized tickets are a good place to get started so that we can bring you
up to speed on how we develop Trac, including things that may not have
(yet) been documented. You are right that the bite-sized tasks are not up
to date. We haven't done a good job lately of marking tickets as
bite-sized. I'll plan to review and mark tickets as bite-size in the next
several days.

In the meantime, you could find some very relevant tickets to work on by
surveying the tickets assigned to next-stable-1.0.x and next-dev-1.1.x:
http://trac.edgewall.org/milestone/next-stable-1.0.x
http://trac.edgewall.org/milestone/next-dev-1.1.x

Those are tickets we've determined should be fixed on the maintenance
branch for 1.0 or the development branch for 1.2. We certainly won't get to
all of them by the time 1.2 is released, so we would sure appreciate help
in knocking out some of those.

We are currently preparing the next release, hoping to finish today. After
that we will dive into developing for the next milestones. I've found that
a good way to learn is to checkout the changes that other devs post for
review, code review the changes and run the tests. It always helps to have
the tests executed on one more platform. When I started working on the
project I found at least a half-dozen issues with the tests that were due
to my developing on a platform with a different configuration than the
other devs.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] 1.0.6 and 1.1.5 releases

[Ryan Ollos]

On Wed, Apr 29, 2015 at 2:49 AM, Christian Boos christian.b...@free.fr
wrote:

 On 4/27/2015 7:18 PM, Ryan Ollos wrote:
  The next releases (1.0.6 and 1.1.5) are scheduled for Monday May 4th (I
  modified the milestone due date over the weekend, previously it was May
  1st). I'm going to try to create the releases early Monday morning of
  May 4th (GMT), which means we should wrap up changes by mid-day Sunday
  (GMT). The release steps are simplified quite a bit now and I'll be
  focusing on getting this release out on time.

 Sounds good! Unfortunately I won't be able to assist, being away from my
 workstation for a few weeks. But you seem to have everything under
 control by now anyway.

 
  The milestones that follow are 1.0.7 and 1.1.6, scheduled for July 1st
  2015. If things go well and we are in a good position for a 1.2 release
  following 1.1.6, then the 1.2 release could happen later in the month.
  That would give some time after 1.1.6 to pull in translations and ask
  for extensive beta testing of 1.1.6. That implies no enhancements, just
  fixes, between 1.1.6 and 1.2.

 However I'll have time to catch-up reading my mail and contribute to the
 previous discussions I missed on Trac-dev, notably the 1.2 roadmap and
 what's beyond. Some of the ideas I'll try to develop would be to focus
 on Python 2.7, find a way out of the Genshi trap and modernize the UI,
 doing more stuff client-side and have the Python backend go back to
 generate the data only (only, JSON instead of HDF this time ;-) ).


That sounds great. I have a short document outlining some features I'll
propose to implement in 1.3.x. I look forward to discussing those and
hearing more about your ideas for the modernization.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] 1.0.6 and 1.1.5 releases

[Ryan Ollos]

The next releases (1.0.6 and 1.1.5) are scheduled for Monday May 4th (I
modified the milestone due date over the weekend, previously it was May
1st). I'm going to try to create the releases early Monday morning of May
4th (GMT), which means we should wrap up changes by mid-day Sunday (GMT).
The release steps are simplified quite a bit now and I'll be focusing on
getting this release out on time.

The milestones that follow are 1.0.7 and 1.1.6, scheduled for July 1st
2015. If things go well and we are in a good position for a 1.2 release
following 1.1.6, then the 1.2 release could happen later in the month. That
would give some time after 1.1.6 to pull in translations and ask for
extensive beta testing of 1.1.6. That implies no enhancements, just fixes,
between 1.1.6 and 1.2.

We should think about how we'll support the 1.0.x line after 1.2 is
released. I'd like to push only critical fixes to 1.0.x after 1.2 is
released, but please let me know your thoughts.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] ApiChanges document

[Ryan Ollos]

On Sun, Apr 19, 2015 at 10:20 AM, Peter Suter petsu...@gmail.com wrote:

  On 26.03.2015 20:56, RjOllos wrote:

 I thought about it some more. We could:
  * Have an ApiChanges/1.1 page with annotations showing the 1.1.x release
 in which a change was made.
  * Remove the 1.1.x annotations when preparing ApiChanges/1.2.

  The result is two pages with distinct information. ApiChanges/1.1 page
 is easy to create because it can be edited incrementally as tickets are
 closed out. ApiChanges/1.2 is easy to create because the only necessary
 steps are copying 1.1 and deleting some content. That can easily be done
 just prior to the 1.2 release.

 I created ApiChanges/1.1, merging ApiChanges/1.1.1 to 1.1.5 and adding
 version annotations.
 http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1

 We could delete these pages now:
 http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.1
 http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.2
 http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.3
 http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.4
 http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.5

 Or maybe better just replace them with a redirection link to 1.1.


Thanks for taking care of that. I'm okay with deleting the pages, but if we
want to be more conservative we could leave them with the redirect until
1.2 is released, deleting them in about 6 months.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] WIki page retirement

[Ryan Ollos]

On Mon, Apr 13, 2015 at 2:58 PM, figaro stijn.bouwh...@gmail.com wrote:

 The following pages are candidates to be deleted:
 http://trac.edgewall.org/wiki/ApiDocs
 http://trac.edgewall.org/wiki/VersioningSystemBackend
 http://trac.edgewall.org/wiki/ClueMapper (but has referencing page here:
 https://pypi.python.org/pypi/ClueMapper/0.7)
 http://trac.edgewall.org/wiki/TracDev/ScratchPad/DefaultTheme

 What to do with the following page?:
 http://trac.edgewall.org/wiki/TracUninstall


We probably want to keep the page below ScratchPad, but the others look
like they can be removed. As for uninstalling, I'm not there is much value
to documenting the brief steps of removing the egg and the site-packages
entry, but we could add a section to the TracInstall page. For anyone that
may be concerned in the future about uninstalling Trac, I suggest either
installing through a package manager or installing in a virtualenv so that
the entire virtualenv can be deleted when you wish to uninstall.

I'll remove the pages in a few days if there are no further comments.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Ticket change validation

[Ryan Ollos]

On Thu, Mar 26, 2015 at 3:34 AM, Emmanuel BOUAZIZ 
emmanuel.boua...@gmail.com wrote:

 Hi,

 I'm looking to add a simple ticket change validation to our Trac (i.e
 prevent to close the ticket if some conditions are not met).

 I figured that a simple plugin implementing ITicketManipulator would be
 nice and wrote a basic one for test purpose, but it only works for
 modifications made from the web interface, and I'd like to be able to
 validate the modifications made from the trac commit hooks too.

 I tried to put the extension point in the Trac PreCommitHook like it is in
 the TicketModule but it fails because CommitHook's are not Component's.

 The remaining solution appears to be writing a piece of code that makes
 the validation and call it from both the pre-commit-hook and a Trac plugin
 implementing ITicketManipulator.


As far as I know that is your best option. You could implement the
IAdminCommandProvider interface and call the command from the pre-commit
hook . You could model this after CommitTicketUpdater and
DbRepositoryProvider:
http://trac.edgewall.org/browser/trunk/tracopt/ticket/commit_updater.py?rev=13600marks=160,167#L158
http://trac.edgewall.org/browser/trunk/trac/versioncontrol/api.py?rev=13846marks=118,140#L115

There is some related discussion in #10125:
http://trac.edgewall.org/ticket/10125

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] ApiChanges document

[Ryan Ollos]

On Wed, Mar 25, 2015 at 2:19 PM, Peter Suter petsu...@gmail.com wrote:

  I'd probably also merge the current 1.1.x pages.


Thanks, I'll do this in a few days if no one objects, after double-checking
that all of the documentation from earlier releases in now contained in
ApiChanges/1.1.5.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.1.4 Released

[Ryan Ollos]

Trac 1.1.4 Released
===

Trac 1.1.4 continues the 1.1.x development line
leading to 1.2 with some new features and a few
not-so-disruptive changes.

Note that the 1.1.x releases are stable and
tested snapshots of the trunk.  They can be seen
as sub-milestones on the road towards Trac 1.2. As
opposed to maintenance releases, *we offer no
guarantees on feature and API compatibility from
one 1.1.x release to the next*.

However, by following 1.1.x you get a chance to
use new features earlier, and therefore be able to
contribute feedback when things are still in flux.
It's also less risky than just getting the latest
trunk, as we won't cut a 1.1.x release in the middle
of a series of changes (though we had and still intend
to have a good record of keeping things always working
on trunk).

The intended audience are therefore enthusiast Trac
users and Trac plugin developers. These packages should
*not* be integrated in distributions, for example.

Here are a few highlights:

 - Performance improvements with MySQL/MariaDB (#3676).
 - Click on //Permissions// Admin page table row toggles
   all checkboxes in the row (#11417).
 - Configuration sections are written to trac.ini when
   enabling a component through TracAdmin or the web
   administration module (#11437).
 - Subscription rules can be reordered by drag and drop
   (#11941).

Besides the few issues listed here, the fixes made for
1.0.4 and 1.0.5 are also included.

You can find all the detailed release notes at:

 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#DevelopmentReleases
 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Download URLs:

  http://download.edgewall.org/trac/Trac-1.1.4.tar.gz
  http://download.edgewall.org/trac/Trac-1.1.4.win32.exe
  http://download.edgewall.org/trac/Trac-1.1.4.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.1.4.zip

MD5 sums:

  89a6fcdad8ad251b43db5c4517b8603b  Trac-1.1.4.zip
  bc35487b49b7e017d6c89ad9b5e23ba9  Trac-1.1.4.tar.gz
  7d628ff5b372319ed104987163ff9797  Trac-1.1.4.win32.exe
  2b11461fb5c8262122e902eb2fe14872  Trac-1.1.4.win-amd64.exe

SHA1 sums:

  34d6b72421918ea7f87896c53c6f198d3ccbbd4f  Trac-1.1.4.zip
  c7c2e19767fd22e3b9000f3f27299bd799043012  Trac-1.1.4.tar.gz
  b53c562edcc328a371e928c4d0d6f8d597657b7b  Trac-1.1.4.win32.exe
  a1884a9b5cff506ddeee535b44139f2a94a385e4  Trac-1.1.4.win-amd64.exe

Enjoy!

- The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.5 Released

[Ryan Ollos]

Trac 1.0.5 Released
===

Trac 1.0.5, the fifth maintenance release for the
current stable branch, is now available!

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.5

Trac 1.0.5 provides several fixes. The following
are some highlights:

 - Images are not rendered in the timeline (#10751).
 - Git tags are shown in the browser view (#11964).
 - Added support for `journal_mode` and `synchronous`
   pragmas in `sqlite:` database connection string
   (#11967).

You can find the detailed release notes for 1.0.5 on
the following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases


Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.5.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.5.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.5.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.5.zip

MD5 sums:

  17449de4359f71f3c40b894b70ea52d0  Trac-1.0.5.zip
  1146c849f926f9eeb8448569159b29e0  Trac-1.0.5.tar.gz
  987c2c891f5d13ad5eac006cc01290c1  Trac-1.0.5.win32.exe
  d61f149b4b6733e2776b93421afa6b9d  Trac-1.0.5.win-amd64.exe

SHA1 sums:

  87274c88e901ab809fd9d363175007a6648c7ef9  Trac-1.0.5.zip
  83d27bbdd62691a5f8e5ca83c3e28187004c8ebe  Trac-1.0.5.tar.gz
  9b1fa285e5458927df86cf1d9de18e33b5fdf55e  Trac-1.0.5.win32.exe
  8dcc716ce756fea878e2716c0275d32477107ee3  Trac-1.0.5.win-amd64.exe


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 offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will be
an improvement over the last version.

Please let us know.:-)

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Cookbook recipe: document management system

[Ryan Ollos]

On Mon, Mar 16, 2015 at 2:09 PM, figaro stijn.bouwh...@gmail.com wrote:

 It irks me that Trac is not recognised as offering document management
 system capabilities here:
 http://en.wikipedia.org/wiki/Trac
 and more importantly here:
 http://en.wikipedia.org/wiki/Comparison_of_project_management_software

 There is a write up of the success with Trac as a DMS here:
 http://trac.edgewall.org/ticket/1267#comment:7
 I like to start a recipe page with the findings and some of my own
 experiences, for example under a new page CookBook/Configuratiopn.
 /DocumentManagement. How can this be done?


I think you should feel free to just create the page if you have some
content to place there. Just type in the URL of the page and you'll find a
//Create page// button.

http://trac.edgewall.org/wiki/CookBook/Configuration/DocumentManagement

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Wiki page retirement

[Ryan Ollos]

On Sun, Feb 22, 2015 at 5:41 AM, figaro stijn.bouwh...@gmail.com wrote:

 When updating the Trac wiki pages created over the years, the following
 pages can be retired:

 http://trac.edgewall.org/wiki/CruiseControl
 http://trac.edgewall.org/wiki/TracReleaselist
 http://trac.edgewall.org/wiki/TracPlugins_64bitOS
 http://trac.edgewall.org/wiki/FitLibrary (requires removal of link on
 wiki:FIT)
 http://trac.edgewall.org/wiki/FitServer (requires removal of link on
 wiki:FIT)
 http://trac.edgewall.org/wiki/PluginTutorial
 http://trac.edgewall.org/wiki/TracOnUbuntuBreezer
 http://trac.edgewall.org/wiki/TracOnRedhat9HomeDir
 http://trac.edgewall.org/wiki/TracOnUbuntuBreezyWorkingenv
 http://trac.edgewall.org/wiki/TracOnSlackware
 http://trac.edgewall.org/wiki/TracOnSlackwareTenPointTwo
 http://trac.edgewall.org/wiki/TracOnDebianFromTrunk
 http://trac.edgewall.org/wiki/TracOnFedoraCoreFour (superseded by
 http://trac.edgewall.org/wiki/TracOnFedoraCore)
 http://trac.edgewall.org/wiki/TicketButcher
 http://trac.edgewall.org/wiki/TicketGnome
 http://trac.edgewall.org/wiki/LiteSpeed (
 http://trac.edgewall.org/wiki/TracLitespeed is meant)
 http://trac.edgewall.org/wiki/RewriteRule
 http://trac.edgewall.org/wiki/IrcGems
 http://trac.edgewall.org/wiki/WikiMacroObjects
 http://trac.edgewall.org/wiki/GoogleSoc
 http://trac.edgewall.org/wiki/GoogleSoc2007
 http://trac.edgewall.org/wiki/LocationMatch
 http://trac.edgewall.org/wiki/TracVersions (superseded by roadmap?)
 http://trac.edgewall.org/wiki/HighLevelTesting

 There are the following approaches to retire pages:

 (1) http://trac.edgewall.org/wiki/MacroBazaar?action=diffversion=227
 (2) http://trac.edgewall.org/wiki/SilverCityAddLanguage
 (3) http://trac-hacks.org/wiki/TagsPlugin
 (4) http://trac.edgewall.org/ticket/9222

 Least intrusive is option 3, which therefore has my preference.


I agree that all those pages can be removed. I was being conservative with
the edits in (1), but if others agree I think we can just remove all those
pages immediately, leaving MacroBazaar and ProcessBazaar for removal in a
few months.

In the future, implementing (3) and (4) would allow us to have a better
process for removing pages. TagsPlugin would allow pages to be tagged as
deprecated, and easily tracked for removal.


Has the functionality of the following page been adopted somewhere in core?:
 http://trac.edgewall.org/wiki/TaskJuggler


It's not in the core. I think the page can be removed.


 Is the following page an allegory to something else?
 http://trac.edgewall.org/wiki/HowToMakeCoffee


I agree with removing that page as well, unless someone has a nostalgic
feeling towards it.

Related issue, the following page was created yesterday. We should consider
relocating it to a more suitable hierarchy:
http://trac.edgewall.org/wiki/TracOnWindowsIisWfastcgi

Perhaps below the following page:
http://trac.edgewall.org/wiki/CookBook/Installation

However, other hierarchies have been proposed:
   https://groups.google.com/d/msg/trac-dev/nkMUY_8ILF0/No2wHxQD0dUJ
   https://groups.google.com/d/msg/trac-dev/nkMUY_8ILF0/6gSu22CtzUgJ

The author left their email when creating the page, so we could contact to
inform that the page has been relocated. In general, a slight bit of this
kind of change moderation can be a good thing towards having a more
structured wiki.

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: Licensing and joining procedure WAS: [Trac-dev] Re: trac-hacks organization on GitHub

[Ryan Ollos]

On Sat, Feb 21, 2015 at 7:21 PM, Olemis Lang ole...@gmail.com wrote:

 Just an initial comments : at least in (all) my browser(s) trac-hacks
 image/icon overflows available space .


I haven't been able to determine the cause of that issue. It is captured in:
http://trac-hacks.org/ticket/12169


 On 2/21/15, RjOllos rjol...@gmail.com wrote:
  On Thursday, February 19, 2015 at 5:54:55 PM UTC-8, RjOllos wrote:
 
 [...]
 
  We have a trac-hacks organization on GitHub (2).
 [...]
 
  I've started by inviting a bunch of users to join the trac-hacks
  organization. I found those users through a search for trac plugin and
  filtering the false positives. I've received a half-dozen positive
  responses in the first few hours, so you'll see more repositories
  appearing
  on the organization page.
 
  If you have a GitHub repository that you'd like to associate with the
  organization, please contact me or just reply here.

 In the last few years I've developed quite a few Trac plugins ,
 extensions even whole projects from scratch . Some of them have been
 developed for a third-party . Therefore licensing is different (e.g.
 GPL) and owners might want to retain their (ownership / central point
 of distribution / copyright) over the plugin rather than yielding
 control to the Trac-Hacks organization and being owners indirectly .


Summarizing the existing, somewhat informal policies: anyone publishing a
plugin to trac-hacks retains full control over the plugin, until such time
as they voluntarily give up the plugin or can no longer be reached.  Plugin
authors are free to choose the license for their plugin. So far we don't
even prevent publishing of software on trac-hacks for which the source code
is not provided.

Several times Steffen (hasienda) and I have discussed the need for more
formal policies that are developed by the community. So far neither of us
has found the time to push this effort though.


 Nevertheless there might be an interest for being indexed in there .
 Is there anything that can be done in this case ?


Anyone is free to create a wiki page on trac-hacks.org that contains links
to an external issue tracker, repository, etc ...

The only thing I would ask of potential hack creators, and this is not a
formal rule that has been written by the community but rather something
that just seems sensible to me, is that you don't create the hack until the
external project exists and is actually usable. Over the years there have
been several hacks created for projects that are never developed. These
just take up space and eventually one of us has to remove them. If you wish
to create a page in order to develop a plugin in a trac-hacks repository,
that is a different scenario and it makes sense to create the hack in order
to have a place to work from.


 OTOH could you please clarify (maybe a blog post is better) the items
 below ?

 1. how is the repository setup ?
 - e.g. permissions / ownership but not limited to that


There is a Admin access team associated with each repository. The user
who transfers the repository becomes the sole member of the Admin access
team for the repository. No other users have write-access to the
repository unless granted by the repository author. Admin access team
permissions are described here:
https://help.github.com/articles/permission-levels-for-an-organization-repository/#repository-access-teams

2. how to join the organization @ Github ? IOW
 - Only repositories join the organization ?
 - Will plugin authors join the organization as well ? How ?


Plugin authors join the organization along with their repositories.

I proposed in the blog post that anyone with an interest in trac-hacks may
join the organization. Unfortunately it appears that I must send an invite
to every user; there is no way for a user to request an invite through the
trac-hacks organization page on GitHub. I sent an inquiry to GitHub about
this yesterday but so far haven't received a reply. So if you'd like an
invite, just let me know.

With the features provided by GitHub this is the best way I could see to
setup the organization. It's a work-in-progress, so feedback is good in
helping to improve the process. If anyone hits a roadblock in trying to do
something, please post to the list.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] trac-hacks organization on GitHub

[Ryan Ollos]

On Feb 19, 2015 6:47 PM, Christopher Nelson chris.nelson.1...@gmail.com
wrote:

 I'd be thrilled to move Trac-jsGantt and maybe a couple of others to
 Git; Subversion on T-H makes me crazy. ;-)

Is your Github username ChrisNelson or did I just send an invite to someone
else?

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Files in Trac distribution

[Ryan Ollos]

On Fri, Feb 13, 2015 at 6:39 PM, Jun Omae jun6...@gmail.com wrote:

 On Mon, Feb 9, 2015 at 3:14 PM, RjOllos rjol...@gmail.com wrote:
  INSTALL (5) and UPGRADE (6) duplicate what is provided in TracInstall (7)
  and TracUpgrade (8). Would it be sufficient to just put a link to the
 wiki
  docs in the files? The link could direct to either the documentation in
 the
  distribution or to the t.e.o wiki.

 Linking to the documentation in the distribution sounds good. INSTALL
 and UPGRADE files already navigate the files in the default-pages
 directory.

   9 **You should also read the trac/wiki/default-pages/TracInstall
  10 documentation file present in the source distribution.**
  11
  12 If you're upgrading an already installed Trac environment, please also
  13 read trac/wiki/default-pages/TracUpgrade.

 However, I assume that users read INSTALL and UPGRADE files on the
 user's terminal. TracInstall and TracUpgrade file have too long lines
 (over 80 columns).


That sounds good. I'll test out the script.

Regarding the other pages
 - The ChangeLog file could point to ChangeLog on the wiki, and ChangeLog
could be included in the default-pages as TracChangeLog.
 - RELEASE contains content from TracDev/ReleaseNotes/1.0, but also points
to that page for more detailed info. As far as I can see it's probably best
to leave that file as it is. Besides, it's only updated for major releases.

ChangeLog will likely need some edits to replace TracLinks with
InterTracLinks and full URLs.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac's supported dependencies

[Ryan Ollos]

On Mon, Feb 9, 2015 at 9:40 AM, Greg Troxel g...@ir.bbn.com wrote:


 Jun Omae jun6...@gmail.com writes:

  I mean it that disagree against dropping support for SVN 1.6 in Trac
 1.2.x.
 
  Hummm, I would agree dropping SVN 1.6 if it means that Trac 1.2.x is
  likely to work with SVN 1.6, but the version is not officially
  supported.

 I still am having trouble understanding the thought process here.  Why
 do people think it's ok to stay with old subversion but not to stay with
 old trac (1.0.x)?


I am with you on that.

It still potentially hurts us if we can't make incompatible changes with
SVN 1.6.

I don't agree with having Trac held back so that users running old versions
of Red Hat can run the latest version of Trac. Those users can run an old
version of Trac, after all they are running an old version of SVN, so they
are apparently okay with not having the latest and greatest of everything.
If they don't want to run an old version of Trac they can upgrade their OS.
Everything has a cost, and going out of our way to support old platforms
will slow the project. That's why I was hoping we could adopt a rule, such
as supporting the latest version from a set of informally supported OS's
available at the time of a major release. That would imply we should target
RHEL7/CentOS7 with the next major release, 1.2.

Assuming we do try to maintain compatibility with RHEL6/CentOS6, I was even
more concerned that we'd have to continue supporting Python 2.6 for the
next several years due to RHEL6/CentOS6. It appears at least they provide
Python 2.7:
http://rpmfind.net/linux/rpm2html/search.php?query=pythonsubmit=Search+...system=arch=

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac's supported dependencies

[Ryan Ollos]

On Mon, Feb 9, 2015 at 9:47 AM, Ryan Ollos rjol...@gmail.com wrote:

 On Mon, Feb 9, 2015 at 9:40 AM, Greg Troxel g...@ir.bbn.com wrote:


 Jun Omae jun6...@gmail.com writes:

  I mean it that disagree against dropping support for SVN 1.6 in Trac
 1.2.x.
 
  Hummm, I would agree dropping SVN 1.6 if it means that Trac 1.2.x is
  likely to work with SVN 1.6, but the version is not officially
  supported.

 I still am having trouble understanding the thought process here.  Why
 do people think it's ok to stay with old subversion but not to stay with
 old trac (1.0.x)?


 I am with you on that.

 It still potentially hurts us if we can't make incompatible changes with
 SVN 1.6.

 I don't agree with having Trac held back so that users running old
 versions of Red Hat can run the latest version of Trac. Those users can run
 an old version of Trac, after all they are running an old version of SVN,
 so they are apparently okay with not having the latest and greatest of
 everything. If they don't want to run an old version of Trac they can
 upgrade their OS. Everything has a cost, and going out of our way to
 support old platforms will slow the project. That's why I was hoping we
 could adopt a rule, such as supporting the latest version from a set of
 informally supported OS's available at the time of a major release. That
 would imply we should target RHEL7/CentOS7 with the next major release, 1.2.

 Assuming we do try to maintain compatibility with RHEL6/CentOS6, I was
 even more concerned that we'd have to continue supporting Python 2.6 for
 the next several years due to RHEL6/CentOS6. It appears at least they
 provide Python 2.7:

 http://rpmfind.net/linux/rpm2html/search.php?query=pythonsubmit=Search+...system=arch=



I didn't setup that filter correctly and it appears the info isn't
available through that database.  From a quick search it appears that
RHEL6/CentOS6 may not provide Python 2.7:
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/
http://distrowatch.com/table.php?distribution=redhat

Dropping support for Python 2.6 is an issue really worth discussing.
Keeping supporting for Python 2.6 indefinitely is something that will
really slow us down and make it even harder to get to Python 3.x someday.
We have already committed to supporting Python 2.6 in Trac 1.2.x, but I'd
like to drop support for Python 2.6 starting with 1.3.1. I'm really tired
of testing on multiple versions of Python and worrying about using
incompatible features. The situation has gotten better now that we don't
develop Trac 0.12.x, which supports Python 2.4, but we still have to worry
about Python 2.5 in Trac 1.0.x, and I'm eager to move on. By this time next
year it would be ideal if development was focused on 1.3.x and we only had
to test against Python 2.7.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.4 Released

[Ryan Ollos]

Trac 1.0.4 Released
===

Trac 1.0.4, the fourth maintenance release for the
current stable branch, is now available!

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.4

Trac 1.0.3 was release on 17th of January and contained a significant
regression that is corrected in this release.

 - Workflow action labels were not displayed unless name
   attribute was explicitly defined (#11930)

You can find the detailed release notes for 1.0.4 on the
following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases


Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.4.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.4.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.4.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.4.zip

MD5 sums:

  a47d56333d1b4ae18a81bd1a9a5a4e8e  Trac-1.0.4.zip
  20f1f76b4d993cecab13b7b4a93547f5  Trac-1.0.4.tar.gz
  d90cf917d71d8cb6256994fbb28bb38b  Trac-1.0.4.win32.exe
  bd50070355a40a577c4f1eb5b80534bb  Trac-1.0.4.win-amd64.exe

SHA1 sums:



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 offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will be
an improvement over the last version.

Please let us know.:-)

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac's supported dependencies

[Ryan Ollos]

On Sun, Feb 8, 2015 at 7:26 AM, Steffen Hoffmann hoff...@web.de wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 08.02.2015 07:19, Ryan Ollos wrote:
  In general I think it's sufficient to say that we will aim to support
  the most recent LTS release with each major release of Trac, provided
  the LTS release has been out for a while, say 6 months. I'm most
  familiar with Ubuntu and Debian, so I would say that we should aim to
  support Ubuntu 14.04 and Debian 7 with the 1.2 release of Trac.

 Nit-pick: At least from Debian side it should rather be Debian 8, as
 long as Trac 1.2 is not right around the corner. I don't know so much
 about Ubuntu.

 Steffen Hoffmann


In a recent thread I proposed around May 1st for the Trac 1.2 release, but
it's still too soon to say for sure,
https://groups.google.com/d/msg/trac-dev/09KHkId-deE/Mg8M6jt-uywJ

A quick search didn't yield a release date for Debian 8, do you know of one?

Ubuntu provides an LTS release every 2 years. The most recent was 14.04,
the next will be 16.04 (April 2016).
https://wiki.ubuntu.com/LTS

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] MacroBazaar and ProcessorBazaar

[Ryan Ollos]

On Sun, Feb 8, 2015 at 7:09 PM, Ryan Ollos rjol...@gmail.com wrote:

 On Sun, Feb 8, 2015 at 12:14 AM, Peter Suter petsu...@gmail.com wrote:

 On 08.02.2015 04:47, RjOllos wrote:

 suggestion I'm seeking feedback on is to just remove all the content
 from the pages and keep the notice directing users to trac-hacks.org.
 The content would still be retained in the page history. Further, all
 links to these pages could be removed from the documentation on t.e.o
 (4), (5).


 I'm in favour. The heaps of ancient content on the t.e.o. wiki pages can
 be overwhelming and confusing.


 That's a good point. I'm not sure we want to keep pages around forever if
 they are no longer relevant, even on the small chance an external page is
 linking to it. If the information is obsolete, I favor eventually removing
 the page.


 What do you plan to do with the ~100 attachments? Removing them will not
 leave them in the page history. I think it could still be preferable to
 delete them. I imagine they do more harm than good.
 Maybe explicitly pre-announce a removal date in the deprecation notice?


 I hadn't thought about the attachment. With that in mind, what if we just
 announce that the page will be completely deleted in say 6 months, and
 immediately remove all TracLinks to the pages?



For example, http://trac.edgewall.org/wiki/LegendBox

In the long term, it could be nice to implement:
http://trac.edgewall.org/ticket/9222

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac's supported dependencies

[Ryan Ollos]

On Sun, Feb 8, 2015 at 7:37 PM, Jun Omae jun6...@gmail.com wrote:

 On Sun, Feb 8, 2015 at 3:19 PM, Ryan Ollos rjol...@gmail.com wrote:
  The issue of which versions we support has come up in the following case
 -
  Subversion 1.6 is no longer supported (1) and I'm considering
 implementing a
  change that would be supported in Subversion 1.7, but not in 1.6 (2). It
  would be great if we could drop support for Subversion 1.6 in Trac 1.2,
 but
  I feel there should be a formal process for approaching this.

 -1 to dropping support for 1.6.

 RHEL6/CentOS6 provide full updates until 2017Q2. Subversion 1.6.11 is
 used in the distributions.


It would be helpful if you could clarify.

Are you:
 - Against dropping support for SVN 1.6 until 2017Q2?
 - Against dropping support for SVN 1.6 in Trac 1.0.x?
 - Against dropping support for SVN 1.6 in Trac 1.2.x?

What about when we start development on the 1.3.x line? (which could be as
early as May 2015)

If RHEL6/CentOS6 provides full updates, why haven't they updated to a
version of Subversion that is supported by the Subversion team? Which
version of Trac is currently provided by RHEL6/CentOS6?

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] MacroBazaar and ProcessorBazaar

[Ryan Ollos]

On Sun, Feb 8, 2015 at 12:14 AM, Peter Suter petsu...@gmail.com wrote:

 On 08.02.2015 04:47, RjOllos wrote:

 suggestion I'm seeking feedback on is to just remove all the content
 from the pages and keep the notice directing users to trac-hacks.org.
 The content would still be retained in the page history. Further, all
 links to these pages could be removed from the documentation on t.e.o
 (4), (5).


 I'm in favour. The heaps of ancient content on the t.e.o. wiki pages can
 be overwhelming and confusing.


That's a good point. I'm not sure we want to keep pages around forever if
they are no longer relevant, even on the small chance an external page is
linking to it. If the information is obsolete, I favor eventually removing
the page.


 What do you plan to do with the ~100 attachments? Removing them will not
 leave them in the page history. I think it could still be preferable to
 delete them. I imagine they do more harm than good.
 Maybe explicitly pre-announce a removal date in the deprecation notice?


I hadn't thought about the attachment. With that in mind, what if we just
announce that the page will be completely deleted in say 6 months, and
immediately remove all TracLinks to the pages?

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac's supported dependencies

[Ryan Ollos]

On Sun, Feb 8, 2015 at 1:59 AM, Peter Suter petsu...@gmail.com wrote:

 On 08.02.2015 09:50, Peter Suter wrote:

 [3] http://trac.edgewall.org/wiki/TitleIndex
 [4] http://trac.edgewall.org/wiki/TracOnArchLinux
 [5] http://trac.edgewall.org/wiki/TracOnArkLinux
 [6] http://trac.edgewall.org/wiki/TracOnGentoo
 [7] http://trac.edgewall.org/wiki/TracOnLeopardServer
 [8] http://trac.edgewall.org/wiki/TracOnMandrakelinux
 [9] http://trac.edgewall.org/wiki/TracOnMandriva
 [10] http://trac.edgewall.org/wiki/TracOnNetBsd
 [11] http://trac.edgewall.org/wiki/TracOnOpenBSD
 [12] http://trac.edgewall.org/wiki/TracOnOpenSolaris
 [13] http://trac.edgewall.org/wiki/TracOnSolaris
 [14] http://trac.edgewall.org/wiki/TracOnSlackware

 Reorganization of these pages in a TracOnPlatform/* hierarchy might be
 helpful for keeping a [[TitleIndex(./)]] of all platforms.


 Or under the existing TracInstallPlatforms page. [15]

 [15] http://trac.edgewall.org/wiki/TracInstallPlatforms


Reorganizing the pages in a hierarchy seems like a good idea. We could
leave a redirect on the old page for some time, and then delete the page
after 6 months or 12 months ... whatever is deemed a sufficient amount of
time.

Would having a real redirect macro in the core help, particularly one that
returns the proper HTTP status code for a moved page? Something like:
http://trac-hacks.org/wiki/ServerSideRedirectPlugin

The more difficult issue is determining when to remove the pages because
they are so out-of-date as to do more harm than good. It would be really
nice if we had dedicated maintainers of the pages for each platform. In
absence of that, I guess the only thing to do is to run through each one
and decide whether to update or remove it.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac's supported dependencies

[Ryan Ollos]

Trac has a number of required and optional dependencies across all its
modules. I've attempted to compile a complete list:
http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.4

The issue of which versions we support has come up in the following case -
Subversion 1.6 is no longer supported (1) and I'm considering implementing
a change that would be supported in Subversion 1.7, but not in 1.6 (2). It
would be great if we could drop support for Subversion 1.6 in Trac 1.2, but
I feel there should be a formal process for approaching this.

In some cases we have not been explicit (as far as I know) about what
versions of the dependencies we support. A good place to start would be to
have an informal list of platforms that we are aiming to support. We can
then use that list to decide which versions of the dependencies we'll aim
to support. For example, although Subversion 1.6 is now unsupported by the
Subversion developers, we would want to continue to support it if it was
provided by the official package manager of one the versions of the
platforms we are aiming to support.

The list of platforms I came up with is: Ubuntu, Debian, Red Hat / CentOS,
Fedora, Suse / OpenSuse, FreeBSD, Windows, Windows Server, Mac OSX.

What are people using that I overlooked?  It might be a good question to
raise in a dedicated thread on trac-users.

In general I think it's sufficient to say that we will aim to support the
most recent LTS release with each major release of Trac, provided the LTS
release has been out for a while, say 6 months. I'm most familiar with
Ubuntu and Debian, so I would say that we should aim to support Ubuntu
14.04 and Debian 7 with the 1.2 release of Trac.

What I have in mind is to compile a list of platforms we support, and then
list the versions of the dependencies provided by the platforms. From that
we can generate the table of supported dependencies. If this seems like a
good plan, I'm hoping that those familiar with the platforms can help
generate the list.

Another motivation is, it's burdensome to fix issues associated with old
packages. If we don't state that, for example, Pygments  1.0 is
unsupported (1.0 was released in 2008) and someone finds an issue with 0.6,
then in my mind we are obligated to fix the issue. Even if Trac will work
with a 5 year old dependency, it would be better to just head off potential
issues and enforce a requirement in the codebase, or at least specify it in
the documentation.

Thank you for any input on the issue!

- Ryan


(1)
https://subversion.apache.org/docs/release-notes/1.8.html#svn-1.6-deprecation
(2) http://trac.edgewall.org/ticket/11703#comment:5

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Roadmap to Trac 1.2

[Ryan Ollos]

On Thu, Jan 22, 2015 at 11:48 AM, Peter Suter petsu...@gmail.com wrote:

 On 21.01.2015 08:00, Ryan Ollos wrote:

 Some other features that have been worked and look promising for
 inclusion in the release are:
   - PyGit2 plugin
   - #8172: Plugin db upgrade infrastructure
   - #10672: Automatically minify Javascript and CSS
   - #11676: Reusable commenting module


 I neglected this a bit, focusing more on notifications. It might be good
 to include new interfaces and DB tables in at least one development release
 (i.e. 1.1.x or 1.3.x etc.) before freezing them for long-term compatibility
 in a stable release (like 1.2).

  What do others have in mind to include in the release? The question
 isn't only for current committers, but I'm hoping to hear from people
 that would be willing to step up and implement the changes as opposed to
 please include feature X.


 The other notification improvements might keep me be busy for a bit.

  I'd like to see 1.1.5 be released as 1.2, but if we aren't ready by May
 1st, then release 1.2 on July 1st along with 1.0.6. After that I'm
 hoping we can release the minor versions on yearly intervals, which
 would be every 6th maintenance release.


 Sounds great.

  Looking forward to 1.2, is it too early to think about dropping support
 for Python 2.6 and support Python 2.7 and 3.3+ from a single codebase?


 Has anyone tried Trac on Python 3?
 On #10083 I see SVN and HG will be unlikely. I guess that's less
 important now that Git is so popular.
 http://trac.edgewall.org/ticket/10083

 For HG a command-server backend would be an interesting option.
 http://trac.edgewall.org/ticket/10411

 Trac 1.0 still supports Python 2.5. Maybe Trac 1.2 should still support
 Python 2.6?


Yeah I think that Trac 1.2 will support Python 2.6. However, as soon as 1.2
is released we start development on the 1.3.x line and we'll need to decide
what to support in 1.3.x, which determines what will be supported in 1.4.

Even if we don't officially support Python 3.3+ for Trac 1.4, dropping
support for 2.6 should allow us to start making more modifications that
will lead to a smoother transition to supporting 3.3+. I haven't looked
closely at the specifics though.


  Finally, we still need a codename for the release, so that is something
 to think about as well.
 http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#CodeName


 Added my suggestion. :)


Looks like we have a few choices now. I think we should give the old
guard (Jonas, Christian, Remy) the first shot at picking the name. If they
don't want to make the choice, we could hold a vote in a trac-dev thread.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Roadmap to Trac 1.2

[Ryan Ollos]

On Wed, Jan 21, 2015 at 9:54 AM, Greg Troxel g...@ir.bbn.com wrote:


 Ryan Ollos rjol...@gmail.com writes:

Change of scheme to store numbers as numbers, rather than as strings,
and generally to thereby use database consistency checking.
 
  There are many columns in the database that store values as int and
 int64.
  Do you have some specific fields in mind?
  http://trac.edgewall.org/browser/trunk/trac/db_default.py

 I think I really meant ticket_custom, which loses type safety for pretty
 much everything that isn't a string.


It looks like #10040 has a patch for the behavior you are requesting:
http://trac.edgewall.org/ticket/10040

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Roadmap to Trac 1.2

[Ryan Ollos]

On Wed, Jan 21, 2015 at 5:35 AM, Christopher Nelson 
chris.nelson.1...@gmail.com wrote:

  ...
  In addition to the tickets currently assigned to 1.0.4 and 1.1.4, there
 are
  a few key features that I'd like to implement for 1.2:
   - #11469: Custom field admin panel
   - #1233: Components and Versions become first-class objects in the
  TicketSystem with their own Roadmap-like pages, TracLinks, macros,
  permissions, ...
   - #3098: Repository README rendering
 
  Some other features that have been worked and look promising for
 inclusion
  in the release are:
   - PyGit2 plugin
   - #8172: Plugin db upgrade infrastructure
   - #10672: Automatically minify Javascript and CSS
   - #11676: Reusable commenting module
 
  What do others have in mind to include in the release? The question isn't
  only for current committers, but I'm hoping to hear from people that
 would
  be willing to step up and implement the changes as opposed to please
  include feature X.

 http://trac.edgewall.org/ticket/10983 is important to me.  If the
 patch needs rework, I'd be happy to do that.


Thanks, I'll take a look in a few days and follow-up in the ticket if it
looks like there are any issues remaining with the patch.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Roadmap to Trac 1.2

[Ryan Ollos]

On Wed, Jan 21, 2015 at 7:17 AM, Greg Troxel g...@ir.bbn.com wrote:


 Ryan Ollos rjol...@gmail.com writes:

  It seems like a good time to discuss what we plan to deliver for Trac
 1.2,
  and when we will deliver it. So far I see one big feature, and some
  components that have been significantly improved:

 The two things that I'd like to see long term (separate from what should
 be in 1.2 or when there will be code) are:

   Integration of ticket dependencies into the base; this seems too
   fundamental to make optional.  There are two kinds of dependencies:
   one is parent/child for hierarchical WBS (for task/enhancement
   tickets), and the other is blocking (for those, or for defects).  With
   mastertickets you can one or the other, or have it be a little
   confused and do both.


That is one of the features I have in mind for development in 1.3.x. The
BloodhoundRelationsPlugin looks promising for backporting into Trac.
http://trac.edgewall.org/ticket/31#comment:180


   Change of scheme to store numbers as numbers, rather than as strings,
   and generally to thereby use database consistency checking.

  Looking forward to 1.2, is it too early to think about dropping support
 for
  Python 2.6 and support Python 2.7 and 3.3+ from a single codebase? As we
  get close to releasing 1.2 I'll raise another thread to talk about what
  features we have in mind for development in the 1.3.x line.

 From the pkgsrc viewpoint, dropping 2.6 is fine, as 2.6 is getting
 pretty crufty.


-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Roadmap to Trac 1.2

[Ryan Ollos]

It seems like a good time to discuss what we plan to deliver for Trac 1.2,
and when we will deliver it. So far I see one big feature, and some
components that have been significantly improved:

 - Enhanced notification system
 - Time custom fields
 - Numerous minor enhancements to the TracWorkflow

We've dropped support for Python 2.5 and removed a lot of deprecated code
from the API, which will make Trac easier to develop going forward. There
have been numerous minor enhancements to functionality, lots of tidying of
the user interface and I like the improvements that Christian has been
working on for the ticket changelog view. It's always nice to have a new
look for pages when we push out a new release.

In addition to the tickets currently assigned to 1.0.4 and 1.1.4, there are
a few key features that I'd like to implement for 1.2:
 - #11469: Custom field admin panel
 - #1233: Components and Versions become first-class objects in the
TicketSystem with their own Roadmap-like pages, TracLinks, macros,
permissions, ...
 - #3098: Repository README rendering

Some other features that have been worked and look promising for inclusion
in the release are:
 - PyGit2 plugin
 - #8172: Plugin db upgrade infrastructure
 - #10672: Automatically minify Javascript and CSS
 - #11676: Reusable commenting module

What do others have in mind to include in the release? The question isn't
only for current committers, but I'm hoping to hear from people that would
be willing to step up and implement the changes as opposed to please
include feature X.

With a bimonthly release schedule, the next two releases will be:
March 1: 1.0.4 and 1.1.4
May 1: 1.0.5 and 1.1.5

I'd like to see 1.1.5 be released as 1.2, but if we aren't ready by May
1st, then release 1.2 on July 1st along with 1.0.6. After that I'm hoping
we can release the minor versions on yearly intervals, which would be every
6th maintenance release.

Somewhere in there we should release Trac 0.12.7 as well, after pulling the
latest translations from Transifex for several languages.

Looking forward to 1.2, is it too early to think about dropping support for
Python 2.6 and support Python 2.7 and 3.3+ from a single codebase? As we
get close to releasing 1.2 I'll raise another thread to talk about what
features we have in mind for development in the 1.3.x line.

Finally, we still need a codename for the release, so that is something to
think about as well.
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#CodeName

I'm looking forward to hearing comments, and excited to push out some more
releases!

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.1.3 Released

[Ryan Ollos]

Trac 1.1.3 Released
===

Trac 1.1.3 continues the 1.1.x development line leading to 1.2
with some new features and a few not-so-disruptive changes.

Note that the 1.1.x releases are stable and tested snapshots
of the trunk.  They can be seen as sub-milestones on the road
towards Trac 1.2. As opposed to maintenance releases,
*we offer no guarantees on feature and API compatibility
from one 1.1.x release to the next*.

However, by following 1.1.x you get a chance to use new features
earlier, and therefore be able to contribute feedback when things
are still in flux. It's also less risky than just getting the
latest trunk, as we won't cut a 1.1.x release in the middle
of a series of changes (though we had and still intend to have a
good record of keeping things always working on trunk).

The intended audience are therefore enthusiast Trac users and Trac
plugin developers. These packages should *not* be integrated in
distributions, for example.

Here are a few highlights:

 - The ticket creation step can be configured in the TracWorkflow
   and the workflow controls are present on the NewTicket
   page (#2045).
 - New notification system that can be extended by plugins (#3517).
 - New preferences panel for notification subscriptions (#4056).
 - Wiki page version comments can be edited by users with
  `WIKI_ADMIN` (#6573).
 - Improved positioning of //Add Comment// section and //author//
   field on the ticket form (#10207).
 - The delete confirmation pages warn if attachments will also
   be deleted (#11542).
 - Removed support for SilverCity, Enscript and PhpRenderer
   syntax highlighters (#11795).
 - Combined //Date  Time// and //Language// preference panels
   as //Localization// (#11813).
 - Groups and permissions can be used in the workflow
   `set_owner` attribute (#11839).

Besides the few issues listed here, the fixes made for 1.0.3 are also
included.

You can find all the detailed release notes at:

 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#DevelopmentReleases
 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases

Download URLs:

  http://download.edgewall.org/trac/Trac-1.1.3.tar.gz
  http://download.edgewall.org/trac/Trac-1.1.3.win32.exe
  http://download.edgewall.org/trac/Trac-1.1.3.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.1.3.zip

MD5 sums:

  d4358eef1ee1e6a899368e3b4dcb9de1  Trac-1.1.3.zip
  5a882ddffc33743b885a145b977b0847  Trac-1.1.3.tar.gz
  dbc258b8a88f86ab428187751dfdb3ee  Trac-1.1.3.win32.exe
  77757ed80de03c837294b252d4b117bb  Trac-1.1.3.win-amd64.exe

SHA1 sums:

  624d1255475541c031719dca2cfe43690deed827  Trac-1.1.3.zip
  f6edb7f685a31f869b9dcc813168c2c3097f206d  Trac-1.1.3.tar.gz
  d78ddf0c697772606699dd90c5a76cafb0f8981c  Trac-1.1.3.win32.exe
  c01879221c6bd9fec7857bd8d0972e5ccb71d2c6  Trac-1.1.3.win-amd64.exe

Enjoy!

- The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.3 Released

[Ryan Ollos]

Trac 1.0.3 Released
===

Trac 1.0.3, the third maintenance release for the
current stable branch, is now available!

You will find this release at the usual places:

  http://trac.edgewall.org/wiki/TracDownload#LatestStableRelease
  https://pypi.python.org/pypi/Trac/1.0.3

Trac 1.0.3 was release in October 2014 and we've provided over
40 fixes and minor enhancements since then.

A few highlights from this release:

 - Notification is sent when adding an attachment to a ticket (#2259).
 - Stylesheets and scripts are loaded during autopreview, resulting
   in proper syntax highlighting when code WikiProcessors are added
   (#10470) and display of Workflow graphs without explicit
   autopreview (#10674).
 - Merge changesets are shown as differences against first parent,
   resulting in less noisy changesets (#10740).
 - Pygments 2.0 is supported (#11796).
 - Fixed error when completing the `initenv` TracAdmin command
   (#11797).
 - Performance improvement on systems with many thousands of
   authenticated users due to caching of Environment.get_known_users
   (#11868).
 - Distribution metadata of wheel package is supported and displayed
   on the About page (#11877).

You can find the detailed release notes for 1.0.3 on the
following pages:
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases


Now to the packages themselves:

URLs:

  http://download.edgewall.org/trac/Trac-1.0.3.tar.gz
  http://download.edgewall.org/trac/Trac-1.0.3.win32.exe
  http://download.edgewall.org/trac/Trac-1.0.3.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.0.3.zip

MD5 sums:

  89681f15d6c27aa68c4d45d569807c87  Trac-1.0.3.zip
  6a0e05e95782d2c807491540234d9bc7  Trac-1.0.3.tar.gz
  7ea0358a53028cc079727bcc2ba5551d  Trac-1.0.3.win32.exe
  64fba69c2f2811feddd23f4962d633d0  Trac-1.0.3.win-amd64.exe

SHA1 sums:



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 offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will be
an improvement over the last version.

Please let us know.:-)

/The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Proposed additions to coding guidelines

[Ryan Ollos]

Over the past several months I've accumulated in my notes a few items that
I would like to add to the coding guidelines (1). I'm seeking feedback on
these changes before editing the wiki.

 - Use trailing underscore to avoid conflicts with built-in keywords. I've
seen this practice sparingly in the codebase and it's actually suggested in
PEP-0008, but we have many instances of variables such as id, so I think
it would be good to add this point to the CodingStyle document.
 - On the trunk (Python 2.6+) we can start using str.format() rather than
the string interpolation operator. Should str.format() be preferred?
 - The brackets are unnecessary in Genshi template variable. My suggestions
is that $var be preferred to ${var}
 - Generally I seem to prefer putting the properties / attributes before
methods in class definitions, but I tend to think that's something I
picked-up from C++ and maybe shouldn't be a guideline.

I'll add more item here for comment when I think of them. Thanks for any
feedback.

(1) http://trac.edgewall.org/wiki/TracDev/CodingStyle
(2) https://www.python.org/dev/peps/pep-0008/#descriptive-naming-styles

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.0.3 / 1.1.3

[Ryan Ollos]

I've previously proposed a 2 month release schedule, which suggests Jan 1st
for the next set of releases. We've closed 36 tickets for 1.0.3 and 32
tickets for 1.1.3.

I currently have 20 tickets in-progress and would like to close out a few
of these; the rest will be moved forward. I propose a code freeze on
1.0-stable and trunk on Jan 1st and I would then create the release by Jan
5th. I'm interested to hear thoughts from other developers on this schedule.

Nothing, to my knowledge, has been done for Trac 0.12.7. The main task
we've discussed is to pull the latest translations from Transifex. If
nothing is done soon for 0.12.7, then I suggest we just postpone that
release but go ahead with 1.0.3 and 1.1.3.

Release ticket for 1.0.3 / 1.1.3: http://trac.edgewall.org/ticket/11827

Next milestones - 1.0.4 and 1.1.4:
http://trac.edgewall.org/milestone/1.0.4
http://trac.edgewall.org/milestone/1.1.4

- Ryan

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Git performance in Trac (was: [Trac-dev] trac-hacks group on GitHub)

[Ryan Ollos]

On Thu Dec 04 2014 at 1:40:57 AM W. Martin Borgert deba...@debian.org
wrote:

 Quoting Peter Suter petsu...@gmail.com:
  On 03.12.2014 16:40, Christopher Nelson wrote:
  On 2014-06-22 12:12, Olemis Lang wrote:
  I'm not very fond of git at all , TBH . It does not integrate well
  with Trac ,
  OT: This is a major problem for Trac. Nothing against hg, but Git
  is currently the most successful VCS. If Trac will not improve
  its Git support, people will move away from Trac, not from Git.
 
  Could you give more details about what you mean? Why does git not
  integrate well? How would improved git support look like? What's
  missing that hg has?

 Olemis Lang can probably compare git with hg in Trac.

 For me, there are two problems:

   1. No nice integration. With typical/simple hooks, the same commits
  get referenced (#refs) in tickets again and again when merging and
  branching.  Worse, if you had a commit closed by a commit
  (#closes), but had to reopen later, it gets closed again just by a
  merge!

  What is missing is a list of commits already processed, so that
  Trac doesn't list the same commit multiple times. Or a more
  flexible approach, e.g. if one maintains ticket specific branches,
  link all changes in the respective branch in the ticket, but also
  show merges into master or a release branch.

  Good hook scripts for different workflows should be part of the
  Trac distribution in the contrib directory.

   2. Performance for large repositories. Try to import the linux kernel
  source and actually use it. It works neither with nor without
  cache, it is too slow to use. Cache creation took many hours on my
  notebook computer, btw.


I have 2 questions:
 1. Have you assessed the performance of Trac 1.0.2 with large repositories?
 2. Have you evaluated Jun's PyGit2Plugin? The plugin may be part of Trac
by the 1.2 release and is available on trac-hacks:
http://trac-hacks.org/wiki/TracPygit2Plugin

It's true that there are a lot of issues that can be improved with Trac,
but it should be clear from the number of Git-related issues fixed in 1.0.2
and the availability of an alternate connector for Git that things are
improving.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Re: Trac 1.0.2 released

[Ryan Ollos]

On Mon, Nov 3, 2014 at 10:47 AM, Dirk Stöcker t...@dstoecker.de wrote:

 Hello,

 it seems Trac 1.0.2 is delivered with the help texts of 1.1.x instead of
 the 1.0.x version.

 Probably this is not really wanted?

 Ciao
 --
 http://www.dstoecker.eu/ (PGP key available)



What evidence do you have of that?

There were a few edits on the TracFineGrainedPermissions page that were
only applicable to 1.1.2 and were not rolled back before the release. Jun
corrected these a few day ago:

http://trac.edgewall.org/wiki/TracFineGrainedPermissions?sfp_email=sfph_mail=action=diffversion=55old_version=54sfp_email=sfph_mail=

Other than that I'm not aware of any 1.1.x documentation on the 1.0.x
branch. You can inspect all the changes that went into 1.0.2 here:

http://trac.edgewall.org/changeset?sfp_email=sfph_mail=reponame=new=13120%40branches%2F1.0-stable%2Ftrac%2Fwiki%2Fdefault-pagesold=11674%40branches%2F1.0-stable%2Ftrac%2Fwiki%2Fdefault-pagessfp_email=sfph_mail=

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 1.0.2 released

[Ryan Ollos]

On Mon, Nov 3, 2014 at 6:20 AM, falkb fbrettschnei...@baumer.com wrote:

 Thanks a lot for the release and the priceless effort behind it! :-)
 Is there already an idea when 1.1.x is planned to become a stable one?
 Cheers,
  F@lk


It is undecided at this point, but I had in mind 6 months to 1 year from
now, depending on the progress of new features.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] MAJOR t.e.o error and ticket report

[Ryan Ollos]

On Sun, Nov 2, 2014 at 12:11 PM, Dirk Stöcker t...@dstoecker.de wrote:

 Hello,

 reporting tickets is not possible ATM:
 AttributeError: 'Environment' object has no attribute 'get_db_cnx'


I saw the issue for a moment but it seems to be fixed now. I assume the
site was just being updated to 1.1.3 and the issue with the VotePlugin was
spotted immediately.


 Also admin pages don't come up (BTW could someone update spamfilter plugin
 :-)

 There is an big problem in Trac 1.0.2 - Export of raw data is broken for
 larger files. The chunked data transfer stops in the middle. See the bug
 report in JOSM tracker:

 http://josm.openstreetmap.de/ticket/10692

 Ciao
 --
 http://www.dstoecker.eu/ (PGP key available)

 --
 You received this message because you are subscribed to the Google Groups
 Trac Development group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to trac-dev+unsubscr...@googlegroups.com.
 To post to this group, send email to trac-dev@googlegroups.com.
 Visit this group at http://groups.google.com/group/trac-dev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] How much longer should we continue to maintain the 0.12.x release line?

[Ryan Ollos]

On Sun, Oct 26, 2014 at 6:15 AM, Christian Boos christian.b...@free.fr
wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 10/26/2014 9:01 AM, Remy Blank wrote:
  RjOllos wrote:
  I'm hopeful that we can have a 2-month release cycle going
  forward, with the next release by Jan 1st. That set of releases
  will include 0.12.7.
 
  I don't have any interest in the 0.12 release line, but of course
  I will continue to fix issues on the branch until we have
  agreement that it should be dropped and 1.0.x made our LTS
  release. What do others have in mind, particularly the other
  devs?
 
  I'm not really qualifying as a dev anymore, and I tend to have a
  radical view on such issues, but I would make the just-released
  0.12.6 the last release on the 0.12 branch, and only patch it for
  security issues.
 
  Rationale: the dev team is small, and the time that you guys can
  spend on Trac (thanks a lot, BTW!) should be spent on new features
  and bug fixes, not on maintenance.
 
  Here is one proposal: - 0.12.7 / 1.0.3 / 1.1.3: Jan 2015

 Here's a middle ground: I basically agree with what Remy said, except
 that 0.12.6 wasn't announced as being the last release. Maybe there
 are still people blocked with Python 2.4(?) and hoping for a few last
 bugfixes(?). We could announce that 0.12.7 will be the last bugfix
 release for 0.12.x and if there are people who still care about this
 line of development, here's their chance to bring forward their
 patches! After 0.12.7, only have releases for important security fixes
 (and that could still go on for a while, without much additional work).

 Also, make clear that 0.11.x will no longer be updated, even for
 security fixes (and remove it from TracDownload).

 - -- Christian


Having a final planned release on 0.12.x sounds like a friendly transition.
How should we go about announcing this? Is the discussion in this thread
along with some edits to the wiki enough, or should we post a formal
message to the trac-announce channel?

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] How much longer should we continue to maintain the 0.12.x release line?

[Ryan Ollos]

On Sun, Oct 26, 2014 at 12:57 AM, Peter Suter petsu...@gmail.com wrote:

On 26.10.2014 05:12, RjOllos wrote:

 I'm hopeful that we can have a 2-month release cycle going forward, with
 the next release by Jan 1st. That set of releases will include 0.12.7.


 2-month release cycle would be great. It sounds very ambitious, but you
 now probably know best if and how it is achievable.

 I assume this means a simplified release process e.g. without
 string-freeze periods? (Personally I think the faster iteration time would
 more than compensate any drawbacks.)


It will probably be a bit challenging, but should be much more achievable
as we tweak and script more of the release process. I think there are some
small things that we can do, such as #11725, which together will make the
whole process a bit easier. Even just having a smaller set of tickets will
make writing the change log easier, or we can do that part as we progress
through the milestone.

trac.edgewall.org/ticket/11725

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Re: Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Fri, Oct 24, 2014 at 12:25 PM, Dirk Stöcker t...@dstoecker.de wrote:

 On Fri, 24 Oct 2014, RjOllos wrote:

  The releases are available on the TracDownload page and on PyPI.
 Announcement email forthcoming in a few hours.


 I'd prefer when the source releases e.g. used by easy_install don't have
 \r\n as line endings and use \n instead. It's pretty ugly on Unix
 systems.

 Ciao


The tar.gz release should have \n line endings. The zip release should
have \r\n. So just easy_install using the tar.gz release on Unix.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Re: Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Sat, Oct 25, 2014 at 1:00 AM, Jun Omae jun6...@gmail.com wrote:

 On Sat, Oct 25, 2014 at 4:46 PM, Ryan Ollos rjol...@gmail.com wrote:
  On Fri, Oct 24, 2014 at 12:25 PM, Dirk Stöcker t...@dstoecker.de
 wrote:
 
  On Fri, 24 Oct 2014, RjOllos wrote:
 
  The releases are available on the TracDownload page and on PyPI.
  Announcement email forthcoming in a few hours.
 
 
  I'd prefer when the source releases e.g. used by easy_install don't have
  \r\n as line endings and use \n instead. It's pretty ugly on Unix
  systems.
 
  Ciao
 
 
  The tar.gz release should have \n line endings. The zip release should
  have \r\n. So just easy_install using the tar.gz release on Unix.

 The easy_install prefers zip archive even if Unix if both tar.gz and
 zip archives exist, like this.


The case willneed to be made why we should favor one particular set of line
endings. Supposing \r\n causes problems on Unix (I don't know, I've never
noticed any problems), does \n not cause any problems on Windows?

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[Trac-dev] Trac 1.1.2 released

[Ryan Ollos]

Trac 1.1.2 Released
===

Trac 1.1.2 continues the 1.1.x development line leading to 1.2
with some new features and a few not-so-disruptive changes.

Note that the 1.1.x releases are stable and tested snapshots
of the trunk.  They can be seen as sub-milestones on the road
towards Trac 1.2. As opposed to maintenance releases,
*we offer no guarantees on feature and API compatibility
from one 1.1.x release to the next*.

However, by following 1.1.x you get a chance to use new features
earlier, and therefore be able to contribute feedback when things
are still in flux. It's also less risky than just getting the latest trunk,
as we won't cut a 1.1.x release in the middle
of a series of changes (though we had and still intend to have a
good record of keeping things always working on trunk).

The intended audience are therefore enthusiast Trac users and Trac
plugin developers. These packages should *not* be integrated in
distributions, for example.

Here are a few highlights:

 - Dropped support for Python 2.5. Trac can no longer be run on
   Python 2.5 as incompatible changes have been made in the
   source code (#11600).
 - The new ticket workflow action `may_set_owner` is similar to
   `set_owner` but the owner defaults to the existing ticket
   owner rather than the current user (#10018).
 - The new option `[ticket]` `optional_fields` specifies ticket
   select fields that are treated as optional (i.e. an empty value
   is allowed) (#10772).
 - Line number and row highlighting annotations can be specified
   for WikiProcessor code blocks (#10834).
 - The //default handler// can be set as a session preference
   (#11597), and the default value for all users can be set from
   the //Basic Settings// admin page (#11519).
 - Attachments can't be added to read-only wiki pages (#11244).
 - Tables on the admin pages have a //Select all// checkbox in
   the header (#10994).
 - Submit buttons are disabled if the required items are not
   selected (#11056).
 - The Admin //Permissions// page has a //Copy Permissions// form
   for copying permissions between users and groups (#11099).
 - The new option `[milestone]` `default_retarget_to` determines
   the default milestone for retargeting tickets when a milestone
   is deleted or closed, and can be specified from the
   //Milestone// admin page (#10010).
 - The //retarget// select is not shown when closing or deleting
   a milestone which has no tickets associated with it (#11366).
 - //Clear default// buttons allow the ticket system default value
   (e.g. `default_milestone`, `default_version`) to be cleared
   through the corresponding admin pages (#10772, #11300).
 - The `TitleIndex` macro supports relative path prefixes when used
   on wiki pages (#11455).
 - CommitTicketUpdater will recognize a ticket reference that
   includes a trailing `#comment:N` or `#comment:description`
   (#11622).
 - The //Tickets// column of the milestone table on the
   //Milestone// admin page contains links to the query page
   showing all tickets associated with the milestone, grouped
   by status (#11661).
 - Authz policy can be used to restrict access to the //Report List//
 page using the resource id `-1` (#11697).

Besides the few issues listed here, the fixes made for 1.0.2 and
0.12.6 are also included.

You can find all the detailed release notes at:

 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#DevelopmentReleases
 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases
 -
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.12#MaintenanceReleases

Download URLs:

  http://download.edgewall.org/trac/Trac-1.1.2.tar.gz
  http://download.edgewall.org/trac/Trac-1.1.2.win32.exe
  http://download.edgewall.org/trac/Trac-1.1.2.win-amd64.exe
  http://download.edgewall.org/trac/Trac-1.1.2.zip
http://download.edgewall.org/trac/Trac-1.1.1.zip

MD5 sums:

  32d7000abdc8bd7b7132c544e6512361  Trac-1.1.2.tar.gz
  ff33a630636549d24e0f558c539294ba  Trac-1.1.2.win32.exe
  2569b748e4bb53b5d65a7da59473b406  Trac-1.1.2.win-amd64.exe
  29ba27dacf1c1f65efae37881c2a5a6d  Trac-1.1.2.zip

SHA1 sums:

  0f2845d69551d135b635dbfc9211ef36f6797c50  Trac-1.1.2.tar.gz
  8737d9d4dce384a995741bd1c80a313e1c099181  Trac-1.1.2.win32.exe
  4eee91a9f983ec855f001eb8017481caafa8a566  Trac-1.1.2.win-amd64.exe
  b548489c514602c35cff7455c96de548c778d77f  Trac-1.1.2.zip

Enjoy!

- The Trac Team  http://trac.edgewall.org/

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Fri, Oct 24, 2014 at 3:46 PM, Ryan Ollos ryan.j.ol...@gmail.com wrote:

 On Fri, Oct 24, 2014 at 2:57 PM, falkb fbrettschnei...@baumer.com wrote:

 Hi,

 Am Freitag, 24. Oktober 2014 19:33:47 UTC+2 schrieb RjOllos:
  http://trac.edgewall.org/wiki/TracDownload

 I've tested the amd-64 one, and the result on my 64bit Windows 7 is a
 FAIL: After the first click on the Next button an error message appears
 saying No python installation found in the registry. After clicking OK,
 only Back and Abort buttons are active.



 I've tested also the 32-bit one on my 64bit Windows 7 and it's a FAIL as
 well: It is able to detect my Python-7 installation via registry in
 C:\Program Files\BitNamiTrac-1.0/python\Lib\site-packages\ but clicking the
 Next button two times crashes the installer application.

 CU, F@lk


 I don't know why it detected that location as the root of a Python
installation. C:\Program Files\BitNamiTrac-1.0/python might be correct, or
perhaps you misquoted that and it's actually the installation location:


[image: Inline image 3]


The 32-bit Trac package goes with the 32-bit Python package, and similarly
for the 64-bit version. It sounds like the only version of Python you have
installed is the one that came with your Bitnami installation. You should
install a standard Python package for your platform (e.g. C:\Python27),
either 32-bit or 64-bit (doesn't matter which you choose), but just make
sure to use the matching Trac installer for the Python package:
https://www.python.org/downloads

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Tue, Oct 7, 2014 at 1:04 AM, falkb fbrettschnei...@baumer.com wrote:

 Am Montag, 6. Oktober 2014 21:14:00 UTC+2 schrieb Peter Suter:



 amd-64 is for all x86-64 CPUs.



 I see. Could you please rename it to perhaps just 64. That amd is
 misleading and unusable.


win32 and amd64 are the suffixes generated by setuptools, but we could
change the latter to win64, or use x86 and x64.


 As the installer didn't work here, I suspected the reason is that it is
 designed for AMD CPUs, only.


No, it is just convention like Peter mentioned and as described in the
article he referenced.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Mon, Oct 6, 2014 at 12:01 AM, falkb fbrettschnei...@baumer.com wrote:


 Hi,
 what has happend to the Release again? Where are we now? What can we do to
 lift the stalled plane up again? I didn't understand whether you changed
 something in the Windows installers or not.
 CU, F@lk


I've been traveling for a few weeks so I haven't had access to a Windows
development machine to do any testing myself. I haven't heard from anyone
other than you about testing the installers. I'll be home on Thursday and
will do some testing at that time.

If you'd like to try creating the dist packages again or further debugging
the issue you experienced, the steps for creating the dist packages can be
found here:
http://trac.edgewall.org/wiki/TracDev/ReleaseChecklist#Createdistpackages

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Sep 23, 2014 12:23 PM, ryan.j.ol...@gmail.com wrote:



 On Friday Sep 19, 2014 at 8:35 PM, falkb fbrettschnei...@baumer.com,
wrote:

 I tried http://download.edgewall.org/trac/Trac-1.0.2beta1.win32.exe
 
http://www.google.com/url?q=http%3A%2F%2Fdownload.edgewall.org%2Ftrac%2FTrac-1.0.2beta1.win32.exesa=Dsntz=1usg=AFQjCNFH_0dekgL-vUO6PwI3G0XPxz3qNA

 on Win7 64bit, but the installer hangs after I've chosen the pathes of
 Python and install dir and went to the next page and clicked on the Next
 button. Then I tried the 1.0.2beta amd-64bit installer on the same
machine
 (although I don't have an AMD CPU), but a click on the first Next button
of
 the installer just says No python installation found in the registry
and
 returns to the installer page where's just Cancel works then and aborts
 the installation.
 CU, F@lk

Thanks for testing.  I built the packages with Python 2.7 on windows 8. We
might need to create them again.  I won't have an opportunity to test on
Windows and debug potential issues until Oct 9th, so hopefully someone else
can try. I should be able to test on Linux soon

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Wed, Aug 27, 2014 at 1:55 AM, falkb fbrettschnei...@baumer.com wrote:

 Hi,

 What is the news with the release? Are you stuck again somewhere? How can
 I help?

 CU, F@lk


Just need to confirm that the installation steps are correct when using
setuptools 5.4 - 5.6, and taking into consideration the warnings we added
to the docs and the patch that will soon be committed,
http://trac.edgewall.org/ticket/11694#comment:20

Unfortunately I'm very busy at my day job until Friday, so not sure if I
will find time before this weekend.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] mod_python still not recommended?

[Ryan Ollos]

On Fri, Aug 22, 2014 at 12:26 AM, Franz f.ma...@web.de wrote:

 Hi,

 as I reinstalled my test system, I found that Trac do NOT recommend
 mod_python, because it is *not actively maintained anymore* [1] and As
 of 16th June 2010, the mod_python project is officially dead [2]. But
 when I check web-site of mod_python [3] it has released two new versions in
 2013. This means to me that it is still actively maintained.

 I installed mod_python on ubuntu 14.04, but it appearently installed an
 older (?) version 3.3.1 of mod_python: libapache2-mod-python
 (3.3.1-11ubuntu2)

 Should the hint in [1] and [2] be removed or are they still valid?

 [1] http://trac.edgewall.org/wiki/TracInstall#RunningTraconaWebServer
 [2] http://trac.edgewall.org/wiki/TracModPython
 [3] http://modpython.org/

 Best regards,
 Franz


Yes, the project was revived (1). I proposed and a wait and see approach,
as to whether the mod_python project continues to be maintained (2).

We should probably update those pages, but I'm unsure of what to say at
this point. Maybe something non-committal such as //The mod_python project
has been revived and Trac continue to have mod_python support.//

(1) https://groups.google.com/d/msg/trac-users/1VzLgLT4gDE/wJsTOFl1QDMJ
(2) http://trac.edgewall.org/ticket/11605#comment:34

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Project local plugins

[Ryan Ollos]

On Mon, Aug 4, 2014 at 7:13 AM, Samuel Degrande samuel.degra...@lifl.fr
wrote:

 In my setup (using Trac 1.0), we have several projects, each of them
 inheriting from a common trac.ini.

 In the [inherit] section of the common trac.ini, I have a
 plugins_dir = /etc/forge/plugins

 That /etc/forge/plugins is empty.

 I use apache + mod_wsgi, and for each project, I set
 trac.env_path to /var/forge/projects/project_name/trac


 I added a plugin in the 'local' plugins dir of one of this project.
 (so in /var/forge/projects/that_project/trac/plugins)

 Despite what I expected, this plugin is available to all projects
 (and it is listed in the 'About Trac' page of all projects).

 Is that the expected behavior ? Did I something wrong ?


 Note: I have same behavior with 1.1.1, and afaik the private plugin
 was hidden from other projects in Trac  1.0 (but I may be wrong, it
 was 3 years ago...)


 Thx for your great work !


This is somewhat of a guess, but I would think that
 /var/forge/projects/that_project/trac/plugins must be on sys.path.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] About trac redirect

[Ryan Ollos]

On Thu, Aug 7, 2014 at 6:06 PM, Tian Hongjie tianhongji...@gmail.com
wrote:

  Hi,

 I see some redirect have been written in function, such as ticket _do_save
 function:

 def _do_save(self, req, ticket, action):
 # Save the action controllers we need to call side-effects for before
 # we save the changes to the ticket.
 controllers = list(self._get_action_controllers(req, ticket, action))

 # -- Save changes

 fragment = ''
 now = datetime.now(utc)
 cnum = ticket.save_changes(get_reporter_id(req, 'author'),
req.args.get('comment'), when=now,
replyto=req.args.get('replyto'))
 if cnum:
 fragment = '#comment:%d' % cnum
 try:
 tn = TicketNotifyEmail(self.env)
 tn.notify(ticket, newticket=False, modtime=now)
 except Exception, e:
 self.log.error(Failure sending notification on change to 
 ticket #%s: %s, ticket.id, exception_to_unicode(e))
 # TRANSLATOR: The 'change' has been saved... (link)
 change = _('change')
 if fragment:
 change = tag.a(change, href=fragment)
 add_warning(req, tag_(The %(change)s has been saved, but an 
   error occurred while sending 
   notifications: %(message)s,
   change=change, message=to_unicode(e)))
 fragment = ''

 # After saving the changes, apply the side-effects.
 for controller in controllers:
 self.log.debug(Side effect for %s %
controller.__class__.__name__)
 controller.apply_action_side_effects(req, ticket, action)

 *req.redirect(req.href.ticket(ticket.id http://ticket.id) + 
 fragment)*

 My question is could i redirect to home page writing some handler not
 rewrite this function only modify redirect which with underline?

 Thanks,
 Charlie



The following single-file plugin will redirect to the default handler when
//Submit changes// is pressed on the ticket page. It will not redirect on
ticket creation, comment edit and comment deletion.

from trac.core import Component, implements
from trac.ticket.web_ui import TicketModule
from trac.web.api import IRequestFilter


class RedirectOnTicketSave(Component):

implements(IRequestFilter)

def pre_process_request(self, req, handler):
if handler is TicketModule(self.env) \
and req.method == 'POST' and 'submit' in req.args \
and req.args['submit'] == 'Submit changes' \
and not req.args.get('preview'):
req.add_redirect_listener(ticket_save_listener)
return handler

def post_process_request(self, req, template, data, content_type):
return template, data, content_type


def ticket_save_listener(req, url, permanent):
if ticket_save_listener in req.redirect_listeners:
req.redirect_listeners.remove(ticket_save_listener)
req.redirect(req.href())


If I misunderstood your need, and instead you want to redirect on ticket
creation, you'll need to modify the conditions in pre_process_request. The
change req.args['submit'] == 'Submit changes'  - req.args['submit'] ==
'Create ticket' should be sufficient.  Additionally, the code below adds a
notice to indicate that the ticket has been created.

from trac.core import Component, implements
from trac.ticket.web_ui import TicketModule
from trac.util.translation import _
from trac.web.api import IRequestFilter
from trac.web.chrome import add_notice


class RedirectOnTicketSave(Component):

implements(IRequestFilter)

def pre_process_request(self, req, handler):
if handler is TicketModule(self.env) \
and req.method == 'POST' and 'submit' in req.args \
and req.args['submit'] == 'Create ticket' \
and not req.args.get('preview'):
req.add_redirect_listener(ticket_save_listener)
return handler

def post_process_request(self, req, template, data, content_type):
return template, data, content_type


def ticket_save_listener(req, url, permanent):
if ticket_save_listener in req.redirect_listeners:
req.redirect_listeners.remove(ticket_save_listener)
id = url.split('/')[-1]
add_notice(req, _(Ticket #%(id)s has been created., id=id))
req.redirect(req.href())

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit 

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Sun, Jul 27, 2014 at 11:55 AM, Ryan Ollos rjol...@gmail.com wrote:

 On Sat, Jul 26, 2014 at 2:14 AM, Christian Boos christian.b...@free.fr
 wrote:

 On 2014-07-26 7:20 AM, RjOllos wrote:
  On Friday, July 25, 2014 1:19:36 AM UTC-7, RjOllos wrote:
 
  It seems I have let this drag on through the week. I'm currently
  down to two tickets: #11684 and #10018. The latter is the important
  one since I think some regressions have been introduced. I'm aiming
  to resolve those by Saturday.
 
  Additionally it looks like Jun is working 3 Subversion-related
  tickets for 0.12.6. There are two more tickets, #11650 and #10207,
  both of which can probably be moved forward.
 
  I'll follow-up on Saturday or Sunday to see what the next steps
  might be.

 I'll be able to have some time on Sunday as well, maybe we could go
 through the steps of creating some beta1 releases first.


 I'm available for the next 10 hours or so, currently pushing some final
 changes to the codebase and will start looking at the release process. I'll
 be on IRC.

 Thanks for your help!



Just wanted to send a quick update on progress. I have some more work to do
updating the ChangeLog, and then a Wiki Page documentation sync (1). After
that I think we can create a beta1. So possibly tomorrow.

If any other devs have some free time and want to work on the ApiChanges
for 1.1.1 and 1.1.2, those pages will need more work (but I don't think
that will hold up the release since the changes don't get sync'ed into the
repository).

Please don't hesitate to correct any mistakes in the changes I've made to
the wiki or tickets!

http://trac.edgewall.org/wiki/TracProject/DefaultWikiPages#sync

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] New column for ticket group id

[Ryan Ollos]

On Sat, Aug 2, 2014 at 6:04 AM, Christopher Nelson 
chris.nelson.1...@gmail.com wrote:

  I want to add new column [ticket_type_id] in ticket table as group id for
  type.
  ...

 I thought ticket type was an enum already.  If it isn't, I'd add it to
 the enum table rather than restructure a standard table.


That is right. The name of the ticket type is stored in the ticket table.
If you want to get the ordering value, you would do a join of the ticket
and enum tables.
http://trac.edgewall.org/wiki/TracDev/DatabaseSchema/TicketSystem#Tableticket
http://trac.edgewall.org/wiki/TracDev/DatabaseSchema/TicketSystem#Tableenum

Given that the ticket_type_id doesn't look like the ordering value, I
guess you could add another column to the enum table, provided that a
simple TicketCustomField won't work in this case. But how are you going to
inject a form element into the ticket form for setting the value? I guess
you'd have to write a ITemplateStreamFilter to do that.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Edgewall group on GitHub

[Ryan Ollos]

On Fri, Jul 11, 2014 at 9:23 AM, Peter Suter petsu...@gmail.com wrote:

 On 07.07.2014 21:14, Ryan Ollos wrote:

 On Fri, Jul 4, 2014 at 11:57 PM, Jun Omae jun6...@gmail.com
 mailto:jun6...@gmail.com wrote:
 I just noticed that the mirror repository on github has enabled
 travis-ci testing by someone. See
 https://travis-ci.org/edgewall/trac/builds

 We could start testing on travis-ci once we add .travis.yml to each
 branch in subversion repository.


   That sounds great. I vote for adding the .travis.yml since there is no
 harm and we can always delete it later.


 Sounds cool.

 Would it make sense to document / link to this service somewhere on the
 wiki? Is this similar to the previous Automatic builds [1] and/or Python
 Community Buildbot [2]? (Neither seems to be available anymore. Perhaps
 their description should be removed instead.)


 Cheers,
 Peter

 [1] http://trac.edgewall.org/wiki/TracDev/UnitTests#Buildbots
 [2] http://trac.edgewall.org/wiki/TracDev/AutomaticBuilds


Those look like the right places to document the Travis CI service. It
might be good to just remove the section in [1] and add a link from there
to [2], updating [2] with new information about Travis CI. I'll plan to
update those eventually if you don't beat me to it.

It could be nice to have a dedicated mailing list for build notifications.
Looking at the current mailing lists [3], the Trac Tickets list is probably
too verbose for many people that would be interested in knowing about
failing builds. Maybe we could have a trac-bui...@edgewall.org?

[3] http://trac.edgewall.org/wiki/MailingList

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Sat, Jul 26, 2014 at 2:14 AM, Christian Boos christian.b...@free.fr
wrote:

 On 2014-07-26 7:20 AM, RjOllos wrote:
  On Friday, July 25, 2014 1:19:36 AM UTC-7, RjOllos wrote:
 
  It seems I have let this drag on through the week. I'm currently
  down to two tickets: #11684 and #10018. The latter is the important
  one since I think some regressions have been introduced. I'm aiming
  to resolve those by Saturday.
 
  Additionally it looks like Jun is working 3 Subversion-related
  tickets for 0.12.6. There are two more tickets, #11650 and #10207,
  both of which can probably be moved forward.
 
  I'll follow-up on Saturday or Sunday to see what the next steps
  might be.

 I'll be able to have some time on Sunday as well, maybe we could go
 through the steps of creating some beta1 releases first.


I'm available for the next 10 hours or so, currently pushing some final
changes to the codebase and will start looking at the release process. I'll
be on IRC.

Thanks for your help!

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Next release: Add git post-receive-hook to contrib dir?

[Ryan Ollos]

On Fri, Jul 18, 2014 at 3:30 PM, W. Martin Borgert deba...@debian.org
wrote:

 On 2014-07-17 13:28, W. Martin Borgert wrote:
  Now git is very popular and it would be nice to add a post-receive-hook
  as well. How about this one?
  http://trac.edgewall.org/attachment/wiki/TracGit/post-receive-hook.py

 Pardon, of course it's simpler now (from the Trac docs):

 #!/bin/sh

 while read oldrev newrev refname; do
 git rev-list --reverse $newrev ^$oldrev  | \
 while read rev; do
 trac-admin /path/to/trac/env changeset added a_repository $rev
 done
 done

 This works fine for me so far.


There's also been some recent discussion about this in #10730.

http://trac.edgewall.org/ticket/10730

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Trac 0.12.6 / 1.0.2 / 1.1.2

[Ryan Ollos]

On Wed, Jul 16, 2014 at 11:10 PM, Peter Suter petsu...@gmail.com wrote:

 On 17.07.2014 07:06, RjOllos wrote:

 On Wednesday, July 16, 2014 12:29:43 PM UTC-7, cboos wrote:
 Speaking about that (0.12.6 / 1.0.2 / 1.1.2), I'm ready to give any
 advice or even build the Windows parts, if needed. So Ryan, Jun and
 Peter, don't hesitate to ask me if you need anything.


 Maybe the main question is this:


 On 14.07.2014 07:43, RjOllos wrote:

 For the latter we'll certainly need assistance since I'm sure we don't
 have permissions to publish the release in various places.


 I.e. at the very end, how would we do the update steps in:
 http://trac.edgewall.org/wiki/TracDev/ReleaseChecklist#Finalizetherelease



 Thanks! It would be great to get a release out.

 I currently have about a half dozen tickets in progress. What I'm
 thinking is:

   - Close out those tickets by Friday 07/25
   - Spend the next few days reviewing the tickets that were closed in
 the release, testing, trying to catch anything that may have been
 overlooked initially. String freeze on Monday 07/28.
   - Allow the two weeks for translators to update the catalogs.
   - Prepare the release on 08/08 or later.

 How does that sound to the other devs?


 Sounds ok.

 Though I think tickets should not hold up a release except in rare cases
 (e.g. new bug in old functionality). Just move them to the next milestone.
 At this point, late/no releases are more damaging to the project than
 imperfect releases.



I need to commit a fix for a regression in #11610, and I think there is one
other small issue, but I can't recall at the moment.

I can accelerate the timeline and wrap things up by this Saturday. That
would give us the following timeline,

  1. Close out those tickets by Saturday 07/18
  2. Spend the next few days reviewing the tickets that were closed in

the release, testing, trying to catch anything that may have been
overlooked initially. String freeze on Monday 07/20.
  3. Allow the two weeks for translators to update the catalogs.
  4. Prepare the release on 08/01 or later.

I don't know the process well, so I can't comment on whether (3) can be
sped up.



 I'd also support a much simplified process, if reasonably possible via
 automation, otherwise via documentation and reduced flexibility / quality
 if needed.

 I'm personally not a user / contributor of translations and have never
 looked into that process, so maybe I'm totally wrong, but for example to me
 it would be acceptable to drop string freeze delays and force translators
 to use SVN etc. (or whatever process reduces complexity the most **for the
 release coordinator**).


 --
 You received this message because you are subscribed to the Google Groups
 Trac Development group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to trac-dev+unsubscr...@googlegroups.com.
 To post to this group, send email to trac-dev@googlegroups.com.
 Visit this group at http://groups.google.com/group/trac-dev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac-dev] Edgewall group on GitHub

[Ryan Ollos]

On Fri, Jul 4, 2014 at 11:57 PM, Jun Omae jun6...@gmail.com wrote:

 On Thu, Jul 3, 2014 at 6:49 PM, Jun Omae jun6...@gmail.com wrote:
  I just tried travis-ci. Matrix build works well under the following.
  ...
  https://travis-ci.org/jun66j5/trac/builds/29040035
  https://github.com/jun66j5/trac/blob/travis_0.12/.travis.yml

 I just noticed that the mirror repository on github has enabled
 travis-ci testing by someone. See
 https://travis-ci.org/edgewall/trac/builds

 We could start testing on travis-ci once we add .travis.yml to each
 branch in subversion repository.


 That sounds great. I vote for adding the .travis.yml since there is no
harm and we can always delete it later.

-- 
You received this message because you are subscribed to the Google Groups Trac 
Development group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.