ApiChanges and ReleaseNotes
18 views
Skip to first unread message
RjOllos
Apr 22, 2020, 1:18:45 AM4/22/20
to Trac Development
I'm reviewing the ApiChanges (1) and ReleaseNotes (2) for release 1.4 and thinking about the next release.
I like the workflow we have where API Changes and the Release Notes are created as each ticket is closed. It makes the release process much faster.
There are some changes though that don't seem to fit either API Changes or Release Notes. Examples:
It is nice to have a summary of the changes in the ticket, but we want API Changes and Release Notes to be concise and only have things relevant to developers or users/admins, respectively. The above examples don't seem to fit either category. Maybe we could add another field, such as "Internal Changes"?
- Ryan
RjOllos
Apr 25, 2020, 1:34:29 PM4/25/20
to Trac Development
On Tuesday, April 21, 2020 at 10:18:45 PM UTC-7, RjOllos wrote:
It is nice to have a summary of the changes in the ticket, but we want API Changes and Release Notes to be concise and only have things relevant to developers or users/admins, respectively. The above examples don't seem to fit either category. Maybe we could add another field, such as "Internal Changes"?
Added "Internal Changes". I'm reviewing and updating ReleaseNotes and ApiChanges tickets for 1.4 release.
- Ryan
RjOllos
Apr 25, 2020, 4:16:53 PM4/25/20
to Trac Development
Release Notes for 1.4 have been organized. There were many tickets that fixed regressions introduced in 1.3.x. Those are now "Internal Changes".
I hope the presentation is now better for users and admins. Please comment here if anything looks incorrect or could be improved.
- Ryan
Reply all
Reply to author
Forward
0 new messages