You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Mark Womack <mw...@apache.org> on 2005/05/12 07:05:18 UTC

[VOTE] Release Overview

OK, consolidating the dicussions we have had the past few days, I would like 
to propose the following:

1) Release 1.2.11 with JMS build fix, maybe some other critical fixes 
(action item: determine the other fixes).  Timeframe is almost immediate, 
within the next 2 weeks.

2) Abandon the 1.3 version number, the main branch becomes version 1.5 
below.

3) Release a 1.4 version with the TRACE change and other fixes that will 
make life happier for the user base (action item: determine the other 
changes).  No major structural changes.  Just most "important" bugfixes. 
The base of the 1.4 code would start from the v1_2branch.  Timeframe is 
within a month of the 1.2.11 release.

4) Release a 1.5 version based on the current main branch.  This would be 
what we are calling v1.3 today.  Timeframe: release of first final version 
by 10/2005.

Exact timeline for the 1.5 version is TBD, but I think we have discussed the 
basics.  I am not proposing we change the version to 2.0.  Again, to me that 
means much bigger changes, and we should reserve that version number for 
when we want to make the bigger changes.

I am +1 on the above, and I am committing to make it happen.  I am willing 
to be the release manager for the proposed versions.  We will all need to 
focus and do what we need to complete these releases, especially v1.5.

-Mark 



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


RE: [VOTE] Release Overview

Posted by Andy McBride <an...@dsl.pipex.com>.
Hi,

> -----Original Message-----
> From: Curt Arnold [mailto:carnold@apache.org]
> Sent: 13 May 2005 04:49
> To: Log4J Developers List
> Subject: Re: [VOTE] Release Overview
> 
> 
> On May 12, 2005, at 6:44 PM, Andy McBride wrote:
> 
> > Hi,
> > The current cvs head contains breaking changes including the
> > removal of
> > org.apache.log4j.jmx.HierarchyDynamicMBean,
> > org.apache.log4j.spi.ErrorHandler and
> > org.apache.log4j.spi.ErrorCode without
> > any apparent replacement or deprecation cycle.
> >
> 
> Nice to know some names of the disappeared.  Is that a complete list?

No just the ones that broke the app I tried the upgrade on. 

> 
> 
> > The removal and re-implementation of
> > org.apache.log4j.RollingFileAppender
> > does not maintain compatibility with existing code as it claims in the
> > javadoc as it does not support subclasses.  Again no deprecation
> > cycle.
> 
> Probably need to clarify the JavaDoc, though the explicit "final" on
> the class indicates that it wasn't intended or expected to be
> compatible for extension, though hopefully it is compatible for use.
> The primary motivator was to allow projects that had used, but not
> extended, o.a.l.RFA and o.a.l.DailyRFA to work with both 1.2.x and 1.3.
> 

The class was not final in 1.2.9 therefore the API was open to extension.  

I'm quite happy to refactor my code to utilise a better rolling API but a
deprecation cycle would have been nice to give advance warnings about
potentially incompatible code.  

I thought the whole point of 1.2.9 was to enable users to 'prepare' for
incompatible API changes in 1.3?  The app I tried was working happily with
1.2.9 so I was unprepared for the changes required to upgrade to 1.3alpha.  

Either a whole lot more documentation needs to be written or a new release
produced which marks the relevant classes and methods as deprecated.  

Regards

Andy



> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Curt Arnold <ca...@apache.org>.
On May 12, 2005, at 6:44 PM, Andy McBride wrote:

> Hi,
> The current cvs head contains breaking changes including the  
> removal of
> org.apache.log4j.jmx.HierarchyDynamicMBean,
> org.apache.log4j.spi.ErrorHandler and  
> org.apache.log4j.spi.ErrorCode without
> any apparent replacement or deprecation cycle.
>

Nice to know some names of the disappeared.  Is that a complete list?


> The removal and re-implementation of  
> org.apache.log4j.RollingFileAppender
> does not maintain compatibility with existing code as it claims in the
> javadoc as it does not support subclasses.  Again no deprecation  
> cycle.

Probably need to clarify the JavaDoc, though the explicit "final" on  
the class indicates that it wasn't intended or expected to be  
compatible for extension, though hopefully it is compatible for use.   
The primary motivator was to allow projects that had used, but not  
extended, o.a.l.RFA and o.a.l.DailyRFA to work with both 1.2.x and 1.3.


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


RE: [VOTE] Release Overview

Posted by Andy McBride <an...@dsl.pipex.com>.
Hi,

> -----Original Message-----
> From: Curt Arnold [mailto:carnold@apache.org]
> Sent: 12 May 2005 19:18
> To: Log4J Developers List
> Subject: Re: [VOTE] Release Overview
> 
> 
> On May 12, 2005, at 12:05 PM, Yoav Shapira wrote:
> >>> 3) Release a 1.4 version with the TRACE change and other fixes
> >>> that will
> >>> make life happier for the user base (action item: determine the
> >>> other
> >>> changes).  No major structural changes.  Just most "important"
> >>> bugfixes.
> >>> The base of the 1.4 code would start from the v1_2branch.
> >>> Timeframe is
> >>> within a month of the 1.2.11 release.
> >>>
> >
> > I'd like 1.3 = 1.2 + TRACE.  I'm also OK with 1.2.12 = 1.2.11 +
> > TRACE.  But
> > no 1.4/1.5.
> >
> 
> I'd prefer 1.2.12 for 1.2.11 + TRACE over 1.3 since that label is
> already associated with much more substantial changes.
> 

Yoav has a good point that skipping the 1.3 label could cause confusion and
with that it mind it would probably be better to use the 1.3 label for a
branch of 1.2 with trace + *additions*

As long as the final decision on the labelling of the branches, and what
they mean in terms of stability, compatibility and features are well
published and documented on the website, then people will know what to
expect.  

The 1.2 branch could be continued for additional functionality but then
there would still be a huge leap to 1.3 based on current cvs head.

To me an a.b.c version scheme means that
a = major changes in api or functionality
b = minor functionality improvements along with bugfixes
c = bugfix release

> >
> > These (Domains, Joran, etc.) ARE huge changes, easily sufficient
> > for a 2.0
> > version number IMHO.
> >
> 
> However, if we use the big 2.0 for changes that were not expected to
> be breaking that would put a psychic barrier to jumping to 3.0 in
> short order to introduce intentional breaking changes like final
> removal of Category/Level, reducing visiblility of protected members,
> finer-grain locking, etc.
> 
> My desire is that we eliminate the unintentional breaking changes
> regardless of what version label we assign.  However, if we are going
> to release a disruptive build, it is best to get all the pain over
> with.  Maybe would could proceed with the 1.3 release cycle, but
> reserve the right to abandon it in preference to a 2.0 release if the
> 2.0 branch seems to be coming together in a timely manner.

The current cvs head contains breaking changes including the removal of
org.apache.log4j.jmx.HierarchyDynamicMBean,
org.apache.log4j.spi.ErrorHandler and org.apache.log4j.spi.ErrorCode without
any apparent replacement or deprecation cycle.  

The removal and re-implementation of org.apache.log4j.RollingFileAppender
does not maintain compatibility with existing code as it claims in the
javadoc as it does not support subclasses.  Again no deprecation cycle.  

I'm not arguing about the validity of these changes, I just think that they
can only form an *A* release and a better migration path be provided.

Regards

Andy


> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Endre Stølsvik <En...@Stolsvik.com>.
On Thu, 12 May 2005, Curt Arnold wrote:

|
| On May 12, 2005, at 12:05 PM, Yoav Shapira wrote:
| >>> 3) Release a 1.4 version with the TRACE change and other fixes
| >>> that will
| >>> make life happier for the user base (action item: determine the
| >>> other
| >>> changes).  No major structural changes.  Just most "important"
| >>> bugfixes.
| >>> The base of the 1.4 code would start from the v1_2branch.
| >>> Timeframe is
| >>> within a month of the 1.2.11 release.
| >>>
| >
| > I'd like 1.3 = 1.2 + TRACE.  I'm also OK with 1.2.12 = 1.2.11 +
| > TRACE.  But
| > no 1.4/1.5.
| >
|
| I'd prefer 1.2.12 for 1.2.11 + TRACE over 1.3 since that label is
| already associated with much more substantial changes.
|
| >
| > These (Domains, Joran, etc.) ARE huge changes, easily sufficient
| > for a 2.0
| > version number IMHO.
| >
|
| However, if we use the big 2.0 for changes that were not expected to
| be breaking that would put a psychic barrier to jumping to 3.0 in
| short order to introduce intentional breaking changes like final
| removal of Category/Level, reducing visiblility of protected members,
| finer-grain locking, etc.

Why can't you just get rid of Category with the 1.3 / 2.0 then?

I really thought that that was the plan already..

You've been keeping the "next release" not happening long enough for
people to expect the entire system to be totally remade anyway, so just go
for a Category deletion and final-nessig and whatever, and define the 2.0
as the next big thing, that will come ASAP RSN.

Also, don't go into the java-versioning-trap: the "1." just sticks
forever, and then eventually you'll just drop it, doing the EXTREMELY lame
"1.5.0" -> "5.0" move..

I think that you could come away clean with "redefining" the 1.3 to be
1.2+TRACE_and_some - people have kinda lost interest in the 1.3 version by
now, I believe. How many are using a hundred-months old alpha-something?
How many are -actually- using a CVS checkout?? I mean, people use this
stuff _in production_ - that's not the place for alphas and CVS checkouts.

Define your new version-scheme online, and get cracking. Everybody will be
happy.

-- 
Endre Stølsvik -  Endre@CoreTrek.[no|com]
   Work[+47 23100271] Mobile[+47 93054050] Fax[+47 23100299]


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Curt Arnold <ca...@apache.org>.
On May 12, 2005, at 12:05 PM, Yoav Shapira wrote:
>>> 3) Release a 1.4 version with the TRACE change and other fixes  
>>> that will
>>> make life happier for the user base (action item: determine the  
>>> other
>>> changes).  No major structural changes.  Just most "important"  
>>> bugfixes.
>>> The base of the 1.4 code would start from the v1_2branch.   
>>> Timeframe is
>>> within a month of the 1.2.11 release.
>>>
>
> I'd like 1.3 = 1.2 + TRACE.  I'm also OK with 1.2.12 = 1.2.11 +  
> TRACE.  But
> no 1.4/1.5.
>

I'd prefer 1.2.12 for 1.2.11 + TRACE over 1.3 since that label is  
already associated with much more substantial changes.

>
> These (Domains, Joran, etc.) ARE huge changes, easily sufficient  
> for a 2.0
> version number IMHO.
>

However, if we use the big 2.0 for changes that were not expected to  
be breaking that would put a psychic barrier to jumping to 3.0 in  
short order to introduce intentional breaking changes like final  
removal of Category/Level, reducing visiblility of protected members,  
finer-grain locking, etc.

My desire is that we eliminate the unintentional breaking changes  
regardless of what version label we assign.  However, if we are going  
to release a disruptive build, it is best to get all the pain over  
with.  Maybe would could proceed with the 1.3 release cycle, but  
reserve the right to abandon it in preference to a 2.0 release if the  
2.0 branch seems to be coming together in a timely manner.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


RE: [VOTE] Release Overview

Posted by Yoav Shapira <yo...@MIT.EDU>.
Hi,
I largely agree with Jacob and Elias.  However, I don't like the 1.4/1.5
discussion: jumping version numbers confuses users, as I found out first
hand with Tomcat, even when there's good reasoning for it.

> > 1) Release 1.2.11 with JMS build fix, maybe some other critical fixes
> > (action item: determine the other fixes).  Timeframe is almost
> immediate,
> > within the next 2 weeks.

+1.

> > 2) Abandon the 1.3 version number, the main branch becomes version 1.5
> > below.

-0.

> > 3) Release a 1.4 version with the TRACE change and other fixes that will
> > make life happier for the user base (action item: determine the other
> > changes).  No major structural changes.  Just most "important" bugfixes.
> > The base of the 1.4 code would start from the v1_2branch.  Timeframe is
> > within a month of the 1.2.11 release.

I'd like 1.3 = 1.2 + TRACE.  I'm also OK with 1.2.12 = 1.2.11 + TRACE.  But
no 1.4/1.5.

> > 4) Release a 1.5 version based on the current main branch.  This would
> be
> > what we are calling v1.3 today.  Timeframe: release of first final
> version
> > by 10/2005.

Confusing.

> >
> > Exact timeline for the 1.5 version is TBD, but I think we have discussed
> the
> > basics.  I am not proposing we change the version to 2.0.  Again, to me
> that
> > means much bigger changes, and we should reserve that version number for
> > when we want to make the bigger changes.

These (Domains, Joran, etc.) ARE huge changes, easily sufficient for a 2.0
version number IMHO.

Note, however, that my -0's are just that, and not -1's.  I don't have
sufficient time commitment that I feel comfortable jinxing someone else's
efforts.  Whatever we do, when this vote/discussion concludes, I'd like our
action plan to be posted on log4j-user and the web site.

Yoav


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Jacob Kjome <ho...@visi.com>.
After reading some of the responses to this, I think I have to agree with Elias.
 Trace is an addition, not a subtraction, so it shouldn't hurt anyone.  Besides,
previous Log4j-1.2.x releases have added features.  I'm not sure why this should
be any different?  Given the fact that the head will take some time to get to a
stable release point, I think any eariler statement that the 1.2.x branch
should be all but frozen becomes null and void.  We shouldn't be breaking the
existing API, but I see no reason not to add features and bugfixes to 1.2.x. 
Having a whole separate version number for a release with minor changes that
doesn't break existing functionality seems both confusing and unnecessary.

As for 1.5 -vs- 2.0, I guess that kind of makes sense.  Then again, we could
just bite the bullet and make the changes we'd like to make and just call it
2.0.

In any case, I'm not going to be able to put much time into this as work and
other things have been keeping me pretty busy.  As such, I'm +0 to the changes
proposed by Mark.  In other words, I defer to those who are taking a more
active development role.


Jake

Quoting Mark Womack <mw...@apache.org>:

> OK, consolidating the dicussions we have had the past few days, I would like
> to propose the following:
>
> 1) Release 1.2.11 with JMS build fix, maybe some other critical fixes
> (action item: determine the other fixes).  Timeframe is almost immediate,
> within the next 2 weeks.
>
> 2) Abandon the 1.3 version number, the main branch becomes version 1.5
> below.
>
> 3) Release a 1.4 version with the TRACE change and other fixes that will
> make life happier for the user base (action item: determine the other
> changes).  No major structural changes.  Just most "important" bugfixes.
> The base of the 1.4 code would start from the v1_2branch.  Timeframe is
> within a month of the 1.2.11 release.
>
> 4) Release a 1.5 version based on the current main branch.  This would be
> what we are calling v1.3 today.  Timeframe: release of first final version
> by 10/2005.
>
> Exact timeline for the 1.5 version is TBD, but I think we have discussed the
> basics.  I am not proposing we change the version to 2.0.  Again, to me that
> means much bigger changes, and we should reserve that version number for
> when we want to make the bigger changes.
>
> I am +1 on the above, and I am committing to make it happen.  I am willing
> to be the release manager for the proposed versions.  We will all need to
> focus and do what we need to complete these releases, especially v1.5.
>
> -Mark
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>




---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Peter DeGregorio <pd...@comcast.net>.
Regarding adding a trace level to 1.2 if this is done it would be good to 
have a way to externally detect whether the version supports a trace level. 
Commons Logging currently detects pre-1.3 log4j version and acts accordingly 
by checking Priority.class.isAssignableFrom(Level.class) though where trace 
is concerned it doesn't but that is another story. If a trace level where 
added to 1.2 the test in JCL for pre-1.3 version isn't going to pick it up. 
If there were some other way in 1.2 to know the version then JCL can be 
modified to correctly map their trace to log4 trace rather than log4j debug. 
The result would be a user of both log4j and JCL who is up-to-date with 
current (minor) version would be able to take advanage of trace in log4j.

As for adding a trace level before the major release, please do! I look 
forward to giving an early retirement to trace4j 
http://home.comcast.net/~pdegregorio/ a clone of log4 1.2.9 with trace 
enabled.

Peter

----- Original Message ----- 
From: "Paul Smith" <ps...@aconex.com>
To: "Log4J Developers List" <lo...@logging.apache.org>
Sent: Thursday, May 12, 2005 3:47 AM
Subject: Re: [VOTE] Release Overview


> Mark, I appreciate your energy you have at the moment, it's inspiring.
>
> On 12/05/2005, at 3:05 PM, Mark Womack wrote:
>
>
>>
>> 2) Abandon the 1.3 version number, the main branch becomes version  1.5 
>> below.
>
> If we do this, we should probably post some rationale to the rest of  the 
> community, everyone's been following 1.3, so we should be open  about how 
> this all came to be.  Lets not "Do a Sun" and change labels  for the hell 
> of it without a clear message to the community.
>
>>
>> 3) Release a 1.4 version with the TRACE change and other fixes that  will 
>> make life happier for the user base (action item: determine  the other 
>> changes).  No major structural changes.  Just most  "important" bugfixes. 
>> The base of the 1.4 code would start from the  v1_2branch.  Timeframe is 
>> within a month of the 1.2.11 release.
>>
> This action has the risk that 1.4 blows out to be a bigger release  than 
> necessary.  It will also mean that quite a bit of back-porting  effort 
> will be needed. This stuff is already in HEAD, and will  require time and 
> testing to make sure it's perfect ported to the  older branch..
>
> This is the classic time investment problem.  Do we keep plowing  ahead to 
> 1.3 completion, setting only very small goals to be left to  do for 1.3? 
> We have the advantage at the moment that people are  trying out 1.3 as it 
> stands now, and going through the change  management, I'd hate for them to 
> through that effort away.  (as a  side note: we'll need good documentation 
> on how to convert a project  from 1.2.x to 1.3/1.5)
>
> I think the 1.4 release as you suggest is going to be a big  distraction. 
> The _last_ thing we want is a poor release, and so I  see 
> poor-old-1.3-now-1.5 not nearing completion till next year  because we'll 
> spend so much time on 1.4... :(  I'm not saying we  shouldn't do this, 
> just expressing my feelings.
>
>> 4) Release a 1.5 version based on the current main branch.  This  would 
>> be what we are calling v1.3 today.  Timeframe: release of  first final 
>> version by 10/2005.
>
> This is sad, because so many people have problems with the 
> DailyRollingFileAppender that 1.3 could solve, but I know trying to  fix 
> that in 1.4 is asking for trouble.
>>
>
>> I am +1 on the above, and I am committing to make it happen.  I am 
>> willing to be the release manager for the proposed versions.  We  will 
>> all need to focus and do what we need to complete these  releases, 
>> especially v1.5.
>>
> I'm willing to put up and help with whatever if someone can help me  by 
> saying "I think you can do this, can you have it done by such-n- such".  I 
> know that probably makes me sound like a baby, but it's  more likely I'll 
> commit and actually do it right now! :)  Life is  really full on for me at 
> the moment.
>
> I hope I don't come across as a Negative Nelly.  I'm glad that we're 
> actively having this discussion, because I feel we have drifted along  for 
> a while (and I've just drifted along without doing anything for a  while).
>
> Please, those non log4j developers, speak up with your say about what  you 
> want.
>
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Paul Smith <ps...@aconex.com>.
Mark, I appreciate your energy you have at the moment, it's inspiring.

On 12/05/2005, at 3:05 PM, Mark Womack wrote:


>
> 2) Abandon the 1.3 version number, the main branch becomes version  
> 1.5 below.

If we do this, we should probably post some rationale to the rest of  
the community, everyone's been following 1.3, so we should be open  
about how this all came to be.  Lets not "Do a Sun" and change labels  
for the hell of it without a clear message to the community.

>
> 3) Release a 1.4 version with the TRACE change and other fixes that  
> will make life happier for the user base (action item: determine  
> the other changes).  No major structural changes.  Just most  
> "important" bugfixes. The base of the 1.4 code would start from the  
> v1_2branch.  Timeframe is within a month of the 1.2.11 release.
>
This action has the risk that 1.4 blows out to be a bigger release  
than necessary.  It will also mean that quite a bit of back-porting  
effort will be needed. This stuff is already in HEAD, and will  
require time and testing to make sure it's perfect ported to the  
older branch..

This is the classic time investment problem.  Do we keep plowing  
ahead to 1.3 completion, setting only very small goals to be left to  
do for 1.3?  We have the advantage at the moment that people are  
trying out 1.3 as it stands now, and going through the change  
management, I'd hate for them to through that effort away.  (as a  
side note: we'll need good documentation on how to convert a project  
from 1.2.x to 1.3/1.5)

I think the 1.4 release as you suggest is going to be a big  
distraction.  The _last_ thing we want is a poor release, and so I  
see poor-old-1.3-now-1.5 not nearing completion till next year  
because we'll spend so much time on 1.4... :(  I'm not saying we  
shouldn't do this, just expressing my feelings.

> 4) Release a 1.5 version based on the current main branch.  This  
> would be what we are calling v1.3 today.  Timeframe: release of  
> first final version by 10/2005.

This is sad, because so many people have problems with the  
DailyRollingFileAppender that 1.3 could solve, but I know trying to  
fix that in 1.4 is asking for trouble.
>

> I am +1 on the above, and I am committing to make it happen.  I am  
> willing to be the release manager for the proposed versions.  We  
> will all need to focus and do what we need to complete these  
> releases, especially v1.5.
>
I'm willing to put up and help with whatever if someone can help me  
by saying "I think you can do this, can you have it done by such-n- 
such".  I know that probably makes me sound like a baby, but it's  
more likely I'll commit and actually do it right now! :)  Life is  
really full on for me at the moment.

I hope I don't come across as a Negative Nelly.  I'm glad that we're  
actively having this discussion, because I feel we have drifted along  
for a while (and I've just drifted along without doing anything for a  
while).

Please, those non log4j developers, speak up with your say about what  
you want.

cheers,

Paul Smith

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Elias Ross <er...@m-qube.com>.
On Wed, 2005-05-11 at 22:05 -0700, Mark Womack wrote:

> 1) Release 1.2.11 with JMS build fix, maybe some other critical fixes 
> (action item: determine the other fixes).  Timeframe is almost immediate, 
> within the next 2 weeks.

Agree.

> 2) Abandon the 1.3 version number, the main branch becomes version 1.5 
> below.

As a end-user and developer, I am often confused when versions jump like
that.  I would still go with 1.3 or 2.0.

> 3) Release a 1.4 version with the TRACE change and other fixes that will 
> make life happier for the user base (action item: determine the other 
> changes).  No major structural changes.  Just most "important" bugfixes. 
> The base of the 1.4 code would start from the v1_2branch.  Timeframe is 
> within a month of the 1.2.11 release.

If it's a bug fix release, it should go with 1.2.  The TRACE feature is
so minor (IMHO) that adding to to 1.2 seems like not a problem.  This
would confuse users.  I bet though, that users will wait for a real 1.3
or 2.0.

> 4) Release a 1.5 version based on the current main branch.  This would be 
> what we are calling v1.3 today.  Timeframe: release of first final version 
> by 10/2005.

Again, I would stick with 1.3 or 2.0.

In summary:  Release 1.2.11, release a follow on 1.2.12 with minor
features.  Release 1.3 this year.  (Six months or so is not a long time,
though.)

IMHO, if a library makes me do just one little change, I would prefer to
go with the latest version and make X changes.  Because for me, it's the
same number of check-ins, same number of bugs to file, same amount of QA
iterations for one small change as one larger set of changes.



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE] Release Overview

Posted by Curt Arnold <ca...@apache.org>.
I was just thinking the same thing.  Relabeling the 1.3 as 1.5 gives  
us the option to do an interim minor release and have something to  
call it even if the decision to actually prepare a release to occupy  
that number was deferred.  And it also preserves the big 2.0 for  
bigger changes (so long Category).

+1


On May 12, 2005, at 12:05 AM, Mark Womack wrote:

> OK, consolidating the dicussions we have had the past few days, I  
> would like to propose the following:
>
> 1) Release 1.2.11 with JMS build fix, maybe some other critical  
> fixes (action item: determine the other fixes).  Timeframe is  
> almost immediate, within the next 2 weeks.
>
> 2) Abandon the 1.3 version number, the main branch becomes version  
> 1.5 below.
>
> 3) Release a 1.4 version with the TRACE change and other fixes that  
> will make life happier for the user base (action item: determine  
> the other changes).  No major structural changes.  Just most  
> "important" bugfixes. The base of the 1.4 code would start from the  
> v1_2branch.  Timeframe is within a month of the 1.2.11 release.
>
> 4) Release a 1.5 version based on the current main branch.  This  
> would be what we are calling v1.3 today.  Timeframe: release of  
> first final version by 10/2005.
>
> Exact timeline for the 1.5 version is TBD, but I think we have  
> discussed the basics.  I am not proposing we change the version to  
> 2.0.  Again, to me that means much bigger changes, and we should  
> reserve that version number for when we want to make the bigger  
> changes.
>
> I am +1 on the above, and I am committing to make it happen.  I am  
> willing to be the release manager for the proposed versions.  We  
> will all need to focus and do what we need to complete these  
> releases, especially v1.5.
>
> -Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org