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 noticed things had been
changed.
This sounds good to me, and I'll get started on the 'reviewed'
bucket. If I understand you correctly, these aren't actually
reviewed yet, and this bucket should go away over time (with things
going straight into an expected roadmap, right?) So no new issues
go in there, and we try and break it down, but get more vigilant on
the unscheduled bucket.
Yup. Just to keep an eye on incoming while we clean up.
I strongly disagree with the Documentation 'version'. I've found it
to be problematic, and the components should be sufficient. Just
exclude those from the filter to get the technical issues. I
understand we don't currently distribute and version the
documentation, but I think we are all of the opinion now that we
should, right? I've no problem keeping it for clean up purposes, as
long as (again) no new things are going in there.
I think the vast majority of those issue span versions, and the most
commonly looked at view is the dashboard with versions. This is
really just a deficiency with the dashboard but I want to see the
technical issues. Maybe we can get filters to show as the default
view but given the complexity in trying to change the way anything is
viewed in JIRA I picked the version for documentation.
So I'll continue by reviewing some jiras and documenting this.
Thanks,
Brett
On 15/06/2007, at 3:18 PM, Jason van Zyl wrote:
Hi,
The 2.0.7 release will go out tomorrow, and in order to get some
decent vote feedback it would be good to clean up JIRA so that we
have an accurate 2.0.x list people can vote on for issues they
would like fixed in 2.0.8. I created a "Documentation" version so
that technical issues wouldn't be polluted by documentation
issues. I also created a "Reviewed Pending Version Assignment"
where I put everything that's probably been looked at (probably
not entirely true) so that anything coming in from now on in the
unscheduled we can process. I think between all of us we can
probably keep that empty most weeks by assigning a version,
closing if duplicated, or closing due to being incomplete.
Some simple things you can do if you have a few minutes to spare:
- look in the reviewed pending version assignment and try to put
the issue in 2.0.x or 2.1.x
- pick your favorite component and look for duplicates
- issues describing a remotely complicated problem without a
sample project get close as incomplete
- look at issues you've reported and check and see if they have
been resolved
- linking issues up that look similiar so we can close issues
together if they are resolved.
Even if we get rid of the complete cruft like already resolved,
dupes, and incomplete issues that will greatly help.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
