Bug 7168 - The release change notification content should indicate the new layer branch
Summary: The release change notification content should indicate the new layer branch
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low normal
Target Milestone: 1.8 M4
Assignee: Dave Lerner
QA Contact: Alexandru Roman
URL:
Whiteboard: front-end, project configuration page
Depends on:
Blocks:
 
Reported: 2015-01-16 12:43 UTC by Belen Barros Pena
Modified: 2015-11-26 10:57 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
Change release notifications (634.50 KB, application/pdf)
2015-01-16 12:44 UTC, Belen Barros Pena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2015-01-16 12:43:26 UTC
When you change the project release and we find valid layers for the new release, we show a notification saying:

"You have changed the release to: <new_release>. This has caused the following changes in your project layers:

- <no_of_layers> changed: <layer_names>"

For example:

"You have changed the release to: Yocto Project 1.7 Dizzy. This has caused the following changes in your project layers:

- 3 layers changed: openembedded-core, meta-yocto, meta-yocto-bsp"

Although the content above is pretty good, it leaves you wondering what are the actual changes that were made to the layers. That's why the design asked for the following text:

- <no_of_layers> changed to the <branch> branch: <layer_names>

Like so:

"You have changed the release to: Yocto Project 1.7 Dizzy. This has caused the following changes in your project layers:

- 3 layers changed to the dizzy branch: openembedded-core, meta-yocto, meta-yocto-bsp"

Adding the new branch name to that notification would be pretty nice.
Comment 1 Belen Barros Pena 2015-01-16 12:44:24 UTC
Created attachment 2327 [details]
Change release notifications
Comment 2 Belen Barros Pena 2015-03-25 10:39:31 UTC
This should be 'in progress review'. Patch still not merged upstream.
Comment 3 Alexandru Roman 2015-11-26 10:57:41 UTC
Verified.