On Thu, 2009-10-22 at 14:18 -0700, Adam Williamson wrote:
I have two particular nits with it. One, it's pretty unwieldy,
especially for part time maintainers (thinking how many hoops we'll have
to jump through just to keep our packages up to date). Having to jump
through the Bodhi hoops every time we just want to put a trivial update
into a release that won't be coming out for five months feels like a
pain.
Who said anything about 5 months. 3 months max, which is just slightly
longer than the amount of time they spend now doing Trac tickets to get
something in.
I'd worry about a lot of stuff going stale and smelly in the
middle of the Bodhi process somewhere as maintainers lose track of where
the hell they're up to with the four releases they have to cope with
(the last two already-released releases, the upcoming release, and
"rawhide").
"rawhide" would never use bodhi. If you build in devel/ it shows up in
rawhide the next day. End of story. Bodhi would only be used for the
pending and already done releases.
Two, it makes testing things a bit more complex. Those of us who like to
test upcoming stuff in real use - i.e. on our main machines - will have
to choose whether to test "rawhide", in which case we'll have more pain
to deal with ourselves and won't be contributing as much to testing of
the next stable release, or test the next stable release, in which case
we aren't helping maintainers by making sure the stuff they're putting
in "rawhide" isn't totally broken.
For people like you, you'd just keep jumping when we branch off the next
release. Like it or not, this is happening /already/. dist-f13 already
has 953 packages with updates, and it isn't published /anywhere/
for /anybody/ to test it. We can only make that better, not worse.
But overall, the positives could certainly outweigh the negatives. Just
thought I'd flag up the two major concerns I have in case anything could
be done about them.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca:
http://identi.ca/jkeating