2:53 a.m.
On 08/09/2012 09:14 AM, Pierre-Yves Chibon wrote:
On Tue, 2012-08-07 at 15:56 +0200, Alec Leamas wrote:
[cut]
> 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.
Maybe we can remove it from the beginning of the line and just put it
capital within the sentence as well.
MUST:
[] License MUST be valid
[] Package MUST NOT contain kernel module
....
But having them at the beginning of the line seems indeed to confuse
quite some people, so +1 to change this.
I have updated the branch to fit my last
proposal in the bug #68, and
intent to merge it after the release branch is merged into devel.
> 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?
To be honest, I do wonder how many people use this. I do think most
people run f-r, edit the report and copy/paste its output to the ticket.
Agreed.
However, some people seemed unhappy to remove it without
alternatives. Se be it a separate script.
> 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.
My understanding is:
- Master -> the last release
- Devel -> all new changes (besides the one too big which have their own
branch)
- ReleaseX -> changes from devel planned for the next release (that
branch disappears when merge into devel at release)
So I think either people use the RPM from the release or they test Devel
or ReleaseX, I think we should be allowed to have a broken devel branch
once in a while.
Absolutely, agreed. The idea with this is just you should be able
to
create complete packages also from devel. It makes sense e. g. when you
want to test running the no-network limited testsuite as %check in the
specfile. Overall, if it's possible to generate RPM:s from the devel
branch It might be easier to keep the spec file in shape IMHO.
So, this is more a question of exercising the complete build procedure
than actually distributing post/pre-release packages. As Stan says,
let's asume users run either released RPM:s or directly from git. After
all, f-r is not the kind of sw which delivers nighty builds :)
--alec