Without the package name change, would it be a drop in replacement? Aside from changes for providers that is. I am wondering what this would look like for clients only.
Gary On Aug 21, 2011, at 8:33, sebb <seb...@gmail.com> wrote: > On 18 August 2011 17:25, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> This is a vote to release Apache Commons VFS 2.0. >> >> Changes made since the last candidate: >> >> * Removed the sandbox project from the delivery, except for the web site. >> * Updated README.txt to remove the existing text and add very basic build >> instructions. >> >> I have also removed files that shouldn't be present in the Maven repository >> from the staging repo, except for the distribution files which will be moved >> to the standard distribution location and not deployed to the Nexus >> repository when the artifacts are released. >> >> [ ] +1 release it >> [ ] +0 go ahead I don't care >> [ ] -1 no, do not release it because. > > The release itself is fine. > > However I still question whether it really needs to break binary > compatibility. > As the news section on the front page says: > > "The API changes are fairly minor and will mostly impact provider > implementations." > > This does not seem like it really requires binary compatibility to be > broken, with all the resulting downstream work that is involved. > > I am therefore abstaining on this vote. > >> Ralph >> >> >> Tag: >> https://svn.apache.org/repos/asf/commons/proper/vfs/tags/commons-vfs2-project-2.0/ >> (revision 1159220). >> >> Site: http://people.apache.org/~rgoers/commons-vfs/site/ > > The News section paragraph contains several items of information and > is not all that easy to read. > > I think it would be good to make the compatibiltity statement stand out more: > - start new paragraphs for "Version 2.0 is not binary compatible ..." > and "The API changes ..." > - possibly embolden some phrases in the second para. > > http://people.apache.org/~rgoers/commons-vfs/site/download.html > > Contains a list of dependencies. Just wondering whether it should > still contain the references to Sandbox? > > [these can be fixed independently of the release] > >> >> The artifacts have been staged to the org.apache.commons-052 (u:rgoers, >> a:99.180.69.21) repository. >> >> The Maven artifacts are at: >> >> https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2/ >> https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2-examples/ >> https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2-project/ >> https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2-distribution/ >> >> and consist of >> >> archetype-catalog.xml >> commons-vfs2-examples-2.0-javadoc.jar >> commons-vfs2-examples-2.0-sources.jar.asc >> commons-vfs2-examples-2.0.pom >> commons-vfs2-examples-2.0-tests.jar >> commons-vfs2-examples-2.0-tests.jar.asc >> commons-vfs2-examples-2.0.jar.asc >> commons-vfs2-examples-2.0.pom.asc >> commons-vfs2-examples-2.0-javadoc.jar.asc >> commons-vfs2-examples-2.0.jar >> commons-vfs2-examples-2.0-sources.jar >> commons-vfs2-project-2.0.pom.asc >> commons-vfs2-project-2.0.pom >> commons-vfs2-distribution-2.0-src.tar.gz >> commons-vfs2-distribution-2.0-src.tar.gz.asc >> commons-vfs2-distribution-2.0-src.zip.asc >> commons-vfs2-distribution-2.0-bin.zip >> commons-vfs2-distribution-2.0-bin.tar.gz >> commons-vfs2-distribution-2.0-bin.tar.gz.asc >> commons-vfs2-distribution-2.0-src.zip >> commons-vfs2-distribution-2.0-bin.zip.asc >> commons-vfs2-2.0.pom.asc >> commons-vfs2-2.0-javadoc.jar >> commons-vfs2-2.0-tests.jar.asc >> commons-vfs2-2.0-tests.jar >> commons-vfs2-2.0.pom >> commons-vfs2-2.0.jar >> commons-vfs2-2.0-sources.jar.asc >> commons-vfs2-2.0-test-sources.jar.asc >> commons-vfs2-2.0.jar.asc >> commons-vfs2-2.0-sources.jar >> commons-vfs2-2.0-test-sources.jar >> commons-vfs2-2.0-javadoc.jar.asc > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
