Rainer Gerhards wrote: > confusing. In the sample, it would look like: > > 3.13.5 stable > 3.14.0-dev6 (relp) > 3.15.0-dev3 (relp/tcp)
Ok, let me take one last swipe at this, with numbering AND labels: 3.13.5 stable 3.14.6-beta 3.15.3-alpha > > Now let's assume I add a bugfix for the core engine. Would that bring us > to > > 3.13.6 stable > 3.14.0-dev7 (relp) > 3.15.0-dev4 (relp/tcp) 3.13.6 stable 3.14.7-beta 3.15.4-alpha > Once relp is stable, we have > > 3.13.6 deprecated > 3.14.0 stable relp > 3.15.0-dev4 (relp/tcp) 3.13.6 stable 3.14.8-rc 3.15.5-alpha > TLS begun: > 3.13.6 deprecated > 3.14.0 stable relp > 3.15.0-dev4 (relp/tcp) > 3.16.0-dev0 (tls) 3.13.6 deprecated 3.14.9 stable 3.15.5-beta 3.16.0-alpha > Now tcp becomes stable: > > 3.13.6 deprecated > 3.14.0 deprecated > 3.15.0 stable (relp/tcp) > 3.16.0-dev0 (tls) Well, this is kind of a big jump, but assuming it goes through all the proper alpha/beta/rc phases: 3.13.6 deprecated 3.14.9 deprecated 3.15.6 stable 3.16.1-alpha So, you increment the patchlevels, as you've been doing, but you use -alpha, -beta, -rc (with no numbers) to designate the newness/readiness of the branch. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
