He will not mind (TM) :D

So... now we can start to drop IoSessionLogger and you could add JUL
MDC formatter into org.apache.mina.util, right?

Trustin


On Jan 25, 2008 6:10 PM, Maarten Bosteels <[EMAIL PROTECTED]> wrote:
> On Jan 25, 2008 10:08 AM, Maarten Bosteels <[EMAIL PROTECTED]> wrote:
>
> > Hello all,
> >
> > On Jan 25, 2008 9:56 AM, Trustin Lee <[EMAIL PROTECTED]> wrote:
> >
> > > I'd wait for a new SLF4J release that enables MDC for
> > > java.util.logging and consequently simplifies MINA Logging
> > > dramatically.  That is the only issue to be resolved before we release
> > > 2.0.0-M1.  Maarten and Ceki is working on it, so let's wait a little
> > > bit more for him and Ceki.
> >
> >
> > <Maarten> By the way, any idea when the next version of SLF4J will be
> > released ?
> >
> > <Ceki> Real soon now (TM). Once slf4j-converter run properly and a
> > remaining few bugs
> > in SLF4J get fixed, I'll make a release. It should be this month or early
> > February.
> >
>
> Note that this wasn't an official announcement by Ceki in any way.
> I copy-pasted it from a private message, I hope Ceki doesn't mind :-)
>
>
>
> >
> >
> > I will try to add some MDC-aware jukl formatters over the weekend.
> >
> >
> > > If the new release of SLF4J is getting late, we can just do what we
> > > planned to do; just drop IoSessionLogger and support MDC for JDK later
> > > when the new SLF4J is released.
> >
> >
> > We could already start replacing usage of IoSessionLogger with plain SLF4J
> > Logger instances on the trunk ?
> > And once the new SLF4J is released,  we can release the milestone. WDYT ?
> >
> > Emmanuel, you said
> > "There are no roadmap atm. Two versions are expected (2.0.0-M1 and
> > 2.0.0-M2), but they barely contains any issue."
> >
> > I don't understand ?  According to JIRA "99 of 102 issues have been
> > resolved" for 2.0.0-M1
> >
> > regards,
> > Maarten
> >
> >
> > > Other unscheduled issues are mostly feature addition, unreproduceable
> > > bugs or bug reports for the trunk, so we will have to schedule it as
> > > soon as 2.0.0-M1 is released.
> > >
> > > Trustin
> > >
> > > On Jan 25, 2008 4:13 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Alex Karasulu wrote:
> > > > > Hi all,
> > > > >
> > > > > What does everyone think about a 2.0 milestone release in the near
> > > future?
> > > > > After a convo on IRC many feel that milestone releases do not
> > > guarantee API
> > > > > stability.  If this is the case we could get a milestone out so
> > > users can
> > > > > kick the tires on the API changes and give feedback so we can
> > > adjust.
> > > > >
> > > > I would like to see some 2.0 milestones soon
> > > >
> > > > There are a few things to work out though :
> > > > - There are no roadmap atm. Two versions are expected (2.0.0-M1 and
> > > > 2.0.0-M2), but they barely contains any issue.
> > > > - There are 44 unscheduled issues. It would be good to schedule those
> > > > issues into the created milestones
> > > > - There are only 6 open bugs, so I guess we are close to a milestone,
> > > as
> > > > soon as thise bug are fixed.
> > > >
> > > > Now, a lot of improvements are expected to be made, but we don't know
> > > > which version they are targeting.
> > > >
> > > > Generally speaking, it might be a good thing to use JIRA roadmap
> > > > management a bit more.
> > > >
> > > > Hope it helps.
> > > >
> > > > --
> > > > --
> > > > cordialement, regards,
> > > > Emmanuel Lécharny
> > > > www.iktek.com
> > > > directory.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > what we call human nature is actually human habit
> > > --
> > > http://gleamynode.net/
> > > --
> > > PGP Key ID: 0x0255ECA6
> > >
> >
> >
>



-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6

Reply via email to