On 15 Jun 07, at 9:58 AM 15 Jun 07, Henri Yandell wrote:
On 6/14/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 6/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> I created a "Documentation" version so that
> technical issues wouldn't be polluted by documentation issues.
Documentation is ne
I agree with that. Normally if I intend to fix it later, I just assign it to
myself right away.
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 7:27 AM
To: Maven Developers List
Subject: Re: JIRA Smackdown
Hi,
I'd like to ask that i
On 6/14/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 6/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> I created a "Documentation" version so that
> technical issues wouldn't be polluted by documentation issues.
Documentation is neither a version nor pollution. :)
Given the general 'the d
On 15 Jun 07, at 9:06 AM 15 Jun 07, Brett Porter wrote:
Everything has a component now, and I did a whole bunch of versions
while I was at it.
The components really need to be adjusted (review/approve the
taxonomy and migrate towards that), since I found I had a hard time
picking the rig
Everything has a component now, and I did a whole bunch of versions
while I was at it.
The components really need to be adjusted (review/approve the
taxonomy and migrate towards that), since I found I had a hard time
picking the right one, especially in relation to the project builder,
ap
Quick note - I've added a 'shared components' version for assigning
the stuff that isn't in core's versioning scheme (we need to ship
them out of the project later on - have added that to my notes).
I'm assigning components where they are missing so that it might be
easier to identify dupes
On 15 Jun 07, at 4:27 AM 15 Jun 07, Kenney Westerhof wrote:
Hi,
I'd like to ask that issues reported by PMC members and core
developers
get less strict reviews.
Well, you would most likely assign them to a version/component and
possibly assign them to yourself so they wouldn't end up in
On 15/06/2007, at 9:27 PM, Kenney Westerhof wrote:
When I find an issue that's rather complex I usually describe
how to reproduce it, but I lack the time to write sample projects, at
least when reporting. When i get around to it I reproduce the issue
and fix
it in svn - I normally don't attac
Hi,
I'd like to ask that issues reported by PMC members and core developers
get less strict reviews.
When I find an issue that's rather complex I usually describe
how to reproduce it, but I lack the time to write sample projects, at
least when reporting. When i get around to it I reproduce the is
On 6/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I created a "Documentation" version so that
technical issues wouldn't be polluted by documentation issues.
Documentation is neither a version nor pollution. :)
--
Wendy
-
On 14 Jun 07, at 10:28 PM 14 Jun 07, Brett Porter wrote:
Heh, my mail was trying to tell me something as it rejected a
message asking about these at the same time this arrived :)
MPA-90 and 91 came up to the top of my iGTD box today and I was
going to work on them this afternoon - but noti
Heh, my mail was trying to tell me something as it rejected a message
asking about these at the same time this arrived :)
MPA-90 and 91 came up to the top of my iGTD box today and I was going
to work on them this afternoon - but noticed things had been changed.
This sounds good to me, and I
12 matches
Mail list logo
