Hi, Michael wrote: > 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...
Well, if you see the rsyslog product at bugzilla.adiscon.com you are right. But have you ever selected another product like liblognorm or libestr? You cannot choose the current versions to fill a bug.. However, Rainer should look into the milestone feature in Github... this will allow him to create version information and group/organize things. Regarding moving issues: Yes, if an issue was filled in the rsyslog project which is actual a bug in a component like liblognorm, it is not possible to move that issue (well, it is possible, but not that easy, search for gh-issue-importer.py). But on the other hand there was actual a reason *why* somebody filled an issue against rsyslog: The person who filled the bug experienced the issue when using rsyslog. so... 1) If liblognorm must be bumped to a new version to fix that issue, the rsyslog requirements will change so this must be documented. 2) Keeping a reference is good for others experience the same problem. 3) Keeping a history with references how an issue was found also help you sometimes when you review code/a patch. Also: If the problem would be located in a component not owned by Adiscon you would want to create a tracking issue just for that.., not? So I don't see a problem here. -Thomas _______________________________________________ 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.
