[
https://issues.apache.org/jira/browse/YETUS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved YETUS-328.
-------------------------------
Resolution: Fixed
well, in my haste I managed to tag the 0.1.0 tag rather than the commit t
pointed at, which I didn't even know was possible.
AFAICT, this still preserves the same info (I locally deleted the 0.1.0 tag and
{{git show rel/0.1.0}} showed both it and the target commit), so lesson learned
hopefully without harm.
> ensure proper 0.1.0 release tag
> -------------------------------
>
> Key: YETUS-328
> URL: https://issues.apache.org/jira/browse/YETUS-328
> Project: Yetus
> Issue Type: Task
> Components: build
> Affects Versions: 0.1.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
>
> We only have a pre-git-policy-change tag for the 0.1.0 release. Add a signed
> tag that matches it but is at "rel/0.1.0" so that it will be properly
> accounted for by infra.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
