Opened 8 years ago
Closed 6 years ago
#12839 closed task (fixed)
Release Trac 1.0.17
Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.17 |
Component: | general | Version: | |
Severity: | normal | Keywords: | release |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
This ticket is used to coordinate the finalization and testing of the next stable version of Trac, 1.0.17.
Attachments (0)
Change History (17)
comment:1 by , 7 years ago
comment:4 by , 7 years ago
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.
comment:5 by , 7 years ago
Travis builds 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.
comment:7 by , 7 years ago
Summary: | Release Trac 1.0.16 → Release Trac 1.0.17 |
---|
Renamed 1.0.16 to 1.0.17 in r16356 (comment:20:ticket:12833). Noted in 1.0/TracChangeLog@6.
follow-up: 9 comment:8 by , 7 years ago
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.
comment:9 by , 7 years ago
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.
comment:10 by , 7 years ago
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
diff --git a/.travis.yml b/.travis.yml index 5a70fbb5d..1b5c5ce52 100644
a b script: 98 98 notifications: 99 99 email: 100 100 recipients: 101 - trac-builds@googlegroups.com101 secure: lIn4a3G6ww61t3o12DS4aWwEwD6Hl2kxcsZgkxvhU2MgzviJ5j3EBV5F/BlbQmR1BqM51qgDOXoQTO+y9cvzAYBkIy/gfLqZjAl0hfZep6iGZgl1cnUW4c5i9+wkF8PzTaQm+q9gwlIQ7JVedWw9jzHBIn80tCgTcavahAzyelk= 102 102 jobs: 103 103 include: 104 104 - os: linux
comment:11 by , 7 years ago
comment:12 by , 7 years ago
Notifications from yesterday received after several hour delay (list moderation?), but now received immediately after a build failure.
comment:13 by , 7 years ago
comment:10 change committed to 1.0-stable in r16430. Merged in r16434:r16435.
comment:14 by , 7 years ago
Description: | modified (diff) |
---|
comment:16 by , 6 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:17 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Hello Ryan, just noticed today that the announcement mail for 1.0.15 said:
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.