It’s been released onto PyPI and the Apache dist servers I’ll do the
announcement email this evening.

On Sat, 3 Mar 2018 at 4:55 pm, anthony shaw <anthony.p.s...@gmail.com>
wrote:

> Vote passed
>
> [+1] - 5 (3 binding)
> [0] - 0
> [-1] - 0
>
> On Sat, Mar 3, 2018 at 12:39 AM, Eric Johnson <erjoh...@apache.org> wrote:
>
>> Sorry for the lag and lgtm.
>>
>> [+1] Release Apache Libcloud 2.3.0
>>
>>
>> On Sun, Feb 25, 2018 at 7:12 PM anthony shaw <anthony.p.s...@gmail.com>
>> wrote:
>>
>> > This is a *replacement* voting thread for Libcloud 2.3.0. It includes
>> all
>> > the changes
>> > from trunk which have landed there since v2.2.1.
>> >
>> > --- note on previous thread ---
>> > It has additional commits from the original thread that fix the build.
>> No
>> > new features are part of this distribution compared with the previous
>> > thread.
>> >
>> > The v2.3.0-tentative tag has been adjusted
>> > https://github.com/apache/libcloud/tree/v2.3.0-tentative to this commit
>> >
>> >
>> https://github.com/apache/libcloud/commit/a119e396814bf12b7d5631f1f2d97a43c63020a5
>> > -------
>> >
>> > Most notable changes are 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
>> > <
>> 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-2/
>> > <http://people.apache.org/~anthonyshaw/libcloud/2.3.0-2/>*
>> >
>> > 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 March 2nd if required.
>> >
>>
>
>

Reply via email to