Bug 1298566 - [Docs] [Release Notes] - add list of gem changes to release notes for 5.5.2
Summary: [Docs] [Release Notes] - add list of gem changes to release notes for 5.5.2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.5.2
Assignee: Dayle Parker
QA Contact: Shikha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-14 12:55 UTC by Marianne Feifer
Modified: 2016-04-28 00:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Gem changes, see comments.
Clone Of:
Environment:
Last Closed: 2016-02-11 00:27:25 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Marianne Feifer 2016-01-14 12:55:16 UTC
Description of problem: Need list of gem changes for 5.5.2


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Get list of gems from /var/www/miq/vmdb/log/gem_list.txt from a 5.5.0 appliance.
2.Get list of gems from /var/www/miq/vmdb/log/gem_list.txt from a 5.5.2 appliance.
3. List changes in release notes for 5.5.2 and update KB article.

Actual results:


Expected results:


Additional info: 5.5.1 was a text only errata - no gem changes.


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 2 Marianne Feifer 2016-01-14 17:05:46 UTC
Added:

concurrent-ruby (1.0.0)

Version changes:

amq-protocol (2.0.1)
autoprefixer-rails (6.2.1)
bundler (1.11.2)
css_splitter (0.4.3)
dalli (2.7.5)
fog-sakuracloud (1.7.3)
gettext_i18n_rails (1.3.2)
iniparse (1.4.2)
linux_admin (0.13.0)
rails-assets-bootstrap-select (1.7.7)
rdoc (4.2.1)
redhat_access_cfme (0.0.7)
responders (2.1.1)
sass (3.4.20)
secure_headers (2.4.4)
sprockets (3.5.2)

Comment 3 Andrew Dahms 2016-01-14 23:27:34 UTC
Assigning to Dayle for review.

Dayle - updating the list of Ruby Gems is a key task we perform with each release.

For this one, we will need to do the following -

1. Update the Release Notes with two tables to represent the changes above.

2. Add two new KBase articles to the KBase article on Gems mentioned in the 
   Release Notes:

   * 5.5.0
   * 5.5.2

Comment 4 Dayle Parker 2016-01-21 09:00:06 UTC
Changes made:

Release Notes 

* Are updated with the changes for 5.5.2.
* Did a restructure of the chapter "10. Changes in the Core Set of Ruby Gems" so that each release is in its own subsection (feedback welcome)

Kbase

* created two new KBase articles, linked from https://access.redhat.com/articles/1534753:
Gems included in CFME 5.5.0/CF 4.0 - https://access.redhat.com/articles/2130821

This one (for 5.5.2) is on hold until I can figure out when the css_splitter became a new package:
https://access.redhat.com/articles/2133471

Notes - according to Comment 2 it's updated, but there is no record of it in any of the previous releases' "gem_list.txt"

To do:
Find out when css_splitter was new to CFME by checking earlier versions. Add css_splitter to the Ruby gems lists in older release note lists.

Comment 5 Dayle Parker 2016-01-21 09:05:27 UTC
> Notes - according to Comment 2 it's updated, but there is no record of it in
> any of the previous releases' "gem_list.txt"
> 

To clarify - there's no record of it in our previous Kbase articles, but it can be investigated through the gem_list.txt files.

> To do:
> Find out when css_splitter was new to CFME by checking earlier versions. Add
> css_splitter to the Ruby gems lists in older release note lists.

Comment 6 Dayle Parker 2016-01-22 01:18:05 UTC
Note:

After installing CFME appliances of different versions, it seems the css_splitter gem was not in the 5.4.x releases. I've added it to the "new gems" list for 5.5.0 in the release notes, and in the related Kbase articles. css_splitter is now in the 'updated' gems list for 5.5.2 (however, I found version 0.4.4 when testing, so I've documented that.)

Comment 9 Andrew Dahms 2016-02-11 00:27:25 UTC
This content is now live on the Customer Portal.

Closing.


Note You need to log in before you can comment on or make changes to this bug.