Hi Todd, > You can update the README to reference 1.4 - we'll make a deeper sweep of > the root files when we tag the 1.4 release. Ok, I'll make it now until i remember it ...
> Sounds like you can go ahead and resolve the JIRA issue. But shouldn't I copy the generated jars to the people server etc etc before to close the issue (see bottom) ? > ASF projects can get their artifacts published in the central Maven > repository (eg http://repo2.maven.org/maven2/) by copying them to > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ which > automatically syncs with the central repo. > To do that on people.apache.org copy them to > /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository. > All committers should have access to do that, via ssh. I have it, Ok. > Each artifact MUST have been voted on by a PMC and comply with all the > release requirements like having LICENSE, NOTICE, DISCLAIMER files, be > signed, and indicate they're incubating artifacts in the name eg by including > the "-incubating" suffix in the artifact name. A common way of getting that > vote done is by including the artifacts to be published in a staging area > which is pointed to in the release VOTE. mhhh reading better this probably I'll have to wait for the release 1.4 approved, right (other requirements now should be Ok) ? Or can I do a "pivot-1.4-incubating_maven_test" folder inside my home on that server ? Thanks, Sandro
