Opened 8 years ago

Closed 8 years ago

#2126 closed task (complete)

rename b10-showtech to isc-sysinfo

Reported by: jreed Owned by: jelte
Priority: medium Milestone: Sprint-20120807
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 2 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by shane)

Per our phone call meeting on 2012-07-12, rename the b10-showtech to isc-showinfo.

Subtickets

Change History (12)

comment:1 Changed 8 years ago by jinmei

  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:2 Changed 8 years ago by shane

  • Description modified (diff)
  • Summary changed from rename b10-showtech to b10-sysinfo to rename b10-showtech to isc-sysinfo

Actually this should be isc-sysinfo, not b10-sysinfo. Renaming!

comment:3 Changed 8 years ago by jelte

  • Milestone changed from Next-Sprint-Proposed to Sprint-20120807

comment:4 Changed 8 years ago by jelte

  • Owner set to jelte
  • Status changed from new to assigned

comment:5 follow-up: Changed 8 years ago by jelte

  • Owner changed from jelte to UnAssigned
  • Status changed from assigned to reviewing

ready for review. Since I regenerated the manpages, a number of unrelated manpage files got a light tweak as well.

comment:6 Changed 8 years ago by jelte

oh, btw, proposed changelog:
[func] or build perhaps?
b10-showtech is now called isc-sysinfo

comment:7 in reply to: ↑ 5 Changed 8 years ago by jinmei

Replying to jelte:

ready for review. Since I regenerated the manpages, a number of unrelated manpage files got a light tweak as well.

The change looks okay in that it does what the ticket is intended to
do (I assumed you didn't touch the content of the implementation; just
renaming and replacing the tool names in the code).

I'm not sure why we name it isc-XXX though (and I don't remember the
discussion). If it's because this tool is not specific to BIND 10, I
tend to agree, but then shouldn't we rather develop and distribute
independently from BIND 10?

Regarding the generated man page, I'd rather prefer not including the
auto-generated files in the branch (and in the merge commit), but I'd
leave it to you.

Finally, regarding the changelog: I'm not sure if we need a dedicated
changelog for this branch because we've never included the previous
showtech in releases. Maybe just rename it in entry 452 (and if we
want, leave some additional notes about the remaining)?

Anyway, all of these are minor or not directly relevant. Please do or
don't whatever you want about these and merge.

comment:8 Changed 8 years ago by jinmei

  • Owner changed from UnAssigned to jelte

comment:9 follow-up: Changed 8 years ago by jelte

Good point about the changelog, i'll just rename it in the existing entry.

Regarding the other two points

  • AFAIK, it was changed from b10- to isc- because the intent was to make this something not just for bind 10, but perhaps Shane has some more info
  • And as to the manpages, I kind of agree, but the *reason* the manpages are currently in the repository is that they need yet another build dependency to generate, and they are generated automatically on normal make if --enable-man was set. I have no problems with removing them normally, but I'm not gonna touch that in this branch :)

comment:10 Changed 8 years ago by shane

The reason this was changed from b10- to isc- is that we want to have a single tool to be used for all ISC software, rather than force administrators to learn new ones for each product. I don't know if we'll reuse the actual tool or what, but at least it won't require BIND 10 administrators to learn something new. :)

comment:11 in reply to: ↑ 9 Changed 8 years ago by jreed

Replying to jelte:

  • And as to the manpages, I kind of agree, but the *reason* the manpages are currently in the repository is that they need yet another build dependency to generate, and they are generated automatically on normal make if --enable-man was set. I have no problems with removing them normally, but I'm not gonna touch that in this branch :)

The removal of the generated docs is handled in ticket #1687

comment:12 Changed 8 years ago by jelte

  • Resolution set to complete
  • Status changed from reviewing to closed

Merged, closing ticket.

(note that, as suggested, I have updated an existing changelog entry, so this ticket does not get one)

Note: See TracTickets for help on using tickets.