Release Trac 1.0.17

[Ryan J Ollos]

This ticket is used to coordinate the finalization and testing of the next stable version of Trac, 1.0.17.

[Christian Boos]

Hello Ryan, just noticed today that the announcement mail for 1.0.15 said:

Trac 1.0.15 Released
====================

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

current stable branch is also what pretends to be 1.2.2 ;-)

So we may want to use previous stable branch or older stable branch here for 1.0.16, with perhaps a note mentioning that 1.2.x is the current stable.

[Ryan J Ollos]

Thanks, I'll make the adjustment for 1.0.16.

[Ryan J Ollos]

DONE Address comment:22:ticket:12578 before release.

[Ryan J Ollos]

​Babel 2.5.0 released on the 18th, so we'll want to keep an eye on compatibility issue. All tests passing for me on OSX with Babel 2.5.0.

[Ryan J Ollos]

Travis build auto-cancel by default now, see ​blog post. I disabled it, since we generally have a low commit rate.

Auto Cancellation allows you to only run builds for the latest commits in the queue. This setting can be applied to builds for Branch builds and Pull Request builds separately. Builds will only be canceled if they are waiting to run, allowing for any running jobs to finish.

[Ryan J Ollos]

Milestone renamed

[Ryan J Ollos]

Renamed 1.0.16 to 1.0.17 in r16356 (comment:20:ticket:12833). Noted in 1.0/TracChangeLog@6.

[Ryan J Ollos]

Travis CI sends build notifications to trac-builds@ for forks. ​Issue 6100 has a workaround of encrypting the email, which I may try. The email only gets decrypted when committing to the repository used in the encrypt command.

[Jun Omae]

Replying to Ryan J Ollos:

Travis CI sends build notifications to trac-builds@ for forks. ​Issue 6100 has a workaround of encrypting the email, which I may try. The email only gets decrypted when committing to the repository used in the encrypt command.

Interested.

Related issue, ​Move notification settings to the website · Issue #1094 · travis-ci/travis-ci, is not resolved yet.

[Ryan J Ollos]

Following my notes from comment:3:ticket:12833, I think the following is all that's needed:

$ travis encrypt "trac-builds@googlegroups.com" -r edgewall/trac

.travis.yml

@@ -98 +98 @@
 notifications:
   email:
     recipients:
-      - trac-builds@googlegroups.com
+      secure: lIn4a3G6ww61t3o12DS4aWwEwD6Hl2kxcsZgkxvhU2MgzviJ5j3EBV5F/BlbQmR1BqM51qgDOXoQTO+y9cvzAYBkIy/gfLqZjAl0hfZep6iGZgl1cnUW4c5i9+wkF8PzTaQm+q9gwlIQ7JVedWw9jzHBIn80tCgTcavahAzyelk=
 jobs:
   include:
     - os: linux

[Ryan J Ollos]

In order to first reproduce the behavior described in comment:8, I submitted a failing build in ​#198, but no notification was sent to the ​forum. I also tried restarting and canceling the building. Has the behavior changed and build notifications no longer sent for forks?

[Ryan J Ollos]

Notifications from yesterday received after several hour delay (list moderation?), but now received immediately after a build failure.

[Ryan J Ollos]

comment:10 change committed to 1.0-stable in r16430. Merged in r16434:r16435.

[Ryan J Ollos]

Documentation updated to address ​SO:49120675: r16440, r16441, r16442.