You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Peter Palaga <pp...@redhat.com> on 2020/05/27 15:08:16 UTC
[VOTE] Release Apache Camel-Quarkus 1.0.0-CR1
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
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Peter Palaga <pp...@redhat.com>.
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: ancosen1985@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
>> <lb...@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 <lb...@gmail.com>
>> wrote:
>>
>>> +1 (binding)
>>>
>>> ---
>>> Luca Burgazzoli
>>>
>>>
>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>>>
>>>>
>>
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Andrea Cosentino <an...@gmail.com>.
+1 (binding)
Il giorno ven 29 mag 2020 alle ore 12:25 Claus Ibsen <cl...@gmail.com>
ha scritto:
> +1 (binding)
>
> On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> > >>> Twitter: @oscerd2
> > >>> Github: oscerd
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> > >>> <lb...@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 <
> lburgazzoli@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> +1 (binding)
> > >>>>
> > >>>> ---
> > >>>> Luca Burgazzoli
> > >>>>
> > >>>>
> > >>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Claus Ibsen <cl...@gmail.com>.
+1 (binding)
On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> >>> Twitter: @oscerd2
> >>> Github: oscerd
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> >>> <lb...@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 <lb...@gmail.com>
> >>> wrote:
> >>>
> >>>> +1 (binding)
> >>>>
> >>>> ---
> >>>> Luca Burgazzoli
> >>>>
> >>>>
> >>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Luca Burgazzoli <lb...@gmail.com>.
Peter,
do you have time to cancel the vote and perform a new release ?
---
Luca Burgazzoli
On Fri, May 29, 2020 at 4:41 PM Claus Ibsen <cl...@gmail.com> wrote:
> On Fri, May 29, 2020 at 3:59 PM Luca Burgazzoli <lb...@gmail.com>
> wrote:
> >
> > I've unfortunately found a blocking issue [1] and provided a related PR
> [2]
> > I think we should cancel this vote and do a new release.
> >
>
> Yeah I am okay with this. Getting JAXB properly removed and fixed is
> great for making camel-quarkus small, fast and light.
> Ideally if we could cut the release today/tomorrow so we have it to be
> released soonish.
> People can still these these binaries while a new one is being made.
>
> > [1] https://github.com/apache/camel-quarkus/issues/1275
> > [2] https://github.com/apache/camel-quarkus/pull/1276
> >
> > ---
> > Luca Burgazzoli
> >
> >
> > On Fri, May 29, 2020 at 3:14 PM Alex Dettinger <al...@gmail.com>
> > wrote:
> >
> > > +1 (bindng)
> > >
> > > Just filed https://github.com/apache/camel-quarkus/issues/1274, but
> looks
> > > minor,
> > > Alex
> > >
> > > On Fri, May 29, 2020 at 2:29 PM Jean-Baptiste Onofre <jb...@nanthrax.net>
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > > Le 29 mai 2020 à 12:05, Luca Burgazzoli <lb...@gmail.com> a
> > > écrit
> > > > :
> > > > >
> > > > > I've been able to test the 1.0.0-CR1 against camel-k-runtime and
> > > > everything
> > > > > seems fine so here by +1 (binding)
> > > > >
> > > > > ---
> > > > > Luca Burgazzoli
> > > > >
> > > > >
> > > > > On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> > > > >>>>> Twitter: @oscerd2
> > > > >>>>> Github: oscerd
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> > > > >>>>> <lb...@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 <
> > > > lburgazzoli@gmail.com
> > > > >>>
> > > > >>>>> wrote:
> > > > >>>>>
> > > > >>>>>> +1 (binding)
> > > > >>>>>>
> > > > >>>>>> ---
> > > > >>>>>> Luca Burgazzoli
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <
> ppalaga@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
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, May 29, 2020 at 3:59 PM Luca Burgazzoli <lb...@gmail.com> wrote:
>
> I've unfortunately found a blocking issue [1] and provided a related PR [2]
> I think we should cancel this vote and do a new release.
>
Yeah I am okay with this. Getting JAXB properly removed and fixed is
great for making camel-quarkus small, fast and light.
Ideally if we could cut the release today/tomorrow so we have it to be
released soonish.
People can still these these binaries while a new one is being made.
> [1] https://github.com/apache/camel-quarkus/issues/1275
> [2] https://github.com/apache/camel-quarkus/pull/1276
>
> ---
> Luca Burgazzoli
>
>
> On Fri, May 29, 2020 at 3:14 PM Alex Dettinger <al...@gmail.com>
> wrote:
>
> > +1 (bindng)
> >
> > Just filed https://github.com/apache/camel-quarkus/issues/1274, but looks
> > minor,
> > Alex
> >
> > On Fri, May 29, 2020 at 2:29 PM Jean-Baptiste Onofre <jb...@nanthrax.net>
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Regards
> > > JB
> > >
> > > > Le 29 mai 2020 à 12:05, Luca Burgazzoli <lb...@gmail.com> a
> > écrit
> > > :
> > > >
> > > > I've been able to test the 1.0.0-CR1 against camel-k-runtime and
> > > everything
> > > > seems fine so here by +1 (binding)
> > > >
> > > > ---
> > > > Luca Burgazzoli
> > > >
> > > >
> > > > On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> > > >>>>> Twitter: @oscerd2
> > > >>>>> Github: oscerd
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> > > >>>>> <lb...@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 <
> > > lburgazzoli@gmail.com
> > > >>>
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> +1 (binding)
> > > >>>>>>
> > > >>>>>> ---
> > > >>>>>> Luca Burgazzoli
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Luca Burgazzoli <lb...@gmail.com>.
I've unfortunately found a blocking issue [1] and provided a related PR [2]
I think we should cancel this vote and do a new release.
[1] https://github.com/apache/camel-quarkus/issues/1275
[2] https://github.com/apache/camel-quarkus/pull/1276
---
Luca Burgazzoli
On Fri, May 29, 2020 at 3:14 PM Alex Dettinger <al...@gmail.com>
wrote:
> +1 (bindng)
>
> Just filed https://github.com/apache/camel-quarkus/issues/1274, but looks
> minor,
> Alex
>
> On Fri, May 29, 2020 at 2:29 PM Jean-Baptiste Onofre <jb...@nanthrax.net>
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 29 mai 2020 à 12:05, Luca Burgazzoli <lb...@gmail.com> a
> écrit
> > :
> > >
> > > I've been able to test the 1.0.0-CR1 against camel-k-runtime and
> > everything
> > > seems fine so here by +1 (binding)
> > >
> > > ---
> > > Luca Burgazzoli
> > >
> > >
> > > On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> > >>>>> Twitter: @oscerd2
> > >>>>> Github: oscerd
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> > >>>>> <lb...@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 <
> > lburgazzoli@gmail.com
> > >>>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> +1 (binding)
> > >>>>>>
> > >>>>>> ---
> > >>>>>> Luca Burgazzoli
> > >>>>>>
> > >>>>>>
> > >>>>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
> > >>>>>>>
> > >>>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >>
> >
> >
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Alex Dettinger <al...@gmail.com>.
+1 (bindng)
Just filed https://github.com/apache/camel-quarkus/issues/1274, but looks
minor,
Alex
On Fri, May 29, 2020 at 2:29 PM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> +1 (binding)
>
> Regards
> JB
>
> > Le 29 mai 2020 à 12:05, Luca Burgazzoli <lb...@gmail.com> a écrit
> :
> >
> > I've been able to test the 1.0.0-CR1 against camel-k-runtime and
> everything
> > seems fine so here by +1 (binding)
> >
> > ---
> > Luca Burgazzoli
> >
> >
> > On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> >>>>> Twitter: @oscerd2
> >>>>> Github: oscerd
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> >>>>> <lb...@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 <
> lburgazzoli@gmail.com
> >>>
> >>>>> wrote:
> >>>>>
> >>>>>> +1 (binding)
> >>>>>>
> >>>>>> ---
> >>>>>> Luca Burgazzoli
> >>>>>>
> >>>>>>
> >>>>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
+1 (binding)
Regards
JB
> Le 29 mai 2020 à 12:05, Luca Burgazzoli <lb...@gmail.com> a écrit :
>
> I've been able to test the 1.0.0-CR1 against camel-k-runtime and everything
> seems fine so here by +1 (binding)
>
> ---
> Luca Burgazzoli
>
>
> On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
>>>>> Twitter: @oscerd2
>>>>> Github: oscerd
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
>>>>> <lb...@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 <lburgazzoli@gmail.com
>>>
>>>>> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> ---
>>>>>> Luca Burgazzoli
>>>>>>
>>>>>>
>>>>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>
>>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Luca Burgazzoli <lb...@gmail.com>.
I've been able to test the 1.0.0-CR1 against camel-k-runtime and everything
seems fine so here by +1 (binding)
---
Luca Burgazzoli
On Thu, May 28, 2020 at 8:37 PM Peter Palaga <pp...@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: ancosen1985@yahoo.com
> >>> Twitter: @oscerd2
> >>> Github: oscerd
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
> >>> <lb...@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 <lburgazzoli@gmail.com
> >
> >>> wrote:
> >>>
> >>>> +1 (binding)
> >>>>
> >>>> ---
> >>>> Luca Burgazzoli
> >>>>
> >>>>
> >>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
> >>>>>
> >>>>>
> >>>
> >>
> >
>
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Peter Palaga <pp...@redhat.com>.
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: ancosen1985@yahoo.com
>>> Twitter: @oscerd2
>>> Github: oscerd
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
>>> <lb...@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 <lb...@gmail.com>
>>> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> ---
>>>> Luca Burgazzoli
>>>>
>>>>
>>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>>>>
>>>>>
>>>
>>
>
Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Peter Palaga <pp...@redhat.com>.
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: ancosen1985@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli
>> <lb...@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 <lb...@gmail.com>
>> wrote:
>>
>>> +1 (binding)
>>>
>>> ---
>>> Luca Burgazzoli
>>>
>>>
>>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>>>
>>>>
>>
>
Re: [VOTE] Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Peter Palaga <pp...@redhat.com>.
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: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli <lb...@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 <lb...@gmail.com>
> wrote:
>
>> +1 (binding)
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>>
>>>
>
Re: [VOTE] Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
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: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, May 27, 2020, 05:40:02 PM GMT+2, Luca Burgazzoli <lb...@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 <lb...@gmail.com>
wrote:
> +1 (binding)
>
> ---
> Luca Burgazzoli
>
>
> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>
>>
Re: [VOTE] Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Luca Burgazzoli <lb...@gmail.com>.
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 <lb...@gmail.com>
wrote:
> +1 (binding)
>
> ---
> Luca Burgazzoli
>
>
> On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>>
>>
Re: [VOTE] Release Apache Camel-Quarkus 1.0.0-CR1
Posted by Luca Burgazzoli <lb...@gmail.com>.
+1 (binding)
---
Luca Burgazzoli
On Wed, May 27, 2020 at 5:08 PM Peter Palaga <pp...@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
>
>