This issue tracks the release note for the following Fedora Change:
https://fedoraproject.org/wiki/Changes/BodhiNonRPMArtifacts - @bowlofeggs
If you own this change, please add additional information here that we should communicate to Fedora users. Specifically, please consider:
Your notes to us do not need to be formally written. We will edit them and add details as needed. This is a way for you to ensure that we know what is critical about your change.
If you want to write this release note, then:
Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, AsciiDoc, or whatever else, just add it to this issue as a comment and let pbokoc[1] know that you're done with this one and you'd like the note included. Be sure to do this at least one day before the final release (October 29 according to the current schedule). Also make sure to do this even for relnotes that haven't been checked by the change owner.
[0] You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure. [1] In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc @redhat.com if you can't get a hold of me on IRC.
Greetings! I apologize for taking so long to reply here, I think it got lost in my task tracker somewhere.
Bodhi 3.0.0 is what delivered this feature, and the release notes for that are available here:
https://bodhi.fedoraproject.org/docs/release_notes.html
There are a couple of things that come to mind that this enables for end users:
No action is necessary for upgrading users. In fact, they've already been using Bodhi 3.0.0 this week without realizing it ☺
@bowlofeggs you expressed it in right way, so nothing to add :)
Unifies OSTree references ( @dustymabe, can you elaborate on this?)
Mainly this allows us to take advantage of new features in pungi including doing smart versioning when creating ostrees.
Metadata Update from @sclark: - Issue assigned to sclark
@bowlofeggs - I have drafted a release note in PR #60 from the information you added above and information on the change page. Please would you review the text in PR #60 and let me know if anything needs to be added or changed?
Release note text approved by change owner on PR #60. PR merged, closing this issue.
Metadata Update from @sclark: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.