Quoting Alec Leamas (2012-08-07 15:56:58)
Back from holidays, I have five feature branches. This is somewhat
insane, and I need to come to conclusions to trash, merge or update
these. Here we go:
koji: Use koji scratch builds. This is just a manpage update, and a
separate script to download koji scratch builds. I could commit this
myself, but since the corresponding issue #17 is assigned to sochotni I
hesitate for that very reason. As long as noone says otherwise, I intend
to commit this one.
Feel free to commit that one. I assigned it to myself long time ago when
pingou and we were the only active devs. Automating work with koji
scratch-builds would nice(r), but also harder with regards to various
tests. Feel free to push this to release-0.2.1, since the changes are
more-less trivial
no-must: Remove most MUST/SHOULD from output. This is dicussed in
the
related bug #68. We need to finish this discussion, preferably in the
bug. In particular, I need sochotni to reply to my last attempt to find
common ground.
Commented in trac
rm-bugz: This was discussed in the list, see e. g.
https://lists.fedorahosted.org/pipermail/fedorareview/2012-July/000006.html.
My conclusion is that removing the bugzilla options is acceptable if
(and only if) a separate tool is provided with these options. Unless
there are other opinions, I might merge such a solution. I said 'might',
didn't I?
Indeed, if we have a separate tool to do this easily...I am all for
removing this from f-r (we can still package it similar as
fedora-create-review)
vers-info: Keep devel branch ready to produce post-release rpm:s
(which
means some fixes in release branches). I think sochotni and I agreed on
this, but it's long time since. Once again, as long as there is no other
opinions, I plan to merge this.
Actually I don't like this very much. I'd rather people use either git
version directly (try-fedora-review exists exactly for that) or really
run released versions. I'll give this another look though so don't throw
the branch away just yet :-)
So, you have been warned. I guess this is the only way to get
attention
WARNING! WARNING! would work as well :-)
--
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Software Engineer - Base Operating Systems Brno
PGP: 7B087241
Red Hat Inc.
http://cz.redhat.com