Bug 1042121

Summary:	[RFE][oslo]: i18n Message improvements
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	distribution	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Ami Jeain <ajeain>
Severity:	high	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	ddomingo, markmc, sgordon, slong, yeylon
Target Milestone:	Upstream M2	Keywords:	CodeChange, FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/oslo/+spec/i18n-messages
Whiteboard:	upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_discussion
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	This release also features upstream improvements to the implementation of i18n Message. These changes apply codebase improvements that streamline translation-related tasks and Message object processing, among other things.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-08 15:12:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1041839, 1045973, 1046767, 1046773, 1046776, 1046784, 1046797, 1046801

Description RHOS Integration 2013-12-12 21:05:40 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/i18n-messages.

Description:

During the Oslo meeting on 2013-10-11 (http://eavesdrop.openstack.org/meetings/oslo/2013/) we discussed the integration of Messages into OpenStack vs other approaches, and also came up with some ideas for improving the current implementation.


Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:50:54 UTC

Moving to POST based on upstream status (Implemented).

Comment 4 Ami Jeain 2014-06-12 14:16:54 UTC

sanity only test as it is mainly code change

Comment 6 errata-xmlrpc 2014-07-08 15:12:33 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0845.html