Edgewall Software

Changes between Version 1 and Version 2 of Ticket #12120, comment 68


Ignore:
Timestamp:
Nov 21, 2016, 10:47:48 PM (4 years ago)
Author:
Ryan J Ollos

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12120, comment 68

    v1 v2  
    55> That looks good, I was considering making that change as well.
    66>
    7 > Some `changelog` entries on the //Release Notes// page are empty because the ticket was a task, or contained only //API Changes//. I was thinking we should filter those out. By experimenting I found that adding `changelog!=` to the ticket query filters out empty entries. Does that make sense, or am I exploiting some undefined or buggy behavior?
     7> Some `changelog` entries on the //Release Notes// page are empty because the ticket was a task, or contained only //API Changes//. I was thinking we should filter those out. By experimenting I found that adding `changelog~=` to the ticket query filters out empty entries. Does that make sense, or am I exploiting some undefined or buggy behavior?
    88
    9 After looking at the `TicketQuery` in [wiki:TracDev/ApiChanges/1.1] (which contains parameter `apichanges!=`), and looking more closely at the `TicketQuery` in [wiki:TracDev/ReleaseNotes/1.2], I see why `changelog~=` was not working. There's a parameter `changelog!=API only|-`. So we should put `-` or `API only` in the //Release Notes// field for the case of API only changes?
     9After looking at the `TicketQuery` in [wiki:TracDev/ApiChanges/1.1] (which contains parameter `apichanges!=`), and looking more closely at the `TicketQuery` in [wiki:TracDev/ReleaseNotes/1.2], I see why `changelog!=` was not working. There's a parameter `changelog!=API only|-`. So we should put `-` or `API only` in the //Release Notes// field for the case of API only changes?