# Fedora Quality Assurance Meeting
# Date: 2017-02-27
# Time: 16:00 UTC
# Location: #fedora-meeting on irc.freenode.net
I don't have a huge amount of specific topics for a meeting, but it's
been a couple of weeks and we are getting closer to Fedora 26 Alpha:
the Fedora 26 branching is scheduled to happen on Tuesday. There are
also some interesting proposed Changes for Fedora 27 we could look at.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 26 status
3. Fedora 27 Changes: No More Alphas
4. Fedora 27 Changes: Bodhi Non-RPM Artifacts
5. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org
I am asking if anyone knows anything about the whereabouts of Fedora developer Kalpa Welivitigoda? He is the maintainer of unetbootin package. Bug 1229874 would need fixing, but it seems that he is not responding to the bug comments anymore. I tried to ask him about that matter via Facebook as well last Tuesday, but he doesn't seem to respond there either.
– Iiro Laiho
major versions of canl-c and gridsite packages will be updated in
rawhide. Dependent packages should rebuild.
canl-c and gridsite has been FTBFS because of openssl, they will use
openssl 1.1 now.
Gridsite with openssl 1.1 is not well tested yet and it will go from
development snaphost, but using new openssl is needed because of
depency of gridsite on httpd/mod_ssl. There are no known issues for
= Proposed Self Contained Change: Bodhi Non-RPM Artifacts =
* Randy Barlow <bowlofeggs AT fedoraproject DOT org>
Bodhi, the Fedora Updates System, should be able to process more than just RPMs.
== Detailed Description ==
As Fedora starts to deliver more than just RPMs and ISOs, we need a
way to handle delivering updates to these artifacts. Bodhi currently
handles this workflow for RPMs only, but we want to start using it for
other content, such as Docker containers, Flatpak apps, OSTrees, etc.
If it can be tagged in Koji, it should be accepted by Bodhi.
== Scope ==
* Proposal owners:
- Database model changes
- Masher modifications to the push process
- Web UI changes
- CLI modifications
- Unit tests
- Upstream tracker issue: https://github.com/fedora-infra/bodhi/issues/653
* Other developers:
- QA: Taskotron will need handle kicking off tests for non-RPM updates
- QA: Client-side updates-testing tools like fedora-easy-karma could
optionally be updated to detect these new artifacts
* Release engineering:
- We will need to ensure that the current signing process will work
with non-RPM content
- Ensure that the new content has a proper home in the directory structure.
- Releng ticket: #6660
- List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines:
N/A (not a System Wide Change)
* Trademark approval:
N/A (not needed for this Change)
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic