[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    RE: [Logging] [VOTE] Commons Logging 1.0 Release
From:       <costinm () covalent ! net>
Date:       2002-01-31 21:57:19
[Download RAW message or body]

As I said, a week would be nice. This is going to be a very important API
as many projects might depend on it. I don't think too many other
commons components will get this level of criticality - any change after
the release _must_ be backward compatible.

So getting the right thing out is quite important. It seems there is
already a majority of +1s ( from the messages I read before getting a
headache :-). I would like to have some time, now that we know this is
going to happen, for more people to look at the APIs, sleep on it,
discuss, etc.

Costin



On Thu, 31 Jan 2002, Scott Sanders wrote:

> Costin,
>
> As long as you are willing to review it thoroughly, I am willing to wait
> to hear your comments.  How long do you need?
>
> Scott
>
> > -----Original Message-----
> > From: costinm@covalent.net [mailto:costinm@covalent.net]
> > Sent: Thursday, January 31, 2002 1:23 PM
> > To: Jakarta Commons Developers List
> > Subject: Re: [Logging] [VOTE] Commons Logging 1.0 Release
> >
> >
> > I'm going to vote +1.
> >
> > I was among those who voted -1 the first time this commons
> > logging was proposed, and my reason was that I hoped log4j
> > would be used instead. It is a top level project, and that's
> > what it is supposed to do - logging.
> >
> > It seems I was wrong. This is not about code, but community,
> > and from some reasons log4j was never accepted by a lot of
> > people as the right solution for the logging API.
> >
> > I would like to ask for about a week before freezing - I want
> > to read the code first, and I suppose other people would want
> > to do the same. This will be an important API, and it needs a
> > lot more review than most other common components.
> >
> >
> > Costin
> >
> >
> > On Tue, 29 Jan 2002, Craig R. McClanahan wrote:
> >
> > > We've refined the commons-logging APIs, and documented the
> > mechanics.
> > > In addition, I've heard from numerous people on various
> > projects that
> > > would like to use these APIs, but are hesitant to do so
> > without a 1.0
> > > release.
> > >
> > > Therefore, I'd like to now propose that we do a 1.0 release of the
> > > commons-logging package, based on the current contents of the CVS
> > > repository for this package.  I will volunteer to act as release
> > > manager, following the standard process for Commons packages:
> > >
> > >   http://jakarta.apache.org/commons/releases.html
> > >
> > > ----- CUT HERE -----
> > > [ ] +1  I support the release of Commons Logging 1.0 and
> > will help [ ]
> > > +0  I support the release, but cannot help [ ] -0  I am not
> > in favor
> > > of the release [ ] -1  I am opposed to this release, and here's why
> > > (attach reasons)
> > > ----- CUT HERE -----
> > >
> > >
> > > Craig McClanahan
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> > > For
> > additional commands,
> > e-mail:
> > > <mailto:commons-dev-help@jakarta.apache.org>
> > >
> > >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> > For
> > additional commands,
> > e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]