You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/05/03 15:29:48 UTC
[VOTE] LogKit Code Freeze Plans
Since LogKit is the official loggin mechanism of Avalon, and
used in the Framework and Excalibur, I propose that LogKit
enters code freeze along with the other packages.
All a code freeze means is that no new features will be
added during the freeze, and the API remains the same.
Its purpose is to focus on bug fixes.
VOTE
----
LogKit follows same release plan as Framework/Excalibur
I am +1 as they need each other.
QUESTIONS
---------
Has LogKit ever had an official release?
What version should we apply to it?
Since it is more independant of Framework/Excalibur I don't
think we should match version numbers like MS artificial jump
to Version 6 on its office suite. I don't know if you recall,
but they had Word 5.x, Excel 4.x, PowerPoint 4.x, and Access 2.x
and the next version for all of them was 6.0.
REASONING
---------
LogKit is very useful, and a well written program. It's API has
been fairly stable from the beginning. However, documentation
is severely lacking in that project. It would benefit from the
focus we will be placing on Beta 2 (Documentation).
I found out after talking to my CTO, that the reason he was hesitant
to use Avalon most was the lack of useful documentation. (I can
say this because I wrote most of what we do have). He would like
to see some stuff on how to break down a system into Components.
He is familiar with OO techniques (a SystemUser object, a Dog, etc).
and less with breaking down analasys into useful Components. I would
like to see documentation on the correct manner to set up a Logger,
and how to take advantage of Rolling Log Files, etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [VOTE] LogKit Code Freeze Plans
Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
> Historical versioning has been
> 0.3 -> 0.6 -> 0.7 (when moved to Apache) -> ...
Then lets go for release version 1.0b1
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: [VOTE] LogKit Code Freeze Plans
Posted by Peter Donald <do...@apache.org>.
At 08:01 4/5/01 +0200, Leo Simons wrote:
>> > QUESTIONS
>> > ---------
>> > Has LogKit ever had an official release?
>> > What version should we apply to it?
>> >
>> > Since it is more independant of Framework/Excalibur I don't
>> > think we should match version numbers like MS artificial jump
>> > to Version 6 on its office suite. I don't know if you recall,
>> > but they had Word 5.x, Excel 4.x, PowerPoint 4.x, and Access 2.x
>> > and the next version for all of them was 6.0.
>
>I'd go for 2.0b...
Historical versioning has been
0.3 -> 0.6 -> 0.7 (when moved to Apache) -> ...
So anything above 0.7 is good though I guess I would go with 1.0 - not sure ;)
>I would like to not have a freeze on the xdocs dir in any case - I have
>been working on a "Getting Started with Avalon and Phoenix" tutorial-style
>thing. I will probably try and submit it to JavaWorld as well. It should
>help =)
ooer ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [VOTE] LogKit Code Freeze Plans
Posted by Berin Loritsch <bl...@apache.org>.
Leo Simons wrote:
> I would like to not have a freeze on the xdocs dir in any case - I have
> been working on a "Getting Started with Avalon and Phoenix" tutorial-style
> thing. I will probably try and submit it to JavaWorld as well. It should
> help =)
It should help, but we need to make sure that the documentation (such as it
is) makes sense, and is buildable. We are shooting for a release on May 11,
which is not that far in the future. It might be better to hold off on them
and commit a whole bunch at one time after our release.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: [VOTE] LogKit Code Freeze Plans
Posted by Leo Simons <ma...@leosimons.com>.
> > VOTE
> > ----
> >
> > LogKit follows same release plan as Framework/Excalibur
> >
> > I am +1 as they need each other.
+1
> > QUESTIONS
> > ---------
> > Has LogKit ever had an official release?
> > What version should we apply to it?
> >
> > Since it is more independant of Framework/Excalibur I don't
> > think we should match version numbers like MS artificial jump
> > to Version 6 on its office suite. I don't know if you recall,
> > but they had Word 5.x, Excel 4.x, PowerPoint 4.x, and Access 2.x
> > and the next version for all of them was 6.0.
I'd go for 2.0b...
> > I found out after talking to my CTO, that the reason he was hesitant
> > to use Avalon most was the lack of useful documentation. (I can
> > say this because I wrote most of what we do have). He would like
> > to see some stuff on how to break down a system into Components.
> > He is familiar with OO techniques (a SystemUser object, a Dog, etc).
> > and less with breaking down analasys into useful Components. I would
> > like to see documentation on the correct manner to set up a Logger,
> > and how to take advantage of Rolling Log Files, etc.
I would like to not have a freeze on the xdocs dir in any case - I have
been working on a "Getting Started with Avalon and Phoenix" tutorial-style
thing. I will probably try and submit it to JavaWorld as well. It should
help =)
cheers!
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [VOTE] LogKit Code Freeze Plans
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Berin Loritsch wrote:
>
> Since LogKit is the official loggin mechanism of Avalon, and
> used in the Framework and Excalibur, I propose that LogKit
> enters code freeze along with the other packages.
>
> All a code freeze means is that no new features will be
> added during the freeze, and the API remains the same.
> Its purpose is to focus on bug fixes.
>
> VOTE
> ----
>
> LogKit follows same release plan as Framework/Excalibur
>
> I am +1 as they need each other.
+1
>
> QUESTIONS
> ---------
> Has LogKit ever had an official release?
> What version should we apply to it?
>
> Since it is more independant of Framework/Excalibur I don't
> think we should match version numbers like MS artificial jump
> to Version 6 on its office suite. I don't know if you recall,
> but they had Word 5.x, Excel 4.x, PowerPoint 4.x, and Access 2.x
> and the next version for all of them was 6.0.
>
> REASONING
> ---------
> LogKit is very useful, and a well written program. It's API has
> been fairly stable from the beginning. However, documentation
> is severely lacking in that project. It would benefit from the
> focus we will be placing on Beta 2 (Documentation).
>
> I found out after talking to my CTO, that the reason he was hesitant
> to use Avalon most was the lack of useful documentation. (I can
> say this because I wrote most of what we do have). He would like
> to see some stuff on how to break down a system into Components.
> He is familiar with OO techniques (a SystemUser object, a Dog, etc).
> and less with breaking down analasys into useful Components. I would
> like to see documentation on the correct manner to set up a Logger,
> and how to take advantage of Rolling Log Files, etc.
Yes, we need tons more documentation after beta 1.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [VOTE] LogKit Code Freeze Plans
Posted by Peter Donald <do...@apache.org>.
+1 post my hack ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org