Well, in practice I almost never received doc together with a code contribution. ..
Sent from phone, thus brief. Am 14.12.2013 19:21 schrieb "David Lang" <[email protected]>: > On Sat, 14 Dec 2013, Rainer Gerhards wrote: > >> I've also thought a bit more about the separate repo question. I am now >> again of the view that this is not a problem, but indeed desirable. The >> only thing we need to make sure is that it follows the same maintenance >> policies (regarding versions) that rsyslog does. And that's not very hard. >> >> Indeed, the whole doc version issue is not so much a real issue IMHO. In >> fact, we just have two of them >> >> a) the old legacy stuff used in v5 >> b) the new stuff used in v6+ >> >> That's the main source of confusion. Otherwise, rsyslog always keeps >> backward-compatibility very high on the priority list. So actually all we >> need is "this parameter/module" is available since ... and you are all >> set. >> >> Back to the repo question: I think a separate repo is of big advantage, as >> access to it, especially commit access, follows quite different paradigms >> than the main code repository. So I am back to the "let's do a separate >> one" PoV - maybe better earlier than later (so that other folks can see >> what's going on). >> >> >> David, all: anything I overlooked? >> > > My only real concern is that this means that the patch/pull request for a > feature and it's documentation now get split up and take two different > paths. > > just from a conceptual level this strikes me as very wrong. It may not end > up being that bad in practice (again because things are fairly small), but > it will make things harder for people writing new things to do the > documentation for their changes, and this is an area we are already weak in. > > David Lang > _______________________________________________ > 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. > _______________________________________________ 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.
