Am 2016-12-24 um 04:07 schrieb Dan Tran:
Hi,

We have fixed 18 issues:
*https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12333396
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12333396>*

There are still issues left in JIRA:
*https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC>*

Staging repository:
https://repository.apache.org/content/repositories/maven-1313
https://repository.apache.org/content/repositories/maven-
1313/org/apache/maven/wagon/wagon/2.11/wagon-2.11-source-release.zip

Source release checksum(s):
wagon-2.11-source-release.zip sha1: 98bc0b031880b175e144c55447a62000c58abfa5

Staging site:
*http://maven.apache.org/components/wagon-archives/wagon-LATEST/
<http://maven.apache.org/components/wagon-archives/wagon-LATEST/>*

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html
<https://maven.apache.org/guides/development/guide-testing-releases.html>
Vote open for 72H + 48H to accomodate for holidays

+1

SHA1 is fine, site is fine. Builds passes on Windows but constantly fails on non-Windows, here on my FreeBSD machine as well as on our Jenkins Ubuntu slave. It should probably investigated for the 3.0 release.

Michael




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to