You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by anthony shaw <an...@apache.org> on 2018/02/02 08:07:26 UTC
[dev] [VOTE] Release Apache Libcloud 2.3.0
This is a voting thread for Libcloud 2.3.0. It includes all the changes
from trunk which have landed there since v2.2.1.
Most notable changes is the dropping of support for Python 2.6 and 3.3,
both of which are unsupported distributions.
There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes and
improvements for many other drivers.
Full list of changes can be found at
https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-230
Release artifacts can be found at
*http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
<http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
Note that KEYS file can found at
https://dist.apache.org/repos/dist/release/libcloud/KEYS
Please test the release and post your votes.
+/- 1
[ ] Release Apache Libcloud 2.3.0
Vote will be open until February 7th if required.
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by Quentin Pradet <qu...@gmail.com>.
gentle ping
On Mon, Feb 5, 2018 at 6:04 PM, Quentin Pradet <qu...@gmail.com>
wrote:
> The pull request that fixes the tests has been merged thanks to Anthony.
> What is the next step?
>
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by Quentin Pradet <qu...@gmail.com>.
The pull request that fixes the tests has been merged thanks to Anthony.
What is the next step?
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by Quentin Pradet <qu...@gmail.com>.
Thanks Anthony!
I tested the .whl file and I'm +1 on the content of the release even
though I can't vote just yet.
However the tests don't pass with Python 2.7 [0] due to the recent
release of pytest 3.4 which has incompatible logging changes:
https://github.com/apache/libcloud/pull/1170 is needed to fix the
tests. (Tests only fail on Python 2.7 because paramiko is only tested
on Python 2.7.)
[0]: https://travis-ci.org/apache/libcloud/jobs/336449747
On Fri, Feb 2, 2018 at 12:07 PM, anthony shaw <an...@apache.org> wrote:
> This is a voting thread for Libcloud 2.3.0. It includes all the changes
> from trunk which have landed there since v2.2.1.
>
> Most notable changes is the dropping of support for Python 2.6 and 3.3,
> both of which are unsupported distributions.
>
> There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes and
> improvements for many other drivers.
>
> Full list of changes can be found at
> https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-230
>
> Release artifacts can be found at
> *http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
> <http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
>
> Note that KEYS file can found at
> https://dist.apache.org/repos/dist/release/libcloud/KEYS
>
> Please test the release and post your votes.
>
> +/- 1
> [ ] Release Apache Libcloud 2.3.0
>
> Vote will be open until February 7th if required.
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by anthony shaw <an...@gmail.com>.
This voting thread is now closed.
[-1] - 2 (binding)
On Sun, Feb 25, 2018 at 8:06 AM, anthony shaw <an...@gmail.com>
wrote:
> My apologies I’ve been travelling constantly since the thread was started.
>
> Will recreate a new release package and resign the tags tomorrow
>
> On Sun, 25 Feb 2018 at 7:59 am, Tomaz Muraus <to...@apache.org> wrote:
>
>> Yes, if we want to include new changes, new release artifacts need to be
>> generated.
>>
>> In addition to that, 2.3.0-tentative tag needs to be re-created to point
>> at
>> the correct commit for the latest release artifact and a new voting thread
>> needs to be started ("[dev] [VOTE] Release Apache Libcloud 2.3.0 (take 2)"
>> or whatever you may want to call it :)).
>>
>> Edit: I noticed v2.3.0 tag is already there - final release tag should
>> only
>> be created and pushed upstream once the voting thread has passed.
>>
>> On Sat, Feb 24, 2018 at 8:01 PM, Quentin Pradet <quentin.pradet@gmail.com
>> >
>> wrote:
>>
>> > My understanding is that we need to generate new release artifacts. Can
>> > anyone confirm?
>> >
>> > On Wed, Feb 21, 2018 at 9:23 PM, Allard Hoeve <al...@gmail.com>
>> > wrote:
>> >
>> > > [+1] Release Apache Libcloud 2.3.0
>> > >
>> > >
>> > > Op vr 2 feb. 2018 09:07 schreef anthony shaw <anthonyshaw@apache.org
>> >:
>> > >
>> > > > This is a voting thread for Libcloud 2.3.0. It includes all the
>> changes
>> > > > from trunk which have landed there since v2.2.1.
>> > > >
>> > > > Most notable changes is the dropping of support for Python 2.6 and
>> 3.3,
>> > > > both of which are unsupported distributions.
>> > > >
>> > > > There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes
>> and
>> > > > improvements for many other drivers.
>> > > >
>> > > > Full list of changes can be found at
>> > > >
>> > > > https://github.com/apache/libcloud/blob/trunk/CHANGES.
>> > > rst#changes-in-apache-libcloud-230
>> > > >
>> > > > Release artifacts can be found at
>> > > > *http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
>> > > > <http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
>> > > >
>> > > > Note that KEYS file can found at
>> > > > https://dist.apache.org/repos/dist/release/libcloud/KEYS
>> > > >
>> > > > Please test the release and post your votes.
>> > > >
>> > > > +/- 1
>> > > > [ ] Release Apache Libcloud 2.3.0
>> > > >
>> > > > Vote will be open until February 7th if required.
>> > > >
>> > >
>> >
>>
>
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by anthony shaw <an...@gmail.com>.
My apologies I’ve been travelling constantly since the thread was started.
Will recreate a new release package and resign the tags tomorrow
On Sun, 25 Feb 2018 at 7:59 am, Tomaz Muraus <to...@apache.org> wrote:
> Yes, if we want to include new changes, new release artifacts need to be
> generated.
>
> In addition to that, 2.3.0-tentative tag needs to be re-created to point at
> the correct commit for the latest release artifact and a new voting thread
> needs to be started ("[dev] [VOTE] Release Apache Libcloud 2.3.0 (take 2)"
> or whatever you may want to call it :)).
>
> Edit: I noticed v2.3.0 tag is already there - final release tag should only
> be created and pushed upstream once the voting thread has passed.
>
> On Sat, Feb 24, 2018 at 8:01 PM, Quentin Pradet <qu...@gmail.com>
> wrote:
>
> > My understanding is that we need to generate new release artifacts. Can
> > anyone confirm?
> >
> > On Wed, Feb 21, 2018 at 9:23 PM, Allard Hoeve <al...@gmail.com>
> > wrote:
> >
> > > [+1] Release Apache Libcloud 2.3.0
> > >
> > >
> > > Op vr 2 feb. 2018 09:07 schreef anthony shaw <an...@apache.org>:
> > >
> > > > This is a voting thread for Libcloud 2.3.0. It includes all the
> changes
> > > > from trunk which have landed there since v2.2.1.
> > > >
> > > > Most notable changes is the dropping of support for Python 2.6 and
> 3.3,
> > > > both of which are unsupported distributions.
> > > >
> > > > There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes and
> > > > improvements for many other drivers.
> > > >
> > > > Full list of changes can be found at
> > > >
> > > > https://github.com/apache/libcloud/blob/trunk/CHANGES.
> > > rst#changes-in-apache-libcloud-230
> > > >
> > > > Release artifacts can be found at
> > > > *http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
> > > > <http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
> > > >
> > > > Note that KEYS file can found at
> > > > https://dist.apache.org/repos/dist/release/libcloud/KEYS
> > > >
> > > > Please test the release and post your votes.
> > > >
> > > > +/- 1
> > > > [ ] Release Apache Libcloud 2.3.0
> > > >
> > > > Vote will be open until February 7th if required.
> > > >
> > >
> >
>
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by Tomaz Muraus <to...@apache.org>.
Yes, if we want to include new changes, new release artifacts need to be
generated.
In addition to that, 2.3.0-tentative tag needs to be re-created to point at
the correct commit for the latest release artifact and a new voting thread
needs to be started ("[dev] [VOTE] Release Apache Libcloud 2.3.0 (take 2)"
or whatever you may want to call it :)).
Edit: I noticed v2.3.0 tag is already there - final release tag should only
be created and pushed upstream once the voting thread has passed.
On Sat, Feb 24, 2018 at 8:01 PM, Quentin Pradet <qu...@gmail.com>
wrote:
> My understanding is that we need to generate new release artifacts. Can
> anyone confirm?
>
> On Wed, Feb 21, 2018 at 9:23 PM, Allard Hoeve <al...@gmail.com>
> wrote:
>
> > [+1] Release Apache Libcloud 2.3.0
> >
> >
> > Op vr 2 feb. 2018 09:07 schreef anthony shaw <an...@apache.org>:
> >
> > > This is a voting thread for Libcloud 2.3.0. It includes all the changes
> > > from trunk which have landed there since v2.2.1.
> > >
> > > Most notable changes is the dropping of support for Python 2.6 and 3.3,
> > > both of which are unsupported distributions.
> > >
> > > There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes and
> > > improvements for many other drivers.
> > >
> > > Full list of changes can be found at
> > >
> > > https://github.com/apache/libcloud/blob/trunk/CHANGES.
> > rst#changes-in-apache-libcloud-230
> > >
> > > Release artifacts can be found at
> > > *http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
> > > <http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
> > >
> > > Note that KEYS file can found at
> > > https://dist.apache.org/repos/dist/release/libcloud/KEYS
> > >
> > > Please test the release and post your votes.
> > >
> > > +/- 1
> > > [ ] Release Apache Libcloud 2.3.0
> > >
> > > Vote will be open until February 7th if required.
> > >
> >
>
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by Quentin Pradet <qu...@gmail.com>.
My understanding is that we need to generate new release artifacts. Can
anyone confirm?
On Wed, Feb 21, 2018 at 9:23 PM, Allard Hoeve <al...@gmail.com> wrote:
> [+1] Release Apache Libcloud 2.3.0
>
>
> Op vr 2 feb. 2018 09:07 schreef anthony shaw <an...@apache.org>:
>
> > This is a voting thread for Libcloud 2.3.0. It includes all the changes
> > from trunk which have landed there since v2.2.1.
> >
> > Most notable changes is the dropping of support for Python 2.6 and 3.3,
> > both of which are unsupported distributions.
> >
> > There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes and
> > improvements for many other drivers.
> >
> > Full list of changes can be found at
> >
> > https://github.com/apache/libcloud/blob/trunk/CHANGES.
> rst#changes-in-apache-libcloud-230
> >
> > Release artifacts can be found at
> > *http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
> > <http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
> >
> > Note that KEYS file can found at
> > https://dist.apache.org/repos/dist/release/libcloud/KEYS
> >
> > Please test the release and post your votes.
> >
> > +/- 1
> > [ ] Release Apache Libcloud 2.3.0
> >
> > Vote will be open until February 7th if required.
> >
>
Re: [dev] [VOTE] Release Apache Libcloud 2.3.0
Posted by Allard Hoeve <al...@gmail.com>.
[+1] Release Apache Libcloud 2.3.0
Op vr 2 feb. 2018 09:07 schreef anthony shaw <an...@apache.org>:
> This is a voting thread for Libcloud 2.3.0. It includes all the changes
> from trunk which have landed there since v2.2.1.
>
> Most notable changes is the dropping of support for Python 2.6 and 3.3,
> both of which are unsupported distributions.
>
> There are new drivers for UpCloud, Digital Ocean Spaces, bugfixes and
> improvements for many other drivers.
>
> Full list of changes can be found at
>
> https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-230
>
> Release artifacts can be found at
> *http://people.apache.org/~anthonyshaw/libcloud/2.3.0/
> <http://people.apache.org/~anthonyshaw/libcloud/2.3.0/>*
>
> Note that KEYS file can found at
> https://dist.apache.org/repos/dist/release/libcloud/KEYS
>
> Please test the release and post your votes.
>
> +/- 1
> [ ] Release Apache Libcloud 2.3.0
>
> Vote will be open until February 7th if required.
>