Commiting recent changes (was: Code change the Apache way)

["Noel J. Bergman" <no...@devtech.com>]

> > Are we near to seeing stuff commited.. ?
> > apart from the obvious fact that some contentious
> > items can be vetoed *after* commit, I'd say that
> > as long as it builds we should be commiting often.

I generally agree, Danny, and found that to be one of the more frustrating
thing.

Generally speaking, how easy or hard it is it to allow posting proposed
changes into the proposals/ tree, and automating the build?  Something that
would let me say, "./build <proposal>", and have a build made from the HEAD
with the proposed changes applied.  What would be involved, and is this a
viable approach?

> What I will do is post the latest, greatest code

Sounds good, Peter.  As soon as I get it, I should have time to work on the
promised Scheduler <-> Watchdog adaption.

Harmeet, since FetchPOP does use the Scheduler in the way it is designed to
work, I think you do need to address the problem I have mentioned about it
not working properly when inserting a time earlier than the current head of
the list.  Until that is resolved, I don't think that it can replace the
general Scheduler Block.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Commiting recent changes (was: Code change the Apache way)

["Noel J. Bergman" <no...@devtech.com>]

Harmeet,

The Avalon Scheduler doesn't leak.  It gets flooded.  Big difference.
FetchPOP doesn't cause flooding.

In any event, my point is that if anyone is going to be able to use your
Scheduler instead of the default from Avalon, that you'll have to fix that
bug.

	--- Noel

-----Original Message-----
From: Harmeet Bedi [mailto:harmeet@kodemuse.com]
Sent: Friday, October 25, 2002 22:48
To: James Developers List
Subject: Re: Commiting recent changes (was: Code change the Apache way)


----- Original Message -----
From: "Noel J. Bergman" <no...@devtech.com>
> Harmeet, since FetchPOP does use the Scheduler in the way it is designed
> to work, I think you do need to address the problem I have mentioned
> about it not working properly when inserting a time earlier than the
> current head of the list.  Until that is resolved, I don't think that
> it can replace the general Scheduler Block.

If we are going to live with the scheduler, it may be a good idea to have
the bug fixed version that was posted rather than the current one with
memory leak.

Harmeet


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Commiting recent changes (was: Code change the Apache way)

[Harmeet Bedi <ha...@kodemuse.com>]

----- Original Message -----
From: "Noel J. Bergman" <no...@devtech.com>
> Harmeet, since FetchPOP does use the Scheduler in the way it is designed
to
> work, I think you do need to address the problem I have mentioned about it
> not working properly when inserting a time earlier than the current head
of
> the list.  Until that is resolved, I don't think that it can replace the
> general Scheduler Block.

If we are going to live with the scheduler, it may be a good idea to have
the bug fixed version that was posted rather than the current one with
memory leak.

Harmeet


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>