Issue 127278 - Repo missing tags/AOO413
Summary: Repo missing tags/AOO413
Status: UNCONFIRMED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 4.1.3
Hardware: All All
: P5 (lowest) Major (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: https://svn.apache.org/repos/asf/open...
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-08 19:38 UTC by Mark E Ziegast
Modified: 2017-01-09 17:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Mark E Ziegast 2017-01-08 19:38:49 UTC 
branches/AOO413 matches revision on web site, so isn't major now, but there isn't an official tag of it in tags/, which could be major later. It appears someone (?arielch) goofed in making release straight out of branches, iow, when practice appears that should be tracking bug fixes and back ports from trunk to tags/ rev. as branches/AOO410 is for tags/AOO410 to AOO4121, and AOO414 should be if 414 actually released as tags/AOO414 before 420.
Comment 1 Marcus 2017-01-08 21:15:31 UTC 
For these kind of issue please use the mailing list dev@ to talk to the devbelopers. Here in the issue tracking system build system issues are nearly invisible. Thanks.
Comment 2 Mark E Ziegast 2017-01-09 07:30:15 UTC 
I'm not one of the developers, nor plan to be, so it's inappropriate for me to post on the @dev list. I was just looking at the repo and noticed the discrepancy; and took out the time to actually bring it up somewhere relevant as a one time thing. Given that, the time to close issue is after you've notified them separately and it's been fixed.
Comment 3 Keith N. McKenna 2017-01-09 17:14:55 UTC 
(In reply to Mark E Ziegast from comment #2)
> I'm not one of the developers, nor plan to be, so it's inappropriate for me
> to post on the @dev list. I was just looking at the repo and noticed the
> discrepancy; and took out the time to actually bring it up somewhere
> relevant as a one time thing. Given that, the time to close issue is after
> you've notified them separately and it's been fixed.

Mark;
 Do not let the dev@ designation deter you from using that list. It is the public mailing list for discussion of all issues of general concern to the project and not just for developers. As Marcus said the dev@ list would be the best place to raise this concern.

Regards
Keith