Bug 1209785

Summary: Update to 1.1.0 development snapshot
Product: [Fedora] Fedora Reporter: poma <pomidorabelisima>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 21CC: dcbw, psimerda, thaller
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-12 09:38:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 1.1.0 development snapshot none

Description poma 2015-04-08 08:25:49 UTC 
Created attachment 1012081 [details]
Update to 1.1.0 development snapshot

Also solves the bridge bug, as described here:
https://mail.gnome.org/archives/networkmanager-list/2015-April/msg00013.html
Comment 1 Thomas Haller 2015-04-08 10:33:08 UTC 
Fedora 21 is based on nm-0-9-10 release, and likewise Fedora 22 is based on nm-1-0.

Updating to a newer major release (or development snapshot) has a huge risk to break other stuff. We can only backport safe fixes to nm-0-9-10/F21.

Lets re-target this bug to a specific issue (bridge behavior with networking disabled?).

See also: https://bugzilla.gnome.org/show_bug.cgi?id=747477
Comment 2 poma 2015-04-08 14:47:33 UTC 
Why the two of you discuss something that is already done and working, as far as the bridge at least?