Feature Branches or How To Come to a Conclusion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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.

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?

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.

So, you have been warned. I guess this is the only way to get attention :)

--alec



--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux