Re: [dev] [VOTE] Release Apache Libcloud 2.6.0

[Rick van de Loo]

[ +1] Release Apache Libcloud 2.6.0

Looks good

Op zo 25 aug. 2019 om 15:47 schreef Jerry Chen :

> [+1]  Release Apache Libcloud 2.6.0
>
> > On Aug 24, 2019, at 2:14 PM, Tomaz Muraus  wrote:
> >
> > This is a voting thread for Libcloud 2.6.0. It includes all the
> > changes from trunk which have landed there since v2.5.0.
> >
> > It has been almost 3 months since the last release so a lot
> > of changes have accumulated in trunk since then.
> >
> > Full list of changes can be found at
> >
> https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-260
> >
> > Release artifacts can be found at
> > http://people.apache.org/~tomaz/libcloud/2.6.0/
> >
> > Please test the release and post your votes.
> >
> > +/- 1
> > [  ]  Release Apache Libcloud 2.6.0
> >
> > Vote will be open until August 28th, 2019 (or longer, if needed)
>
>

Re: [dev] [VOTE] Release Apache Libcloud 2.5.0

[Rick van de Loo]

[ +1]  Release Apache Libcloud 2.5.0

Op di 28 mei 2019 om 23:00 schreef Tomaz Muraus :

> This is a voting thread for Libcloud 2.5.0. It includes all the
> changes from trunk which have landed there since v2.4.0.
>
> It has been almost 8 months since the last release so a lot
> of changes have accumulated in trunk since then.
>
> Full list of changes can be found at
>
> https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-250
>
> Release artifacts can be found at
> http://people.apache.org/~tomaz/libcloud/2.5.0/
>
> Please test the release and post your votes.
>
> +/- 1
> [  ]  Release Apache Libcloud 2.5.0
>
> Vote will be open until May 30th, 2019 (or longer, if needed)
>

Re: [dev] [NOTICE] Mandatory migration of git repos to gitbox.apache.org - three weeks left!

[Rick van de Loo]

Hi Tomaz,

I'm not in the PMC but I do often push to the git-wip-us.apache.org
libcloud repo and I think this is fine. Will the workflow for merging pull
requests change to just merging to trunk on Github? Or will the current
workflow of locally merging and then pushing to the apache repo and let the
asfgit bot close the PR persist?

Greetings,
Rick van de Loo

Op di 15 jan. 2019 om 20:36 schreef Tomaz Muraus :

> Is everyone from the PMC team fine with that migration?
>
> I think it's good since it will give us full control over our GitHub
> project.
>
> Please confirm so I can start working on the migration with the ASF infra
> people.
>
> Thanks,
> Tomaz
>
> On Mon, Jan 14, 2019, 23:50 Apache Infrastructure Team <
> infrastruct...@apache.org wrote:
>
> > Hello, libcloud folks.
> > As stated earlier in 2018, and reiterated two weeks ago, all git
> > repositories must be migrated from the git-wip-us.apache.org URL to
> > gitbox.apache.org, as the old service is being decommissioned. Your
> > project is receiving this email because you still have repositories on
> > git-wip-us that needs to be migrated.
> >
> > The following repositories on git-wip-us belong to your project:
> >  - libcloud.git
> >
> >
> > We are now entering the remaining three weeks of the mandated
> > (coordinated) move stage of the roadmap, and you are asked to please
> > coordinate migration with the Apache Infrastructure Team before February
> > 7th. All repositories not migrated on February 7th will be mass migrated
> > without warning, and we'd appreciate it if we could work together to
> > avoid a big mess that day :-).
> >
> > As stated earlier, moving to gitbox means you will get full write access
> > on GitHub as well, and be able to close/merge pull requests and much
> > more. The move is mandatory for all Apache projects using git.
> >
> > To have your repositories moved, please follow these steps:
> >
> > - Ensure consensus on the move (a link to a lists.apache.org thread will
> >   suffice for us as evidence).
> > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> >
> > Your migration should only take a few minutes. If you wish to migrate
> > at a specific time of day or date, please do let us know in the ticket,
> > otherwise we will migrate at the earliest convenient time.
> >
> > There will be redirects in place from git-wip to gitbox, so requests
> > using the old remote origins should still work (however we encourage
> > people to update their remotes once migration has completed).
> >
> > As always, we appreciate your understanding and patience as we move
> > things around and work to provide better services and features for
> > the Apache Family.
> >
> > Should you wish to contact us with feedback or questions, please do so
> > at: us...@infra.apache.org.
> >
> >
> > With regards,
> > Apache Infrastructure
> >
> >
>

[dev] question regarding ICLA and GITHUB-1242

[Rick van de Loo]

Hi,

I would like to merge this PR https://github.com/apache/libcloud/pull/1242
(Implement new versions of OpenStack API calls [LIBCLOUD-874] #1242) but
because this is a larger PR I'm wondering if the author is required to sign
the ICLA (http://www.apache.org/licenses/#clas) before I'm allowed to?

https://libcloud.readthedocs.io/en/latest/development.html#contributing-bigger-changes

Greetings,
Rick van de Loo

Re: [dev] [VOTE] Release Apache Libcloud 2.3.0

[Rick van de Loo]

[+1] Release Apache Libcloud 2.4.0

Op za 27 okt. 2018 om 09:44 schreef anthony shaw :

> I went through the checklist. All looks good
>
> [+1] Release Apache Libcloud 2.4.0
>
> On Sat, 27 Oct 2018 at 6:04 pm, Quentin Pradet 
> wrote:
>
> > This is a voting thread for Libcloud 2.4.0. It includes all the
> > changes from trunk which have landed there since v2.3.0.
> >
> > The most notable change is Python 3.7 support. There is also a new
> > Scaleway driver, and various improvements, mostly for compute drivers.
> >
> > Full list of changes can be found at
> >
> >
> https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-apache-libcloud-240
> >
> > Release artifacts can be found at
> > http://people.apache.org/~quentinp/libcloud/2.4.0/
> >
> > Not sure how to send my GPG key!
> >
> > Please test the release and post your votes.
> >
> > +/- 1
> > [  ]  Release Apache Libcloud 2.4.0
> >
> > Vote will be open until November 2nd.
> >
>

Re: [dev] New Libcloud release

[Rick van de Loo]

Hi,

Good idea, we've been using the current trunk in production for a while now
and everything (that we use) seems to be working fine and we haven't
encountered any bugs. I'll be away on vacation starting tomorrow so it will
be a while before I can get around to this. Quentin if you have time before
then and you want to do it then that would be great as well, otherwise I'll
do an attempt when I get back.

Greetings,
Rick van de Loo

Op ma 3 sep. 2018 om 16:46 schreef Tomaz Muraus :

> It has been quite a while since the last Libcloud release.
>
> It looks like quite some changes have accumulated in master since then so
> it would be good to release a new version soon.
>
> Quentin, Rick, does one of you want to take a stab at a new release (
>
> https://libcloud.readthedocs.io/en/latest/committer_guide.html#making-a-release-for-release-managers
> )?
>
> I'm happy to help, if needed.
>

Re: [dev] [VOTE] Release Apache Libcloud 2.3.0 [2nd vote]

[Rick van de Loo]

[+1] Release Apache Libcloud 2.3.0


2018-03-02 11:00 GMT+01:00 Allard Hoeve :

> [+1] Release Apache Libcloud 2.3.0
>
> Op vr 2 mrt. 2018 09:51 schreef anthony shaw :
>
> > More votes please everyone.
> >
> >
> >
> > On Tue, 27 Feb 2018 at 4:27 pm, Quentin Pradet  >
> > wrote:
> >
> > > Thanks! The md5 and sha1 now match.
> > >
> > > [+1]  Release Apache Libcloud 2.3.0
> > >
> >
>