This issue tracks the release note for the following Fedora Change:
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 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.
 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.
 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.
Metadata Update from @roypen:
- Issue assigned to roypen
I don't know in which section these release notes should be placed. Desktop? Perhaps there is no need to create them if DE is not installed by default in the system. Also, there is already LXQt Fedora Spin that should cover it. Am I right?
@roypen Sorry, didn't see this before. Yeah, let's put this in Desktop, that should be fine. It doesn't matter that it's not installed by default, we cover plenty of stuff that isn't. No need to make a new page for spins.
Hey @pbokoc , no problem, I should tag you. Fedora release day is tomorrow. The release notes for LXQt are not long, but I don't think I will manage to do it today. Is it going to be ok if I make a PR tomorrow?
Fixed in PR #599
Metadata Update from @pbokoc:
- Issue status updated to: Closed (was: Open)
to comment on this ticket.