FWIW, I think that JAMES should not be shipped with an out of the box
config that is broken. Delaying the release long enough to either change
the config to exclude POP3 or fix the bug is a necessary evil. We lose
more credibility by shipping software that doesn't work than by shipping it
a little late.
To paraphrase a recently famous quote:
An open source project is neither early nor late - it arrives exactly when
it is ready to.
:-)
ADK
--------------------------------------------
There is no magic.
"Rollo, Dan"
<[EMAIL PROTECTED] To: 'James Developers List'
<[EMAIL PROTECTED]>
g> cc:
Subject: RE: There is no active
development on James
20/12/2002
09:13
Please respond
to "James
Developers
List"
I have to agree with the statement that this bug makes James 2.1 useless
out
of the box. As I've mentioned on this list before, I'm stuck with using a
very obsolete version of James until file storage is fixed. Not fixing this
bug means James 2.1 will not work "out of the box" until the version after
2.1. This makes for really bad first impressions of James.
This has been a glaring bug for a long time, but the length of time the bug
has existed doesn't diminish it's importance.
(I have no voting rights, but wanted to share my hope that I can upgrade my
James install sometime soon.)
Dan
-----Original Message-----
From: Peter M. Goldstein [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 3:03 PM
To: James Developers List
Subject: RE: There is no active development on James
All,
IMHO, this is ridiculous.
If the bug is glaring now, it was glaring when we
discussed the list of bugs for release. And when it's
come up on the list before. Again and again and
again. There was a conscious decision (with
discussion) to defer this bug because we're intending
to redo the repositories.
Consider this a -1 vote on further delaying the
release for something we've discussed over and over
and over again.
If you want to update the 2.1 POP3 docs to clarify
this issue, that would be fine.
If you want to put out a 2.2 with this fix, great.
Please do it after the seemingly endless 2.1 is out
the door.
But personally I'm just plain sick of 2.1 and want to
be done with it.
--Peter
--- Danny Angus <[EMAIL PROTECTED]> wrote:
>
> On the basis that it should be on the list of things
> to fix anyway, having
> hung around for, I say go fix it.
>
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8839
>
> d.
>
> > -----Original Message-----
> > From: Serge Knystautas
> [mailto:[EMAIL PROTECTED]]
> > Sent: 19 December 2002 18:38
> > To: James Developers List
> > Subject: Re: There is no active development on
> James
> >
> >
> > Danny,
> >
> > This is such a glaring bug, to not patch it is to
> say we DO NOT support
> > POP3 file storage support (and would need to
> announce that very loudly
> > since this is the configuration out of the box).
> I think it's great the
> > code is more scalable, cleaner, better documented,
> but this has been
> > such a glaring bug for so long. Heck, it's just
> one of those poorly
> > thought out "features" of Avalon, and it wouldn't
> take much work to just
> > copy the code and undo the change that broke this.
> Ok, it'd be a little
> > more work to be backwards compatible, but still,
> really not that much.
> >
> > Can we vote to let me patch this? (or show me the
> previous vote so I can
> > appeal to however blocked it... I've searched the
> archives for the bug #
> > and can't find it).
> >
> > --
> > Serge Knystautas
> > Loki Technologies - Unstoppable Websites
> > http://www.lokitech.com
> >
> > Danny Angus wrote:
> > > James in in a code freeze pending release of
> version 2.1
> > >
> > > I can't say when the release is likely to
> happen, but it is
> > unlikely that
> > > this issue is going to be addressed before then.
> > >
> > > The reason for it not being fixed before now is
> because we
> > inherit it from
> > > Avalon.
> > > We are intending to replace that with our own
> filesystem code
> > in the next
> > > cycle.
> > >
> > > d.
> > >
> > >
> > >
> > >>-----Original Message-----
> > >>From: Dejan Nenov
> [mailto:[EMAIL PROTECTED]]
> > >>Sent: 19 December 2002 07:44
> > >>To: [EMAIL PROTECTED]
> > >>Subject: There is no active development on James
> > >>
> > >>
> > >>To any committers / active contributors to James
> development out there -
> > >>can you please review and verify bug 15460 -
> unless no one else can
> > >>reproduce the problem - it seems to be making
> James totally unusable!
> > >>
> > >>
> > >>
> > >>Thank you,
> > >>
> > >>
> > >>
> > >>Dejan
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
**************************************************************************
This e-mail and any files transmitted with it may contain privileged or
confidential information. It is solely for use by the individual for whom
it is intended, even if addressed incorrectly. If you received this e-mail
in error, please notify the sender; do not disclose, copy, distribute, or
take any action in reliance on the contents of this information; and delete
it from your system. Any other use of this e-mail is prohibited. Thank you
for your compliance.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-----------------------------------------------------------------------------------------------
Have you seen our website?.... http://www.vodafone.co.nz
CAUTION: This correspondence is confidential and intended for the named recipient(s)
only.
If you are not the named recipient and receive this correspondence in error, you must
not copy,
distribute or take any action in reliance on it and you should delete it from your
system and
notify the sender immediately. Thank you.
Unless otherwise stated, any views or opinions expressed are solely those of the
author and do
not represent those of Vodafone New Zealand Limited.
Vodafone New Zealand Limited
21 Pitt Street, Private Bag 92161, Auckland, 1020, New Zealand
Telephone + 64 9 357 5100
Facsimile + 64 9 377 0962
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
