You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/11/09 16:07:06 UTC
[jira] Created: (MPA-20) create release issues for each plugin to track votes and preparedness
create release issues for each plugin to track votes and preparedness
---------------------------------------------------------------------
Key: MPA-20
URL: http://jira.codehaus.org/browse/MPA-20
Project: Maven Project Administration
Type: Task
Reporter: John Casey
Assigned to: John Casey
Priority: Blocker
should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPA-20) create release issues for each plugin to track votes and preparedness
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-20?page=all ]
Jason van Zyl updated MPA-20:
-----------------------------
Component: issue management
> create release issues for each plugin to track votes and preparedness
> ---------------------------------------------------------------------
>
> Key: MPA-20
> URL: http://jira.codehaus.org/browse/MPA-20
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
>
>
> should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPA-20) create release issues for each plugin to
track votes and preparedness
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-20?page=all ]
Jason van Zyl updated MPA-20:
-----------------------------
Fix Version: 2006-q1
> create release issues for each plugin to track votes and preparedness
> ---------------------------------------------------------------------
>
> Key: MPA-20
> URL: http://jira.codehaus.org/browse/MPA-20
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2006-q1
>
>
> should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPA-20) create release issues for each plugin to track votes and preparedness
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-20?page=comments#action_51288 ]
Jason van Zyl commented on MPA-20:
----------------------------------
I'm now working with Jeff Turner to set up the projects, but I think the release issues being present are a good thing so that users can vote so we know what plug-ins are most desired by users. This process can now be automated anyway so at least the tedium is removed.
> create release issues for each plugin to track votes and preparedness
> ---------------------------------------------------------------------
>
> Key: MPA-20
> URL: http://jira.codehaus.org/browse/MPA-20
> Project: Maven Project Administration
> Type: Task
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
>
>
> should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPA-20) create release issues for each plugin to track votes and preparedness
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-20?page=comments#action_50529 ]
Brett Porter commented on MPA-20:
---------------------------------
this is a pretty tedious way to deal with it... I think it might be better to just work on getting the jira projects established?
> create release issues for each plugin to track votes and preparedness
> ---------------------------------------------------------------------
>
> Key: MPA-20
> URL: http://jira.codehaus.org/browse/MPA-20
> Project: Maven Project Administration
> Type: Task
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
>
>
> should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPA-20) create release issues for each plugin to
track votes and preparedness
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-20?page=all ]
John Casey updated MPA-20:
--------------------------
Assign To: (was: John Casey)
> create release issues for each plugin to track votes and preparedness
> ---------------------------------------------------------------------
>
> Key: MPA-20
> URL: http://jira.codehaus.org/browse/MPA-20
> Project: Maven Project Administration
> Type: Task
> Components: Issue Management
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2006-q1
>
>
> should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPA-20) create release issues for each plugin to
track votes and preparedness
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-20?page=comments#action_54105 ]
Brett Porter commented on MPA-20:
---------------------------------
is this still needed now that the projects exist?
> create release issues for each plugin to track votes and preparedness
> ---------------------------------------------------------------------
>
> Key: MPA-20
> URL: http://jira.codehaus.org/browse/MPA-20
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
>
>
> should be specific to one release of one plugin, and should incorporate links to all outstanding issues for that release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org