That sounds nice, but than the vote needs to be on general :)
I would be an favor of that..
Mvgr,
Martin
Dennis Lundberg wrote:
>
> Why not move all JIRA notifications to [EMAIL PROTECTED] ?
>
-
To unsubscribe, e-mail: [EMAIL
Joerg Heinicke gmx.de> writes:
> ... splitting it into commons-cvs|svn|scm jakarta.apache.org,
> commons-jira|issues|bugs jakarta.apache.org and the actual dev list for
> discussions ...
I just wanted to ping on this one [1]. There seems to be much agreement about
splitting the list [2]. So is
Henri Yandell wrote:
On 1/6/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 1/6/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
> Henri Yandell gmail.com> writes:
>
> > The spam issue is a tricky decision. Sometimes I turn off the
> > notifications to then do a lot of changes, other times I let t
On 1/7/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Joerg Heinicke wrote:
> Henri Yandell gmail.com> writes:
>
>> The spam issue is a tricky decision. Sometimes I turn off the
>> notifications to then do a lot of changes, other times I let the spam
>> hit the list because moving an issue into
Joerg Heinicke wrote:
Henri Yandell gmail.com> writes:
The spam issue is a tricky decision. Sometimes I turn off the
notifications to then do a lot of changes, other times I let the spam
hit the list because moving an issue into a version is a decision. If
there were a lot of them, I'd be temp
On 1/6/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 1/6/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
> Henri Yandell gmail.com> writes:
>
> > The spam issue is a tricky decision. Sometimes I turn off the
> > notifications to then do a lot of changes, other times I let the spam
> > hit the li
On 1/6/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
Henri Yandell gmail.com> writes:
> The spam issue is a tricky decision. Sometimes I turn off the
> notifications to then do a lot of changes, other times I let the spam
> hit the list because moving an issue into a version is a decision. If
>
Henri Yandell gmail.com> writes:
> The spam issue is a tricky decision. Sometimes I turn off the
> notifications to then do a lot of changes, other times I let the spam
> hit the list because moving an issue into a version is a decision. If
> there were a lot of them, I'd be tempted to send an em
On 1/5/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
Martin Cooper apache.org> writes:
> > > Any exact targetting for unresolved issues will lead to "this
> > > issues hasn't made it into the latest release, we try to get it into the
> > > next one" mails polluting the mailing lists without nea
Martin Cooper apache.org> writes:
> > > Any exact targetting for unresolved issues will lead to "this
> > > issues hasn't made it into the latest release, we try to get it into the
> > > next one" mails polluting the mailing lists without nearly any additional
> > > value.
> >
> > I think that is
On 1/3/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 1/3/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
> Henri Yandell gmail.com> writes:
>
> > The aim is to provide us with information on where projects are
> > release-wise and where we are in terms of answering new issues. Some
> > of our c
On 1/3/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
Henri Yandell gmail.com> writes:
> The aim is to provide us with information on where projects are
> release-wise and where we are in terms of answering new issues. Some
> of our components aren't there - for example Jelly which has 77
> unve
Henri Yandell gmail.com> writes:
> The aim is to provide us with information on where projects are
> release-wise and where we are in terms of answering new issues. Some
> of our components aren't there - for example Jelly which has 77
> unversioned issues and Attributes/Discovery which are ready
Henri Yandell wrote:
On 1/2/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
> Using the commons-nightly/jira-email.vm swizzle script, I've got a
> report for the Commons projects that lets us see the status of things.
> Here's the output:
>
> http://people.apache.org/~bayard/
On 1/2/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
> Using the commons-nightly/jira-email.vm swizzle script, I've got a
> report for the Commons projects that lets us see the status of things.
> Here's the output:
>
> http://people.apache.org/~bayard/jira-report-for-common
Henri Yandell wrote:
Using the commons-nightly/jira-email.vm swizzle script, I've got a
report for the Commons projects that lets us see the status of things.
Here's the output:
http://people.apache.org/~bayard/jira-report-for-commons.txt
The aim is to provide us with information on where proje
Using the commons-nightly/jira-email.vm swizzle script, I've got a
report for the Commons projects that lets us see the status of things.
Here's the output:
http://people.apache.org/~bayard/jira-report-for-commons.txt
The aim is to provide us with information on where projects are
release-wise a
17 matches
Mail list logo
