Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-710 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-710 Summary: Change policy for posting upload requests Type: Improvement Status: Unassigned Priority: Minor Time Spent: Unknown Remaining: 5 minutes Project: maven Components: Repo Jar Requests documentation Assignee: Reporter: Martin Skopp Created: Fri, 22 Aug 2003 4:31 AM Updated: Fri, 22 Aug 2003 4:31 AM Description: Preferred method for upload request is changed to create a JIRA issue (is currently: send mail to maven-dev)! Vote result was 6x "+" on Fri Aug 22 11:20:59 CEST 2003 Comment from bob mcwhirter <[EMAIL PROTECTED]>: There's a component under the Maven project called "Repo Jar Requests" for just that purpose.� I'd probably call it as "Task" as far as the type of JIRA issue it should be. Since Jira notifies the list, going via Jira accomplishes both dev@ notification and archival of the request (and who made it) in an easy-to-find location.� Additionally, when the admin slurps the jar and closes the task, the list and requester will once-again be notified. So, I'm definitely +1 on Jira, as that's what I've been recommending as The Righ Way for a while now, anyhoo.� Or, if you're active in the #maven channel, that's /sometimes/ a good way to go also, if you need it Right Now. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
