Anonymous | Login | 2024-12-12 15:10 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0001402 | [Aardvark Bugs] Aardvark Mk IV | Editorial | Enhancement Request | 2020-09-20 01:42 | 2021-02-08 16:27 | ||
Reporter | andras_farkas | View Status | public | ||||
Assigned To | |||||||
Priority | normal | Resolution | Accepted As Marked | ||||
Status | Applied | ||||||
Name | Andras Farkas | ||||||
Organization | |||||||
User Reference | |||||||
Summary | 0001402: No 2018 project for bugs, on Aardvark here | ||||||
Description |
Hi! I've been meaning to mark a new bug. However, when selecting a project here on this website, I can select 2008, 2013, and 2016, but not 2017! (2018?) This means I can't quite select the most accurate descriptor for what a bug applies to. My apologies if the project selected (Aardvark Bugs) is incorrect. By the way, the category selections (for aardvark bugs) doesn't contain an Aardvark Mark IV category, only III, and earlier. |
||||||
Desired Action | Add project for 2018 version of standard into the bug tracker. | ||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Notes | |
(0004999) geoffclare (manager) 2020-09-21 08:28 |
The 2016 and 2018 editions are both "Issue7+TC2"; they have identical page and line numbers. (The only difference after the frontmatter is that they refer to themselves as POSIX.1-2008 and POSIX.1-2017, respectively). I have renamed the project so it has "2016/18" instead of "2016" in the name. The addition of an Aardvark Mark IV category still needs to be done. |
(0005042) geoffclare (manager) 2020-10-09 11:21 |
Changing category to (newly created) Aardvark Mk IV. |
(0005043) msbrown (manager) 2020-10-09 21:00 |
I can make a new Project if needed, please advise. |
(0005044) shware_systems (reporter) 2020-10-09 21:43 |
For the odd instance where a report may be filed about the frontmatter, procedurally I think it is better to have separate tags for the editions to handle the different roman numeral page numbers also. Where a tag is relevant to a specific OpenGroup pdf file name for page and line numbers, such as C181 for 2018 edition, that could be incorporated in the name too. |
(0005046) geoffclare (manager) 2020-10-12 08:09 edited on: 2020-10-12 08:13 |
Re: Note: 0005043 Please don't add a new project. As I said in my first bug note, the 2016 and 2018 editions are both "Issue7+TC2", so having separate projects for them makes no sense. The change I made to the project name is sufficient to solve the problem. Re: Note: 0005044 Frontmatter bugs are very rare (8 out of over 1400, but none so far against Issue7+TC2), and in any case the frontmatter doesn't have line numbers so submitters have to be more descriptive of where the problem text is. We often have bugs submitted with no page and line numbers and we handle those by setting the fields later. If anyone submits an Issue7+TC2 frontmatter bug, we can easily set the page number to, e.g. "xlv (2016), xl (2018)" if we feel the need. |
(0005230) geoffclare (manager) 2021-02-08 16:27 |
Fixes applied as per Note: 0004999 |
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |