<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 28, 2014 at 12:58 AM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 04/28/2014 07:56 AM, Tom Fifield wrote:<br>
> On 28/04/14 13:52, Andreas Jaeger wrote:<br>
>> On 04/28/2014 02:28 AM, Tom Fifield wrote:<br>
>>> On 28/04/14 01:30, Andreas Jaeger wrote:<br>
>>>> Anne,<br>
>>>><br>
>>>> even if we do not tag openstack-manuals right now, we should tag IMHO<br>
>>>> the other projects to mark the release of Icehouse - this means all the<br>
>>>> API projects as well as the operations-guide.<br>
>>><br>
>>> Operations guide is not tied to a particular OpenStack release, so I<br>
>>> wouldn't bother for that one. The API site uses API versions (eg v2,<br>
>>> v3), rather than release versions, so I question whether there's a need<br>
>>> for this ?<br>
>><br>
>> It was done with Havana, so I thought it was custom usage.<br>
>><br>
>>> Is there a particular use case for repo tags for these two?<br>
>><br>
>> I stumpled upon this when looking at Stackalytics where the config files<br>
>> need some information when a release cycle starts. Adding just git ids<br>
>> to the list works as well,<br>
><br>
><br>
> OK, fair enough, I guess it doesn't break anything, and stackalytics<br>
> (and stats in general) is a fair use-case .. the point-in-time where we<br>
> stopped cycle X and started cycle Y :)<br>
><br>
> As long as we can avoid confusion (eg people thinking they need to<br>
> backport for these repos), all good on my end! Sorry for getting in the<br>
> way :)<br>
<br></div></blockquote><div><br></div><div>I think the original reason for branching still holds true -- to make releases from released documentation that we can then replicate. It does mean backporting so the less we do of that, the better!</div>
<div><br></div><div>The reasons for tagging sound like:</div><div>- stats tracking </div><div>- change management (Knowing when a big change happened to a repo may be important. In the case of the ops guide, we tagged because we wanted to know when O'Reilly edits were happening and be able to re-create the original version for reference.)</div>
<div><br></div><div>My concern with the overhead of tagging at each release is related to the reasons. </div><div>-Stats aren't the best method to measure doc contributions for accuracy and completeness or coverage. In the past we just used a known SHA for stats collection, has that changed?</div>
<div>- We want to get rid of the <project>-api repos anyway for all the overhead in maintenance they cause, so adding tags now seems against that goal of decreasing work done to those repos.</div><div><br></div><div>
I'd rather not add another task to releases. The projects get to rely on their release manager for the tagging-related tasks -- the Docs PTL won't have that luxury. That said, for change management, I think it's fair to ask for tagging. So it might make sense to tag operations-guide and openstack-manuals, but I'm not sure we need it for other docs repos, especially API docs.<br>
</div><div><br></div><div>I think that's all my concerns. So my counter proposal would be to tag:</div><div>openstack-manuals</div><div>operations-guide (and even this is iffy since there won't be a reason to recreate an original version for a while?)</div>
<div><br></div><div>But not the API repos. </div><div><br></div><div>Thoughts?</div><div>Anne</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
</div>You're not getting in the way - I was just too brief in my email ;)<br>
<br>
I'm also fine with any other means - and if we don't want to tag, so be it,<br>
<div><br>
Andreas<br>
--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
<br>
</div><div><div>_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div><br></div></div>