Open Stack

On 04/28/2014 07:56 AM, Tom Fifield wrote:
> On 28/04/14 13:52, Andreas Jaeger wrote:
>> On 04/28/2014 02:28 AM, Tom Fifield wrote:
>>> On 28/04/14 01:30, Andreas Jaeger wrote:
>>>> Anne,
>>>>
>>>> even if we do not tag openstack-manuals right now, we should tag IMHO
>>>> the other projects to mark the release of Icehouse - this means all the
>>>> API projects as well as the operations-guide.
>>>
>>> Operations guide is not tied to a particular OpenStack release, so I
>>> wouldn't bother for that one. The API site uses API versions (eg v2,
>>> v3), rather than release versions, so I question whether there's a need
>>> for this ?
>>
>> It was done with Havana, so I thought it was custom usage.
>>
>>> Is there a particular use case for repo tags for these two?
>>
>> I stumpled upon this when looking at Stackalytics where the config files
>> need some information when a release cycle starts. Adding just git ids
>> to the list works as well,
> 
> 
> OK, fair enough, I guess it doesn't break anything, and stackalytics
> (and stats in general) is a fair use-case .. the point-in-time where we
> stopped cycle X and started cycle Y :)
> 
> As long as we can avoid confusion (eg people thinking they need to
> backport for these repos), all good on my end! Sorry for getting in the
> way :)

You're not getting in the way - I was just too brief in my email ;)

I'm also fine with any other means - and if we don't want to tag, so be it,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126