All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Asselstine <mark.asselstine@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
	Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Cc: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>
Subject: Re: [meta-cloud-services] [PATCH] python-heatclient: 0.6.0 -> 1.7.0
Date: Mon, 23 Jan 2017 21:33:07 -0500	[thread overview]
Message-ID: <CAPuovEJ0d8suNiX938m7ZUJWk5qPyi9cz0n_H2nG0g0n4NPvNQ@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4MgUjaG6jRzTu=qSH5VTviQh4m37D=rZ15o9gbTp5Ar+g@mail.gmail.com>

On Mon, Jan 23, 2017 at 1:24 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
>
>
> On Mon, Jan 23, 2017 at 9:01 AM, Mark Asselstine
> <mark.asselstine@windriver.com> wrote:
>>
>> On Mon, Jan 23, 2017 at 4:02 AM, Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
>> wrote:
>> > Upgrade python-heatclient from 0.6.0 to 1.7.0.
>> >
>> > Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
>> > ---
>>
>> Huang, we need to ensure we stick to releases witch match
>> stable/newton and not go beyond. So for this package we should be
>> using the latest commit on the stable/newton branch and the version
>> will be 1.5.0+git${SRCPV}. The other uprev's look fine, although as we
>> proceed through the newton update we might find incompatibilities
>> which might result in some tweaking.
>
>
> Agreed. I'm happy to take uprevs of the python support packages, but for
> anything that is a core project, or interfaces directly with those core
> projects,
> I'd rather batch merge their updates .. once we've shown a fully working
> system.

+1. Now that we have made our way through most of the dependencies and
python-oslo* uprev work I am starting to queue the updates to the core
openstack recipes. Huang, you are most likely best to wait until I
have these complete, there is no need to duplicate this work. Once I
have a somewhat functional system I will get these out for review and
merging.

Mark

>
> Bruce
>
>>
>>
>> Just out of curiosity, what are your end goals for these
>> contributions? do you have a usecase for this repo that I can keep in
>> mind as I move things forward?
>>
>> Mark
>>
>>
>> >  meta-openstack/recipes-devtools/python/python-heatclient_git.bb | 4
>> > ++--
>> >  1 file changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git
>> > a/meta-openstack/recipes-devtools/python/python-heatclient_git.bb
>> > b/meta-openstack/recipes-devtools/python/python-heatclient_git.bb
>> > index 26d86be..711a36d 100644
>> > --- a/meta-openstack/recipes-devtools/python/python-heatclient_git.bb
>> > +++ b/meta-openstack/recipes-devtools/python/python-heatclient_git.bb
>> > @@ -28,8 +28,8 @@ SRCNAME = "heatclient"
>> >
>> >  SRC_URI =
>> > "git://github.com/openstack/python-heatclient.git;branch=master"
>> >
>> > -PV = "0.6.0+git${SRCPV}"
>> > -SRCREV = "7cca8394b8ab2f4dccb982ae789b1b2985627115"
>> > +PV = "1.7.0+git${SRCPV}"
>> > +SRCREV = "17dd3068e4d6fc10236290cc082908c439bcfead"
>> >  S = "${WORKDIR}/git"
>> >
>> >  inherit setuptools
>> > --
>> > 2.7.4
>> >
>> >
>> >
>> > --
>> > _______________________________________________
>> > meta-virtualization mailing list
>> > meta-virtualization@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/meta-virtualization
>> --
>> _______________________________________________
>> meta-virtualization mailing list
>> meta-virtualization@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee at
> its end"
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>


  reply	other threads:[~2017-01-24  2:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23  9:02 [meta-cloud-services] [PATCH] python-heatclient: 0.6.0 -> 1.7.0 Huang Qiyu
2017-01-23 14:01 ` Mark Asselstine
2017-01-23 18:24   ` Bruce Ashfield
2017-01-24  2:33     ` Mark Asselstine [this message]
2017-01-31 16:06       ` Mark Asselstine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPuovEJ0d8suNiX938m7ZUJWk5qPyi9cz0n_H2nG0g0n4NPvNQ@mail.gmail.com \
    --to=mark.asselstine@windriver.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=huangqy.fnst@cn.fujitsu.com \
    --cc=meta-virtualization@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.