Open Stack

I would like to insert a clarification here regarding the difference
between "support" and "removal of content".

Essentially: the documentation team needs to be more lenient in removing
old versions than the software projects :) We don't need to update old
versions, and would respond to any queries to do so with "sorry, it's
not supported", but the stuff still needs to be online and accessible
for some time.

The reason for this is, for essentially no cost*, we have the unique
ability to make a positive impact in the approximately one-third of
users that are running an unsupported release.

Though they would no longer be able to get support upstream, have any
feature requests or bug fixes, they should be able to still use the
cloud they have to the best of their ability until such time as they can
upgrade.

On a related note, I have re-opened the bug regarding the difficulty our
readers have in terms of finding the correct version of the document for
their cloud (https://bugs.launchpad.net/openstack-manuals/+bug/1191447
), since this issue is ongoing and continues to be reported.

Your views on how we can continue to best serve our community of users
across all versions that they choose to use are appreciated!


Regards,


Tom

* Assuming the bug mentioned is fixed, the main cost is telling a small
number of people "no, we don't support that" on the bug tracker if they
lodge something. Probably not worth mentioning web hosting costs, since
they're so small regardless ;)

On 30/05/15 05:52, Lana Brindley wrote:
> Ideally, it should be two releases (say kilo and liberty), but there's
> an argument for supporting three around a release (juno, kilo, and liberty).
> 
> L
> 
> On 29 May 2015 9:31:17 pm AEST, "Ildikó Váncsa"
> <ildiko.vancsa at ericsson.com> wrote:
> 
>     Hi Lana,
> 
>     To be honest, I would rather keep the content in the Admin Guide in a less versioned way than move it to a place where it does not belong to. I have some further questions just to see the big picture.
> 
>     How many releases should these guides, like the admin guide cover? I mean is there a window for the content, like last 2-3 stable releases? Or these will be updated with the new changes only in each release?
> 
>     Thanks,
>     Ildikó
> 
>     -----Original Message-----
>     From: Lana Brindley [mailto:openstack at lanabrindley.com] 
>     Sent: May 28, 2015 03:07
>     To: Ildikó Váncsa
>     Cc: openstack-docs at lists.openstack.org
>     Subject: Re: Admin Guide versioning
> 
> Generally, it's as simple as writing "in the [release name] release ..."
> (or similar). It seems to me as though that's what the Ceilometer content is currently doing, though.
> 
> To be frank, it seems as though versioning is not an issue for the rest of the book, and I'm hesitant to change the whole book to suit ceilometer. I think we need to consider either moving this content elsewhere (that *is* versioned), or moving it into the /developer repo so that it can be updated and maintained there.
> 
> What do others think?
> 
> Lana
> 
> On 27/05/15 18:19, Ildikó Váncsa wrote:
> 
>     Hi Lana,
> 
>     I wouldn't move the content to the Config Reference just because
>     it is versioned. I think that all the architectural description
>     of Ceilometer and also the list of collected meters belong to
>     the Admin Guide as opposed to the Config Reference.
> 
>     How other components handle the situation that the Admin Guide
>     is on master, but the information that is needed is one or two
>     releases behind? I mean that in deployments usually older
>     releases are used as opposed to trunk or latest stable.
> 
>     Best Regards,
>     Ildikó
> 
>     -----Original Message-----
>     From: Lana Brindley [mailto:openstack at lanabrindley.com]
>     Sent: May 26, 2015 23:45
>     To: Ildikó Váncsa
>     Cc: openstack-docs at lists.openstack.org
>     Subject: Re: Admin Guide versioning
> 
>     On 26/05/15 20:44, Ildikó Váncsa wrote:
> 
>         Hi Lana,
> 
> 
>         As we discussed on the summit I reported a bug for the issue
>         mentioned in the subject:
>         https://bugs.launchpad.net/openstack-manuals/+bug/1458820
> 
> 
>         I think it would be better to maintain stable versions for
>         this guide too like what we have for the Config Reference or
>         the Install Guide. What is your opinion?
> 
> 
> 
>     Hi Ildikó,
> 
>     Would it better if we just moved the Ceilometer content into the
>     Config Reference instead?
> 
>     L
> 
> 
> 
> 
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> 
> 
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>