Hi Andrew, I believe that the artifacts are incorrect. The content of the artifacts also seems different e.g. I didn't see the *.source-release.zip though they are produced in the target and seem to be present in 0.3.0. I tried to follow the instructions given by Sean [1] and did the following
1. Checkout the rel/0.4.0 tag 2. cd audience-annotations-component/ 3. mvn clean install -Papache-release 4. mvn deploy For the missing artifacts, I guess I can try to repeat the steps 3 and 4 on yetus-project/pom.xml, audience-annotations/pom.xml and audience-annotations-jdiff/pom.xml but I am not sure that 3-4 are correct/sufficient. Any ideas? Regards Ajay Yadava [1] https://issues.apache.org/jira/browse/YETUS-481?focusedCommentId=15826559&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15826559 On Thu, Feb 2, 2017 at 8:47 PM, Andrew Wang <[email protected]> wrote: > Hi Ajay, > > I see the artifacts on Nexus now. One question, I noticed that 0.3.0 has > artifacts that aren't present in 0.4.0; is this intentional? Namely, > audience-annotations-jdiff and the yetus-project source release. > > Re: artifacts and voting, not sure if there's an ASF policy around this, > but for Hadoop we do push the RC jars to Nexus for the release vote. This > can be useful for downstream testing, since most users consume JARs > artifacts via Nexus. > > Best, > Andrew > > On Thu, Feb 2, 2017 at 4:53 PM, Ajay Yadava <[email protected]> wrote: > > > Hello Andrew, > > > > Thank you for taking time out to look into it. I suspect that the staging > > artifact got removed automatically after some time. I had pushed it on > Jan > > 23rd and updated YETUS-481 for help on verification. I have redeployed it > > and can see it now. Can you please try again? > > > > As for the vote, what you are saying makes sense and also seems to be > > suggested in the guide I pointed earlier. However, the documentation > > indicates this step quite late after the vote and 0.3.0 artifact in nexus > > seems to be 189 days old which is quite after the vote for 0.3.0. Plus, > the > > fact that no one objected during the vote(I hadn't pushed the maven > > artifacts to the staging repository at that time) also makes me feel that > > this might not be the process we have been following. So, I am not sure > > about the way forward. > > > > > > Thanks > > Ajay Yadava > > > > On Wed, Feb 1, 2017 at 6:08 PM, Andrew Wang <[email protected]> > > wrote: > > > > > I logged into Nexus and don't see the 0.4.0 artifacts in staging or via > > > search; did you already release and drop the staging repo? > > > > > > The JARs are also part of the release, so ideally they should have been > > > voted on as part of the 0.4.0 vote thread. > > > > > > Best, > > > Andrew > > > > > > On Tue, Jan 31, 2017 at 2:42 PM, Ajay Yadava <[email protected]> > > > wrote: > > > > > > > Hello team, > > > > > > > > Can someone please help me verifying the maven artifacts for 0.4.0 > > > release? > > > > > > > > I have published the maven artifacts to the staging repository at[1] > > But > > > > due to the fact that I am doing it the first time and there is not > > enough > > > > documentation, I am not sure if I am not sure if I missed something. > > For > > > > more context, you can refer to discussion on YETUS-481 > > > > > > > > Also, do we need to vote on this, as suggested by this guide[2]? > > > > > > > > Regards > > > > Ajay Yadava > > > > [1] https://repository.apache.org/#stagingRepositories > > > > [2] http://www.apache.org/dev/publishing-maven-artifacts.html > > > > -- > > > > Regards > > > > Ajay Yadava > > > > > > > > > >
