I pushed out a 0.2 release, but due to a last minute bug fix, was a few hours late (i.e. after bodhi activation). But, bolt 0.2 is necessary to implement all the functionality needed for the Thunderbolt 3 change proposal [0]. Currently 0.1 is in the repositories but 1) it lacks a lot of functionality and 2) there ware some API changes, and the gnome-shell part has already been done upstream in 3.27.92; as a result bolt 0.1 and what will be gnome-shell 3.28 are not compatible. [0] https://fedoraproject.org/wiki/Changes/ThunderboltEnablement
Proposed as a Blocker and Freeze Exception for 28-beta by Fedora user gicmo using the blocker tracking app because: I would like to request a freeze exception for bolt 0.2. I quote form the bug: I pushed out a 0.2 release, but due to a last minute bug fix, was a few hours late (i.e. after bodhi activation). But, bolt 0.2 is necessary to implement all the functionality needed for the Thunderbolt 3 change proposal [0]. Currently 0.1 is in the repositories but 1) it lacks a lot of functionality and 2) there ware some API changes, and the gnome-shell part has already been done upstream in 3.27.92; as a result bolt 0.1 and what will be gnome-shell 3.28 are not compatible.
This clearly doesn't constitute a blocker under the criteria, as it relates only to an enhancement Change, so I'm taking the liberty of un-nominating it as a blocker. It's a good FE candidate, however, I'm +1 FE.
bolt-0.2-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-9053deff2a
Discussed during the 2018-03-12 blocker review meeting: [1] The decision to classify this bug as an AcceptedFreezeException was made as, since it is an accepted change in Fedora 28, it's a good idea to have it in the Beta release for testing. This should not endanger and release-blocking path. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-03-12/f28-blocker-review.2018-03-12-16.01.txt
bolt-0.2-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.