by Luke Macken
The bodhi-client package should be making its way to an updates-testing
repository near you! (and a newer version is already queued up for tomorrow).
Not only does this command-line tool give you easier access to bodhi, but also
provides some new features to help people get more involved with testing
updates and providing useful feedback.
I wrote up some documentation on various usage examples of the tool, which can
be found on the wiki. I also submitted a Makefile.common patch that,
once applied, will allow you to run `make update` from your package branch.
This will drop you into a new update template, and will then submit your update
straight to bodhi.
Some noteworthy features in the bodhi-client, aside from the normal bodhi
• Ability to view all updates-testing packages that you currently have
installed on your local machine, that you *could* be testing and providing
useful feedback for:
∘ bodhi --testable
• Ability to view your update candidates (this is a fairly expensive
operation -- please use sparingly):
∘ bodhi --candidates
I also upgraded our production bodhi instance today, which pulled in a ton of
bugfixes and some new features, such as:
• Updates by default will now get submitted to into testing. This can easily
be modified when using the web form, the bodhi client, and `make update`.
• Thanks to the new security bug tracking policy, we're now tracking CVEs
using Bugzilla, thus bodhi no longer will ask you for CVE IDs. The less
information that the developer has to type, the better. Read the policy
for more details. Bodhi is not yet 100% compliant to the proposed changes,
as it does not know about parent/tracking bugs, but should be soon.
• If you try and submit an update that is older than something already
pending/testing, you will be prompted with a dialog that will give you the
ability to instantly obsolete those updates.
As always, patches/questions/criticisms/comments are welcome. You can file
tickets in the usual place.
15 years, 4 months
After Fedora 8 comes Fedora 9!
by Jesse Keating
The development cycle of Fedora 9 will begin in earnest tomorrow. This
will mark the first attempt at composing Rawhide with package builds
that target Fedora 9. There is quite a number of them built up
already, over 800. This will be a bumpy ride at first as we start to
see where all these builds gets us. In the next couple of weeks we the
project will work on setting a schedule for Fedora 9, start reviewing
proposed Features, and come up with an overall idea of what we'd like
to accomplish this time around.
For those of you that were early adopters of Fedora 8 and joined the
Rawhide bandwagon, but want to get off at the Fedora 8 stop, I suggest
that you ensure your 'development' yum repo is disabled. For those of
you that wish to continue to enjoy Rawhide, I suggest you ensure that
your 'fedora', and any updates repos are disabled, and make sure that
your development repo remains enabled.
During the development of Fedora 8 we experimented with a few things to
help users and developers of Fedora have a smooth ride through the
development cycle. Those experiments have worked out pretty well and
have been incorporated into the overall development strategy, as
http://fedoraproject.org/wiki/ReleaseEngineering/Overview As we look forward to Fedora 9 we hope to make the experience even more enjoyable and at the same time even more beneficial to all involved. I welcome suggestions and discussion on how to improve things, which is always a constant goal of mine.
So lets all sit back, relax, and enjoy a day of rest for Fedora 8.
Tomorrow it starts up all over again!
Fedora -- All my bits are free, are yours?
15 years, 4 months