+1 That should have happened during the actual release. I'm not sure why it didn't.
--Rafael On Thu, May 23, 2013 at 7:11 PM, Robbie Gemmell <robbie.gemm...@gmail.com>wrote: > There is a staging repo on repository.apache.org that appears to have the > 0.4 release artifacts in it and simply wasn't released at the time. > > The files contain the changes from the last change that seems to have gone > into 0.4 (http://svn.apache.org/r1448733), building a copy of the 0.4 > source locally and diffing the contents resulted in no differences within > the contained java class files, and the timestamps seem to align when > accounting for known timezones at the point the release was built. There > were differences in some of the metadata files(timestamps, maven+jvm > versions etc, i.e to be expected), and the the staged 'tests.jar' file > contains $py.class files for the python tests. > > Does it seem acceptable to everyone to simply promote those > previously-staged artifacts now? > > Robbie > > On 23 May 2013 14:45, Phil Harvey <p...@philharveyonline.com> wrote: > > > Hi Hiram, > > > > Did you ever get a reply about this (e.g. on the IRC channel)? > > > > I think Rafi created the 0.4 release candidate but I don't know if > there's > > a specific reason why it hasn't been promoted. > > > > Rafi - can you shed any light on this? I'm happy to lend a hand if > > anything needs doing. > > > > Phil > > > > > > > > On 20 May 2013 15:09, Hiram Chirino <hi...@hiramchirino.com> wrote: > > > > > I don't see the 0.4 release in maven central: > > > > > > http://repo2.maven.org/maven2/org/apache/qpid/proton-api/ > > > > > > Can you guy make sure that a maven deployment is part of the release > > > process? > > > > > > -- > > > Hiram Chirino > > > > > > Engineering | Red Hat, Inc. > > > > > > hchir...@redhat.com | fusesource.com | redhat.com > > > > > > skype: hiramchirino | twitter: @hiramchirino > > > > > > blog: Hiram Chirino's Bit Mojo > > > > > >
