Hi all, I'd like to label the next release as 1.0. Logback is now a mature product and I can't think of a good reason not to go 1.0. Your comments are welcome, -- Ceki
Am 17.10.2011 21:47, schrieb ceki:
I'd like to label the next release as 1.0. Logback is now a mature product and I can't think of a good reason not to go 1.0.
+1.
Your comments are welcome,
Does it mean the API will be stable? -Gunnar -- Gunnar Wagenknecht gunnar@wagenknecht.org http://wagenknecht.org/
On 19/10/2011 9:10 AM, Gunnar Wagenknecht wrote:
Am 17.10.2011 21:47, schrieb ceki:
I'd like to label the next release as 1.0. Logback is now a mature product and I can't think of a good reason not to go 1.0.
+1.
Your comments are welcome,
Does it mean the API will be stable?
I don't expect going 1.0 will affect API stability. Key interfaces will not evolve unless the change is worth the cost but that was already the previous policy. Were you affected by changes in the logback API? -- Ceki
Am 19.10.2011 11:16, schrieb ceki:
Were you affected by changes in the logback API?
No. But I was more thinking aligns of expressing API changes in the version. For example, previously one had to carefully read the news. API could change between 0.9.x and 0.9.y. Now with 1.0 one could establish a convention/policy. For example, if only service providers/extenders/integrators are affected than it's fine to increment the second number (1.x -> 1.x+1). Thus, as long as only the third number is affected (1.0.x -> 1.0.x+1) I can assume no breaking changes for me and just update. :) -Gunnar -- Gunnar Wagenknecht gunnar@wagenknecht.org http://wagenknecht.org/
Hi, On Mon, Oct 17, 2011 at 9:47 PM, ceki <ceki@qos.ch> wrote:
I'd like to label the next release as 1.0. Logback is now a mature product and I can't think of a good reason not to go 1.0.
+1 for 1.0. The perception of maturity and stability of a >0 major version number will make it easier to bring Logback in to many downstream projects. BR, Jukka Zitting
participants (3)
-
ceki -
Gunnar Wagenknecht -
Jukka Zitting