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.pra...@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 <allardho...@gmail.com>
> wrote:
>
> > [+1] Release Apache Libcloud 2.3.0
> >
> >
> > Op vr 2 feb. 2018 09:07 schreef anthony shaw <anthonys...@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.
> > >
> >
>
