On Mon, 2005-10-31 at 15:08 +1100, Brett Porter wrote:
> Jason van Zyl wrote:
> > On Mon, 2005-10-31 at 08:53 +1100, Brett Porter wrote:
> >
> >>Sounds fine to me (there is a design component that can be used).
> >
> >
> > I think it would be more then design as the first one I can think of
> >
Jason van Zyl wrote:
On Mon, 2005-10-31 at 08:53 +1100, Brett Porter wrote:
Sounds fine to me (there is a design component that can be used).
I think it would be more then design as the first one I can think of
that is more task oriented is starting a campaign to find a lot more
mirrors on t
On Mon, 2005-10-31 at 08:53 +1100, Brett Porter wrote:
> Sounds fine to me (there is a design component that can be used).
I think it would be more then design as the first one I can think of
that is more task oriented is starting a campaign to find a lot more
mirrors on the scale of CPAN for perl
Sounds fine to me (there is a design component that can be used).
Let's leave responsibility of the original poster to follow an issue
through to conclusion. I still have the dev process flagged, for
example. I could just as easily file that to start with.
The main thing I want to avoid is us
true enough, and with the trackback features of jira and confluence issues
and pages can be linked up very easily..
On 10/30/05, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On Sun, 2005-10-30 at 10:57 -0500, Jesse McConnell wrote:
> > great idea, I am finding it a pain to keep up on things too..
On Sun, 2005-10-30 at 10:57 -0500, Jesse McConnell wrote:
> great idea, I am finding it a pain to keep up on things too..
>
> although the lionshare of dev@maven.apache.org emails that I think I have
> seen are related to automated processes and jira issues themselves...so
> perhaps all that autom
great idea, I am finding it a pain to keep up on things too..
although the lionshare of dev@maven.apache.org emails that I think I have
seen are related to automated processes and jira issues themselves...so
perhaps all that automatically generated email should be shifted to another
email list...k
Hi,
I wanted to field ideas on how to track development/project
issues/discussions. Lately with the volume of mail I myself have found
it difficult to keep track of things we have been discussing. A couple
topics I remember are:
- standard j2ee layout
- our own development process
But sifting th
