I know I'm late, but

[+1] Release Apache Libcloud 3.0.0rc1

Also, we need to document workarounds for pysphere if this hasn't been done
already

On Thu, Jan 30, 2020 at 12:13 AM Tomaz Muraus <to...@apache.org> wrote:

> Explicit +1 from me.
>
> [+1] Release Apache Libcloud 3.0.0rc1
>
> This brings total to 3 +1's (Allard, Eric, myself) and no other votes.
>
> I will publish the release announcement and artifacts later today.
>
> Thanks to everyone for their votes.
>
>
> On Fri, Jan 24, 2020 at 3:21 PM Eric Johnson <erjoh...@apache.org> wrote:
>
> > [+1] Release Apache Libcloud 3.0.0rc1
> >
> > On Fri, Jan 24, 2020 at 3:32 AM Tomaz Muraus <to...@apache.org> wrote:
> >
> > > This is a voting thread for Libcloud v3.0.0-rc1
> > >
> > > This release includes various changes, most notable ones being:
> > >
> > > * Drop support for Python versions < 3.5
> > > * Type annotations for the base storage API
> > > * Various improvements in the Azure Blobs driver
> > > * New standard "prefix" keyword argument in the
> > > "{list,iterate}_container_objects"
> > >   methods
> > > * 2 new compute drivers (KubeVirt, LXD)
> > >
> > > This is the first release which drops support for Python 2.7 and Python
> > 3 <
> > > 3.5
> > > and that's why I decided to do a release candidate first.
> > >
> > > This way we give early adopters some time to opt-in and test this
> > > pre-release
> > > version (and potentially identify any issues) before we make a stable
> > > release.
> > >
> > > Full list of changes can be found at
> > >
> > >
> >
> https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-300-rc1
> > >
> > > Release artifacts can be found at
> > > https://www.tomaz.me/misc/libcloud/v3.0.0-rc1/index.html
> > >
> > > (I uploaded them to non apache server since I had issues with sftp
> login
> > to
> > > people.apache.org)
> > >
> > > Please test the release and post your votes.
> > >
> > > +/- 1
> > > [  ]  Release Apache Libcloud 3.0.0rc1
> > >
> > > Vote will be open until January 27th, 2020 (or longer, if needed)
> > >
> >
>

Reply via email to