[openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

Doug Hellmann doug at doughellmann.com
Sat Apr 2 20:08:32 UTC 2016


> On Apr 2, 2016, at 1:20 PM, Steven Dake (stdake) <stdake at cisco.com> wrote:
> 
> A big correction to this thread below.
> 
> On 4/2/16, 10:05 AM, "Steven Dake (stdake)" <stdake at cisco.com> wrote:
> 
>> 
>> 
>> On 4/2/16, 10:01 AM, "Jeremy Stanley" <fungi at yuggoth.org> wrote:
>> 
>>> On 2016-04-02 16:13:28 +0000 (+0000), Steven Dake (stdake) wrote:
>>> [...]
>>>> I feel as though we are not permitted to participate in the
>>>> marketing that takes place on the releases website
>>> [...]
>>> 
>>> I'll refrain from commenting on the rest since I'm not a member of
>>> the release team, but I *seriously* hope we've not created a
>>> "marketing" portal simply by way of tracking version numbers,
>>> changelogs and release schedules. I have a feeling few (if any) of
>>> the release team wants to get into the marketing business and I'm
>>> happy to help do whatever is in my power to neuter the "marketing
>>> potential" for releases.openstack.org so it can be viewed simply as
>>> a source of _objective_ technical data.
>>> --
>> 
>> It is objective technical data, but atm we are excluded, and people look
>> at that objective technical data (like marketing and sales folks) to make
>> decisions, so it is by its very nature a marketing resource as well.  If
>> we are excluded, sales and marketing folks that make decisions about
>> OpenStack deployments may come along and say "not on the website, not
>> legitimate".
> 
> release:independent projects are rendered on this website [1], and ttx's
> review comment was more to put kolla in releases:independent of the
> releases repo rather then the mitaka location [1].  I misunderstood ttx's
> comments to mean we were completely excluded which is not the case.

Right, we just need it filed under the right directory.

> 
> That said, release:cycle-with-milestones is still what we want :)

The model change can be approved and applied to Newton. During Newton we’ll figure out how to communicate about projects that have changed their tags — we don’t want to rewrite history for old releases but we don’t want it to be hard for users to find full project history. I have some ideas to handle it but I’m waiting until after the summit to implement them.

Doug

> 
> I'd ask people cut me a little slack on this, I am new to the
> openstack/releases repository ;)
> 
> [1] http://releases.openstack.org/independent.html
> [2] https://review.openstack.org/#/c/297976/
>> 
>> Regards
>> -steve
>> 
>>> 
>>> Jeremy Stanley
>>> 
>>> _________________________________________________________________________
>>> _
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: 
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




More information about the OpenStack-dev mailing list