On 4/5/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
> On 4/5/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>> Niall Pemberton wrote:
>> > On 4/5/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>> >>
>> >> On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>> >> > On 4/4/
Niall Pemberton wrote:
On 4/5/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
> On 4/5/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>>
>> On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>> > On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>> > >
>> > > On 4/4/07,
On 4/5/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
> On 4/5/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>>
>> On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>> > On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>> > >
>> > > On 4/4/07, Dennis Lundberg <[EMAIL
Niall Pemberton wrote:
On 4/5/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> >
> > On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >
> > > Username:
> > > [EMAIL PROTECTED]
> >
>
On 4/5/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> >
> > On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >
> > > Username:
> > > [EMAIL PROTECTED]
> >
> > ah, so not the dennisl
On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>
> On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>
> > Username:
> > [EMAIL PROTECTED]
>
> ah, so not the dennislundberg one. :) I was a bit confused at that one
> not being a jakart
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Username:
> [EMAIL PROTECTED]
ah, so not the dennislundberg one. :) I was a bit confused at that one
not being a jakarta developer.
While you're in there, you should delete your doppelg
On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Username:
[EMAIL PROTECTED]
ah, so not the dennislundberg one. :) I was a bit confused at that one
not being a jakarta developer.
While you're in there, you should delete your doppelganger and assign
its reported issue over to your real us
Henri Yandell wrote:
On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
>
> "Commons Committer" group --> commiter role on all components
> "Jakarta PMC" --> pmc role on all jakarta sub-projects
This sound good to me. Then as Henri said, we should set up a new
Permi
On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
>
> "Commons Committer" group --> commiter role on all components
> "Jakarta PMC" --> pmc role on all jakarta sub-projects
This sound good to me. Then as Henri said, we should set up a new
Permission Scheme. We now h
On 4/4/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
> On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>> On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>> > On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>> > > Can anyone say what the usual practice is for
Niall Pemberton wrote:
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > Can anyone say what the usual practice is for assigning groups/roles
> > for people once they become a commit
On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > Can anyone say what the usual practice is for assigning groups/roles
> >
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > Can anyone say what the usual practice is for assigning groups/roles
> > for people once they become a committer?
> >
> > Theres a "J
On 4/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> Can anyone say what the usual practice is for assigning groups/roles
> for people once they become a committer?
>
> Theres a "Jakarta Developer" group - it gets you "committer" role for
> C
On 4/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
Can anyone say what the usual practice is for assigning groups/roles
for people once they become a committer?
Theres a "Jakarta Developer" group - it gets you "committer" role for
Commons Lang and JCI but strangely nothing else.
Would be sim
Can anyone say what the usual practice is for assigning groups/roles
for people once they become a committer?
Theres a "Jakarta Developer" group - it gets you "committer" role for
Commons Lang and JCI but strangely nothing else.
Would be simpler if it was documented somewhere.
Niall
--
Thought I'd mention this again. It's cron'd nightly:
http://people.apache.org/~bayard/jira-report-for-commons.txt
I often randomly click through the JIRA projects - and it was much
nicer to run down the report and look at each project. The above was
made for an email, but I'll probably go ahead
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-mai
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
getting a wiki change. I'll let this sit for a few days to make
sure no-one -1s, and then go ahead and make it happen.
Scratch that - I misremembered the solution - it was about different
lists, not just moving JIRA and Wiki onto the -commit
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
Thanks. I hadn't noticed that they were different :)
Hen
On 7/20/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
FYI, I updated the issue type scheme of all commons projects today to
the Apache default. This means that we now don't get the Infrastructure
and Geronimo issue types in commons wh
FYI, I updated the issue type scheme of all commons projects today to
the Apache default. This means that we now don't get the Infrastructure
and Geronimo issue types in commons when creating an issue.
No action is required by commoners as a result of this change.
Stephen
As you've noticed, IO is now pretty much in a 'everything has a fix
version' state.
The only exception are Finder issues, which I'd like to move to the
sandbox, and a general issue that I should probably move from IO over
to SITE (deploying javadoc/source for Commons jars).
When modifying versio
On 4/29/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
On Fri, 2006-04-28 at 23:58 +0200, Dennis Lundberg wrote:
> Henri Yandell wrote:
> > In terms of the J***, we should we be asking infra@ what they want to do.
>
> If infra don't require us to use a prefix then we shouldn't use one.
> Keep
On Fri, 2006-04-28 at 23:58 +0200, Dennis Lundberg wrote:
> Henri Yandell wrote:
> > On 4/28/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >
> >> I think that having a naming scheme is a good idea. From a user
> >> standpoint I see no reason for keeping the project ids short (3-4
> >> character
Henri Yandell wrote:
On 4/28/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
I think that having a naming scheme is a good idea. From a user
standpoint I see no reason for keeping the project ids short (3-4
characters). If Jakarta will be sharing the Jira instance with other ASF
projects then us
On 4/28/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
It does seem to be that there's more interest in the full name than
the shorter one.
I don't think we should imply a x character limit either. Hopefully,
everyone will choose the shortest name that still makes sense.
In terms of the J*
On 4/28/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
I think that having a naming scheme is a good idea. From a user
standpoint I see no reason for keeping the project ids short (3-4
characters). If Jakarta will be sharing the Jira instance with other ASF
projects then using a J prefix for Jak
Oleg Kalnichevski wrote:
Henri Yandell wrote:
On 4/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
Given this positive feedback so far, I'm going to email the infra@
mailing list to see how they would go about doing it _if_ we decided
we wanted to move.
I think
On Apr 28, 2006, at 10:29 AM, Henri Yandell wrote:
Dunno if that matches with the infra@ view. Having something with 11
letters is a pain in the arse given that the only time I ever find
myself using the id is: a) to discuss something outside of Jira and b)
to enter into the find box in the top
On 4/28/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 4/28/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> I also find JHCHTTPCORE absolutely horrible. I chose this id as I
> thought it would be the most "politically correct" one. I would very
> much rather prefer HTTPCORE or JHTTPCORE. Do
On 4/28/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
I don't think it's important to have a scheme - it's just a project id
that is used in such a way that users are aware of it. HCO, HTCO,
JHTC. Doesn't matter and I agree with the Atlassian advice on it being
a 3 or 4 letter code.
So:
LANG
I
On 4/28/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
I also find JHCHTTPCORE absolutely horrible. I chose this id as I
thought it would be the most "politically correct" one. I would very
much rather prefer HTTPCORE or JHTTPCORE. Do you envisage a particular
Jira id naming convention for Jak
Big +1 on a move to jira..
Mvgr,
Martin
Henri Yandell wrote:
I know Jelly are on Jira already, and Struts have just moved over to
Jira. Wondering what the view is nowadays on Commons moving to Jira?
Hen
-
To unsubscribe, e-ma
Henri Yandell wrote:
On 4/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
Given this positive feedback so far, I'm going to email the infra@
mailing list to see how they would go about doing it _if_ we decided
we wanted to move.
I think we should be moving fro
On 4/27/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
>
> On 4/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> > Henri Yandell wrote:
> > > Given this positive feedback so far, I'm going to email the infra@
> > > mailing list to see how they would go about doing it _if_ we decided
> > > we wa
On 4/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> Henri Yandell wrote:
> > Given this positive feedback so far, I'm going to email the infra@
> > mailing list to see how they would go about doing it _if_ we decided
> > we wanted to move.
> >
> > I think we should be moving from 1 project
On 4/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
>
> Henri Yandell wrote:
> > Given this positive feedback so far, I'm going to email the infra@
> > mailing list to see how they would go about doing it _if_ we decided
> > we wanted to move.
> >
> > I think we should be moving from 1 projec
Henri Yandell wrote:
Given this positive feedback so far, I'm going to email the infra@
mailing list to see how they would go about doing it _if_ we decided
we wanted to move.
I think we should be moving from 1 project with 37 components to 37
projects - it'll allow us to manage the components i
Henri Yandell wrote:
On 4/25/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
I know Jelly are on Jira already, and Struts have just moved over to
Jira. Wondering what the view is nowadays on Commons moving to Jira?
Except for Mario's -1, things seem to be +1 so far which I must admit
is a bit of
On 4/25/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> I know Jelly are on Jira already, and Struts have just moved over to
> Jira. Wondering what the view is nowadays on Commons moving to Jira?
Except for Mario's -1, things seem to be +1 so far which I must admit
is a bit of a surprise :)
Given
I use to be +0 in regards to Jira migration, but I've read some convincing
arguments, so I'm now firmly +1 in favour. I think the roadmap feature is
almost worth migrating for alone.
Rory
"Jakarta Commons Developers List" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> James
I use to be +0 in regards to Jira migration, but I've read some convincing
arguments, so I'm now firmly +1 in favour. I think the roadmap feature is
almost worth migrating for alone.
Rory
"Jakarta Commons Developers List" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> James
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Carman wrote:
> I'm +1. JIRA is much more user friendly and intuitive, IMHO.
I like JIRA too. I have reported a lot of bugs for other OS projects
using JIRA, cause it's intuitive. As i saw the commons bugzilla
instance first time i was really
Hi Sandy,
> It doesn't make sense to be this adverse to commercial software if you
> agree with the ASL. If you truly have a distaste for commercial
> software then the GPL is probably more fitting with your goals.
>
I am not adverse to commercial software at all, we all have to make money.
We a
Another advantage it's the possibility to customize your dashboard(s) with a
lot of portlets.
You can define what you want to see : the issues open, your votes, ...
It's really useful for developers like us.
Cheers.
Arnaud (Maven's team)
On 4/26/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
>
>
On 4/26/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> Hi!
> > I know Jelly are on Jira already, and Struts have just moved over to
> > Jira. Wondering what the view is nowadays on Commons moving to Jira?
> >
> I am -1 on moving to jira.
>
> I dont understand why we - the open source developers
Henri Yandell wrote:
I know Jelly are on Jira already, and Struts have just moved over to
Jira. Wondering what the view is nowadays on Commons moving to Jira?
Hen
I've been using Jira a lot over in Maven land and I like it. The visual
appearance is so much more appealing than bugzilla, but it
On 4/25/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
>
> Hi!
> > I know Jelly are on Jira already, and Struts have just moved over to
> > Jira. Wondering what the view is nowadays on Commons moving to Jira?
> >
> I am -1 on moving to jira.
>
> I dont understand why we - the open source developer
On 4/25/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> Hi!
> > I know Jelly are on Jira already, and Struts have just moved over to
> > Jira. Wondering what the view is nowadays on Commons moving to Jira?
> >
> I am -1 on moving to jira.
Reason for mentioning Struts above was that I remembered
it looks to me like the asf already licenses/uses jira?
http://issues.apache.org/jira/
so it should only a question about how to customize the behaviour of the
working instance?
regards
engel
Torsten Curdt a écrit :
Guys, it's not as if jira isn't installed already ;)
So the "buuuh! it's comercial" is a bit too late IMO.
I am pretty much +1 ...but not religious about it
...and I hope that everyone who voted -1 has
actually tried to use jira before blocking things
for the wrong reaso
n Source Licenses"?
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 26, 2006 12:46 AM
To: Jakarta Commons Developers List
Subject: [all] Jira?
I know Jelly are on Jira already, and Struts have just moved over to
Jira. Wondering what the view is n
Henri Yandell wrote on Wednesday, April 26, 2006 6:46 AM:
> I know Jelly are on Jira already, and Struts have just moved over to
> Jira. Wondering what the view is nowadays on Commons moving to Jira?
If I put any political decisions aside, I am +1 in JIRA - simply because of its
ease of use.
-
I believe that one of the justifications for installing JIRA in the
first place was that maintaining and upgrading Bugzilla was a big hassle
for the infrastructure team. If that's the case, I'd be willing to
consider moving; the infrastructure team have a hard job to do without
us making it harder.
> "And they conquered all of gaul really all no a small village
> resist ..." ;-)
Hehe ;)
> > ...and I hope that everyone who voted -1 has
> > actually tried to use jira before blocking things
> > for the wrong reasons.
> >
> Yes, the myfaces development team use it - and so do I.
> I c
Hi!
> Guys, it's not as if jira isn't installed already ;)
> So the "buuuh! it's comercial" is a bit too late IMO.
>
"And they conquered all of gaul really all no a small village
resist ..." ;-)
> ...and I hope that everyone who voted -1 has
> actually tried to use jira before blockin
Guys, it's not as if jira isn't installed already ;)
So the "buuuh! it's comercial" is a bit too late IMO.
I am pretty much +1 ...but not religious about it
...and I hope that everyone who voted -1 has
actually tried to use jira before blocking things
for the wrong reasons.
Btw: we had pretty mu
-1 as well for the same reasons. JIRA is a nice product, but Bugzilla is
quite good and fits our needs.
Emmanuel Bourg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
> -Original Message-
> From: Mario Ivankovits [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 26 April 2006 4:16 PM
> To: Jakarta Commons Developers List
> Subject: Re: [all] Jira?
>
>
> Hi!
>
> I am -1 on moving to jira.
>
> I dont understand
Hi!
> I know Jelly are on Jira already, and Struts have just moved over to
> Jira. Wondering what the view is nowadays on Commons moving to Jira?
>
I am -1 on moving to jira.
I dont understand why we - the open source developers and our users -
should help testing a commercial application.
And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd be +1 on the move. I'm not one who bashes Bugzilla for its faults,
but Jira (license aside) is pretty nice to work with. [And the added
'features' that 'could' be utilized would be nice if they're used, too :-)]
Brian
Martin Cooper wrote:
> On 4/
On 4/25/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
>
> I know Jelly are on Jira already, and Struts have just moved over to
> Jira. Wondering what the view is nowadays on Commons moving to Jira?
I used to be a -0.5 on moving to JIRA simply because it's not open source.
However, having delved in
I know Jelly are on Jira already, and Struts have just moved over to
Jira. Wondering what the view is nowadays on Commons moving to Jira?
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PRO
79 matches
Mail list logo
