Release Trac 1.6

[Ryan J Ollos]

Updated trunk/contrib/checkwiki.py​ in r17485. Jun, could you review the changes?

[Ryan J Ollos]

Some test failures appear to be random:

======================================================================
ERROR: runTest (trac.wiki.tests.functional.RegressionTestTicket10850)
Test for regression of https://trac.edgewall.org/ticket/10850
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/edgewall/trac/trac/wiki/tests/functional.py", line 471, in runTest
    pagename, filename='2012-09-11_15:36:40-test.tbz2')
  File "/home/travis/build/edgewall/trac/trac/tests/functional/tester.py", line 306, in attach_file_to_wiki
    replace, content_type)
  File "/home/travis/build/edgewall/trac/trac/tests/functional/tester.py", line 454, in _attach_file_to_resource
    regexp=False)
  File "/home/travis/build/edgewall/trac/trac/tests/functional/better_twill.py", line 176, in url
    .format(url, current_url))
AssertionError: URL didn't equal: 'http://127.0.0.1:43535/attachment/wiki/IbuprofenSnap/?action=new' != 'http://127.0.0.1:43535/wiki/IbuprofenSnap'

Maybe we should save geckodriver.log as a build artifact to help with debugging?

[Ryan J Ollos]

It looks like the New Ticket submit doesn't succeed in ​this case:

======================================================================
ERROR: runTest (trac.ticket.tests.functional.main.TestMilestoneDelete)
Delete a milestone and verify that tickets are retargeted
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/travis/build/edgewall/trac/trac/ticket/tests/functional/main.py", line 979, in runTest
    tid = self._tester.create_ticket(info={'milestone': name})
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/tester.py", line 101, in create_ticket
    tc.url('%s/ticket/%s#ticket' % (self.url, self.ticketcount + 1),
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/better_twill.py", line 175, in url
    raise AssertionError("URL didn't equal: {!r} != {!r}"
AssertionError: URL didn't equal: 'http://127.0.0.1:49972/ticket/63#ticket' != 'http://127.0.0.1:49972/newticket'

[Ryan J Ollos]

Not sure what happened ​here:

======================================================================
ERROR: runTest (trac.ticket.tests.functional.admin.TestAdminMilestoneDetail)
Admin modify milestone details
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/travis/build/edgewall/trac/trac/ticket/tests/functional/admin.py", line 298, in runTest
    self._tester.login('user')
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/tester.py", line 50, in login
    tc.find("Login")
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/better_twill.py", line 191, in find
    raise AssertionError("Regex didn't match: {!r} not found in {}"
AssertionError: Regex didn't match: 'Login' not found in file:///Users/travis/build/edgewall/trac/testenv/trac/log/TestAdminMilestoneDetail.html

[Ryan J Ollos]

======================================================================
ERROR: runTest (trac.wiki.tests.functional.TestWikiHistory)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/better_twill.py", line 415, in _find_by
    return driver.find_element_by_id(kwargs['id'])
  File "/Users/travis/venv-3.9/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 360, in find_element_by_id
    return self.find_element(by=By.ID, value=id_)
  File "/Users/travis/venv-3.9/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 976, in find_element
    return self.execute(Command.FIND_ELEMENT, {
  File "/Users/travis/venv-3.9/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "/Users/travis/venv-3.9/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: Unable to locate element: [id="edit"]
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/Users/travis/build/edgewall/trac/trac/wiki/tests/functional.py", line 153, in runTest
    self._tester.edit_wiki_page(pagename)
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/tester.py", line 289, in edit_wiki_page
    tc.formvalue('edit', 'text', content)
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/better_twill.py", line 209, in formvalue
    form_element = self._find_by(id=form)
  File "/Users/travis/build/edgewall/trac/trac/tests/functional/better_twill.py", line 426, in _find_by
    raise AssertionError('Missing element (%r, %r) in %s' %
AssertionError: Missing element ((), {'id': 'edit'}) in file:///Users/travis/build/edgewall/trac/testenv/trac/log/TestWikiHistory.html
----------------------------------------------------------------------

[anonymous]

Hi have you any idea when you will release 1.6, I am forced to switch to new server + python3 in the next months.

Thanks Klaus

[Ryan J Ollos]

Aiming to release in next 1-2 months. #13345 is the most important ticket for releasing.

[anonymous]

Since #13345 is resolved, are there any further blockers to get Trac 1.6 released?

Really looking forward to switching to Python 3

[anonymous]

mee too: "Really looking forward to switching to Python 3"

[anonymous]

Hi any idea when you will release 1.6.?

Python3 switch is pressing … I don't think we need all small goodies in the first version of 1.6 (even if I like TracAccountManager), but at least it would be a signal:

• for people to adapt thir addons
• that this project is still alive

[Ryan J Ollos]

We are still finding issues to resolve. If we released it tomorrow, it would be the same as the current trunk, so you should feel free to install from trunk or milestone:1.5.3. It's pretty stable by now.

If I had to guess, we'll probably release 1.6 around July 1. Testing and feedback from the current trunk are welcome.

[anonymous]

Any news about the 1.6 release?

Python 3 migration is pressing here.

Or is trac discontinued?

I would only like to know.

Thanks.

[Ryan J Ollos]

Replying to anonymous:

Python 3 migration is pressing here.

The development releases are Python 3 compatible: TracDownload#LatestDevRelease

There will be few changes before the 1.6 release, so you can be fairly confident installing 1.5.3.

Or is trac discontinued?

No, we did a release in May, TracChangeLog#a1.4.3

If you have more questions, please ask on the MailingList.

[anonymous]

Do you think you can set an realistic time schedule for this milestone, or do you guys simply have no more time to work on trac?

An little info would be helpfull so we can plan, thanks :-)

[Ryan J Ollos]

I'm unsure when we can release 1.6, since I don't have much time. However, the main things to be done are #13406 and moving the CI to GitHub, so not that much will change between the current trunk and release of 1.6.

[figaro]

We are running Trac 1.5+ for quite some time now and it is running stable, beyond the incidental Py3 repairs on custom plugins. So there is no issue running a development release, at least from a technical perspective.

The jQuery timepicker upgrade (#13406) is for us a cosmetic requirement. The jQuery UI update (#13431) and jQuery update (#12858) are far more substantial.

[anonymous]

Dear edge team - as DEBIAN 12 seems to be just around the corner, is there any plan to release a 'stable' TRAC with just the basic needed py3 support? Or you plan to keep it in work until it is cosmetically perfect?

[Ryan J Ollos]

Replying to anonymous:

Or you plan to keep it in work until it is cosmetically perfect?

It's not that, it's lack of time. The latest dev release is very stable. I will try to get the release out soon but I can't make any promises.

[anonymous]

Lets release..?

[anonymous]

+1 for release: I use 1.5.4dev just now and it works so far (for me of course)

[anonymous]

pls release soon :(

[Dirk Stöcker]

Any progress here? Trac get's more and more unusable as nearly all big Linux distributions dropped python2 already.

[pulkomandy@…]

You can use one of the already released 1.5.x versions with Python3. They don't have long term support but you can switch to 1.6.0 later when it becomes available.

[figaro]

Please note that this ticket is for collecting reviews and test results as part of the release. For questions and requests please use the MailingList.

[anonymous]

Replying to pulkomandy@…:

You can use one of the already released 1.5.x versions with Python3. They don't have long term support but you can switch to 1.6.0 later when it becomes available.

many, including myself, can not simply use what is not integral part of a stable branch. And that, I believve, is what mr. Stocker is trying to pinpoint.

[Ryan J Ollos]

I'm going to start on the release on Saturday 5/13. If I don't finish this weekend I should be done on 5/20.

[Ryan J Ollos]

Replying to Ryan J Ollos:

I'm going to start on the release on Saturday 5/13. If I don't finish this weekend I should be done on 5/20.

Failed on that attempt but feeling good about making it happen on 6/4.

[figaro]

Did a few more translations and you may have to do a pull on those.

[Jun Omae]

Committed translations from Transifex in [17709].

[Ryan J Ollos]

I'm working to get this done over the weekend. Please let me know if there are any tasks to be done beforehand such as updating translations.

[rantingman@…]

Just wanted to reply saying thank you for all your work on trac, it's a fabulous piece of software and a lot of people will be very grateful when it hits 1.6 and stuffy enterprise folks (like Debian) can upgrade from their ancient stable python2 versions.

Thank you!

[Ryan J Ollos]

Trac 1.6 has been released. 🎉

[Ryan J Ollos]

There are many minor tasks to be done such as upgrading demo sites, wiki maintenance, etc … I'll be finishing those tasks over the next week.

[oleg.vassin@…]

Replying to Ryan J Ollos:

Trac 1.6 has been released. 🎉

Thank you so much for the wonderful product!

We have been using Trac for many years as an industrial tool for project and code management.

I really hope for long-term development.

[Firenz]

Amazing work, well done! We're just due to begin migrating away from a WS2012 server with 1.0, and this couldn't have come at a better time.

[Jun Omae]

I noticed missing 1.6-stable branch on git mirror repository and mirror on github so that TracDev/AutomaticBuilds not triggered for the stable. I just configured for 1.6-stable on the mirror and manually pushed it to github.