On 25 January 2018 at 08:26, Vít Ondruch <vondruch@xxxxxxxxxx> wrote: > Just to illustrate what this is about, these are 3 PR trying to fix the > branches for next RHEL: > > https://src.fedoraproject.org/rpms/rubygem-ruby-rc4/pull-request/1 > https://src.fedoraproject.org/rpms/rubygem-Ascii85/pull-request/1 > https://src.fedoraproject.org/rpms/rubygem-nokogiri/pull-request/1 > > Non of them is correct, because they are not maintained. If there were no > branches, it would be much better. So as you said, main problem here is related to the fact that something is not maintained. With or without branches first you need to solve that issue :) How branches may help solve such problem? In unexpected way .. if on the master and other branches will be clean version of the spec, with standardized format/indentation it will be way easier to allocate time someone who is not assigned to exact packages but for example to whole group of ruby packages to have look on your pull requests -> decide is this something which can be committed or not and eventually send build(s) request(s). Current Fedora model of the git permissions is well prepared to switch to branches model because on top of the assignment some people to single packages there are some number of proven packagers. Giving those people better platform of the specs in clean and standard looking form lowers effort on trying understand about what is proposed change. There is really big number of packages in case which strict assignment of the packages does not make any sense because those packages are very simple or they are very slowly changing. You can find such packages even in core part of the distribution. kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
