Dain Sundstrom wrote:
On Jun 16, 2006, at 2:35 PM, David Jencks wrote:
--- Dain Sundstrom [EMAIL PROTECTED] wrote:
I have two thoughts:
1) we have an automated tool to track patches and it
can track votes
and send out these reports.
I'm not convinced automating this will work all that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One thing that a number of the projects do is maintain a
STATUS file with open issues, and have it send to the
dev list once a week.
This has been particularly useful for tracking the status
of patches during RTC. When someone puts up a patch for
I have two thoughts:
1) we have an automated tool to track patches and it can track votes
and send out these reports.
2) IMHO, if patchs start taking longer than a few days to get
committed, we as a project are not going to be successful. I like
the discussions that RTC raise, but we
--- Dain Sundstrom [EMAIL PROTECTED] wrote:
I have two thoughts:
1) we have an automated tool to track patches and it
can track votes
and send out these reports.
I'm not convinced automating this will work all that
well. I do think that all +1 and suggestions should
be made as
On Jun 16, 2006, at 2:35 PM, David Jencks wrote:
--- Dain Sundstrom [EMAIL PROTECTED] wrote:
I have two thoughts:
1) we have an automated tool to track patches and it
can track votes
and send out these reports.
I'm not convinced automating this will work all that
well. I do think that all
I've attached some patches for an incremental step towards pluggable
JACC to http://issues.apache.org/jira/browse/GERONIMO-1563
Pre RTC I would check these in and pray that someone would notice and
if I was really lucky comment, and then continue with the next
steps. We'll see how RTC
David Jencks wrote:
I've attached some patches for an incremental step towards pluggable
JACC to http://issues.apache.org/jira/browse/GERONIMO-1563
Pre RTC I would check these in and pray that someone would notice and
if I was really lucky comment, and then continue with the next steps.
