On Fri, Feb 14, 2014 at 5:45 AM, David Lang <[email protected]> wrote: > On Thu, 13 Feb 2014, Michael Biebl wrote: > > >> 2014-02-13 23:07 GMT+01:00 Michael Biebl <[email protected]>: >> >>> This patch is for v7-stable but should also apply to master. >>> Apply it with "git am" >>> >> >> Rainer, what's the preferred workflow nowadays: >> a/ post patches to the mailing list >> > > for patches, any way that works is good :-) slight preference to pull > requests (either internal to github, or e-mailed to the list if using a > different git server) followed by e-mail to the list > > full ack, I really don't care as long as it is a good patch :-) A pull request against a life git repo is helpful if we have merge conflicts. Git tends to be able to do more automagically in that case, at least that's my experience.
> > b/ create bugs in bugzilla.adiscon.com >> c/ file tickes in https://github.com/rsyslog/rsyslog/issues/ ? >> >> Michael >> >> P.S.: Am I the only one who finds the issue tracker in github awefully >> limited? No version tracking, no moving of bugs between different >> components and the list goes on... >> > > but reporting is probably best in bugzilla, but he is thinking of moving > to github. you are the first to raise problems with it, so that may cause a > rethink. > <http://www.rsyslog.com/professional-services/> > As David said, I am re-thinking that. The github tracker has some advantages, but one needs to get used to it. They use the new-style paradigm of "tags". So you (actually me) need to create tags for different versions and components. Once this is in place, it's easy to filter on them and shuffle bugs between different categories. If you get used to it, it's quite powerful. Working for a couple of weeks with it, it actually looks like a big plus of the github issues is that a) they get more exposure, so hopes are higher other will jump in [yet to be proven] b) it's easier for many folks to work with them as they already have a github account c) for me, it's easier as I don't need to maintain another piece of infrastructure d) [maybe just me] after getting used to the tagging paradigm, I find them easier to work with of course, there are downsides a) the interface is far from what you expect from a "real" bug tracker [as you mention] b) you never know how long github will be around c) not everyone likes to open a github account So it's pro and con, and it is good to hear counter-argument from some life person. All in all, *I* am currently in favor of the github issue tracker. More comments appreciated. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
