+1 (binding)

Il giorno ven 29 mag 2020 alle ore 12:25 Claus Ibsen <claus.ib...@gmail.com>
ha scritto:

> +1 (binding)
>
> On Thu, May 28, 2020 at 8:37 PM Peter Palaga <ppal...@redhat.com> wrote:
> >
> > The staging repo
> > https://repository.apache.org/content/repositories/orgapachecamel-1216/
> > works now thanks to ASF infra team. -- P
> >
> > On 28/05/2020 17:28, Peter Palaga wrote:
> > > Hi again,
> > >
> > > I found that Nexus UI displays the artifacts in the staging repo
> through
> > > the following URL:
> > >
> > >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1216/content
> > >
> > >
> > > It is not very comfortable for browsing, but it can be used for testing
> > > with Maven, just add something like the following to your settings.xml:
> > > https://gist.github.com/ppalaga/62c413f997fcba94966ec8fcb89776c3
> > >
> > > So I think, technically, the staging repo is verifiable and we can
> > > proceed with the voting.
> > >
> > > Let's reset the voting timer now so that everyone has enough time to
> > > check. I'll close the voting on Monday 2020-06-01 around 9:00 a.m. CET.
> > >
> > > Thanks for your patience,
> > >
> > > -- Peter
> > >
> > >
> > >
> > > On 27/05/2020 22:02, Peter Palaga wrote:
> > >> I have filed https://issues.apache.org/jira/browse/INFRA-20343
> > >>
> > >> BTW, committers can access the staging repo over the Nexus UI
> > >> https://repository.apache.org/ with their ASF LDAP credentials. It
> > >> allows some basic checks. But of course, it is a very poor replacement
> > >> of a plain Maven staging repo.
> > >>
> > >> This older report https://issues.sonatype.org/browse/OSSRH-19080
> > >> recommends either to ignore the unavailability of the staging repo
> > >> (because the release operation works as expected after that) or deploy
> > >> anew.
> > >>
> > >> Let's see what the ASF infra says.
> > >>
> > >> -- P
> > >>
> > >> On 27/05/2020 17:44, Andrea Cosentino wrote:
> > >>> I think INFRA has some troubles in the last days.
> > >>>
> > >>> Syncing between Apache Repo and Maven Central is not working and
> > >>> there are similar cases to this release, like
> > >>> this
> https://issues.apache.org/jira/browse/INFRA-20334?jql=project%20%3D%20INFRA%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC
> > >>>
> > >>>
> > >>> @Peter Palaga I think you should open an issue to INFRA for this and
> > >>> see what we'll be their response.
> > >>>
> > >>> I know they updated Nexus too.
> > >>>
> > >>> Usually even if the repository is closed, it should be possible to
> > >>> use it in any application by pointing it..
> > >>>
> > >>> There is definitely something wrong, but on the INFRA side.
> > >>>
> > >>> --
> > >>> Andrea Cosentino
> > >>> ----------------------------------
> > >>> Apache Camel PMC Chair
> > >>> Apache Karaf Committer
> > >>> Apache Servicemix PMC Member
> > >>> Email: ancosen1...@yahoo.com
> > >>> Twitter: @oscerd2
> > >>> Github: oscerd
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> > >>> <lburgazz...@gmail.com> wrote:
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> mh, was too fast as there should be something wrong:
> > >>>
> > >>> - can't download sources using the link in the mail as I get:
> > >>>    "404 - Repository "orgapachecamel-1216 (staging: open)"
> > >>> [id=orgapachecamel-1216] exists but is not exposed"
> > >>> - can't use the staging repo as maven fails to download artefacts:
> > >>>    "Non-resolvable import POM: Could not find artifact
> > >>> org.apache.camel.quarkus:camel-quarkus-bom:pom:1.0.0-CR1 in
> > >>> apache.staging (
> > >>>
> https://repository.apache.org/content/repositories/orgapachecamel-1216)"
> > >>>
> > >>> so I have to change my vote to -1 as I can't validate it.
> > >>>
> > >>> ---
> > >>> Luca Burgazzoli
> > >>>
> > >>>
> > >>> On Wed, May 27, 2020 at 5:10 PM Luca Burgazzoli <
> lburgazz...@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> +1 (binding)
> > >>>>
> > >>>> ---
> > >>>> Luca Burgazzoli
> > >>>>
> > >>>>
> > >>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <ppal...@redhat.com>
> > >>>> wrote:
> > >>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> This is a vote to release Apache Camel Quarkus 1.0.0-CR1
> > >>>>>
> > >>>>> What's new:
> > >>>>> * Camel 3.3.0
> > >>>>> * Quarkus 1.5.0.Final
> > >>>>> * Fixed issues:
> > >>>>> https://github.com/apache/camel-quarkus/milestone/2?closed=1
> > >>>>>
> > >>>>> Staging repository:
> > >>>>>
> https://repository.apache.org/content/repositories/orgapachecamel-1216
> > >>>>>
> > >>>>> Tag:
> > >>>>>
> > >>>>>
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=tag;h=d6b2bcb4cffad9e165d55a2f28f2ac72ce57ad15
> > >>>>>
> > >>>>>
> > >>>>> Source release package:
> > >>>>>
> > >>>>>
> https://repository.apache.org/content/repositories/orgapachecamel-1216/org/apache/camel/quarkus/camel-quarkus/1.0.0-CR1/camel-quarkus-1.0.0-CR1-src.zip
> > >>>>>
> > >>>>>
> > >>>>> Please test this release candidate and cast your vote.
> > >>>>>
> > >>>>> [ ] +1 Release the binary as Apache Camel Quarkus 1.0.0-CR1
> > >>>>> [ ] -1 Veto the release (provide specific comments)
> > >>>>>
> > >>>>> The vote is open for at least 48 hours.
> > >>>>>
> > >>>>> Thanks,
> > >>>>>
> > >>>>> -- Peter
> > >>>>>
> > >>>>>
> > >>>
> > >>
> > >
> >
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Reply via email to