Sean K <sean.k.moo...@intel.com> wrote:
-----Original Message-----
From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com]
Sent: Thursday, September 1, 2016 8:03 PM
To: Ihar Hrachyshka <ihrac...@redhat.com>; Armando M.
<arma...@gmail.com>; Cathy Zhang <cathy.h.zh...@huawei.com>
Cc: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Neutron][networking-sfc] need help on
requesting release for networking-sfc
Thanks for all your response.
We would like to have the stable branch pulled from a git commit.
Shall we use the git hash of that commit for the intended git hash in
the release request?
I am confused about the following statement in the release guide.
"You need to be careful when picking a git commit to base new releases
on. In most cases, you’ll want to tag the merge commit that merges your
last commit in to the branch. This bug shows an instance where this
mistake was caught. Notice the difference between the incorrect commit
and the correct one which is the merge commit. git log 6191994..22dd683
--oneline shows that the first one misses a handful of important
commits that the second one catches. This is the nature of merging to
master."
What is meant by " tag the merge commit"? How do we tag a git commit on
our master branch?
[Mooney, Sean K] cathy if networking-sfc is setup the way I setup
networking-ovs-dpdk
e.g. following the old infra new projects guide the Core team has the
right to push signed tags.
In this case you would checkout the commit you want To tag.
Then you would tag it with "git tag -s x.y.z" I think its -s to sign the
tag but its been a
While since I did it last then you do "git push --tags gerrit" to push
the tag to the repo.
Becareful to include at least 3 section in the version for it to be a
valid tag for pypi packaging.
Only members of neutron-release are able to push tags for stadium
subprojects.
That said I don’t know if you have to tag the repo manually if you are
using the openstack/release repo.
Yes, initially the release request is just an indication that the team is
ready to release. A neutron-release member will check the proposed commit
to be one of merging commits, if such a commit is present, then push the
tag as you specified above, then +1 the release request in gerrit to
indicate to release folks that neutron side is ready, and they can proceed
with landing the patch that will trigger email notifications about the
release and other relevant release tasks.
Thanks,
Cathy
-----Original Message-----
From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
Sent: Thursday, September 01, 2016 4:22 AM
To: Armando M.
Cc: Cathy Zhang; OpenStack Development Mailing List (not for usage
questions)
Subject: Re: [openstack-dev] [Neutron][networking-sfc] need help on
requesting release for networking-sfc
Armando M. <arma...@gmail.com> wrote:
On 31 August 2016 at 17:31, Cathy Zhang <cathy.h.zh...@huawei.com>
wrote:
CC OpenStack alias.
From: Cathy Zhang
Sent: Wednesday, August 31, 2016 5:19 PM
To: Armando Migliaccio; Ihar Hrachyshka; Cathy Zhang
Subject: need help on requesting release for networking-sfc
Hi Armando/Ihar,
I would like to submit a request for a networking-sfc release. I did
this for previous branch release by submitting a bug request in
launchpad before. I see that other subproject, such as L2GW, did this
in Launchpad for mitaka release too.
But the Neutron stadium link
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidel
ines.html#sub-project-release-process
states that “A sub-project owner proposes a patch to
openstack/releases repository with the intended git hash. The Neutron
release liaison should be added in Gerrit to the list of reviewers
for the patch”.
Could you advise which way I should go or should I do both?
Consider the developer documentation the most up to date process, so
please go ahead with a patch against the openstack/releases repo.
Right. There was a recent change to the process that streamlined
release requests and hopefully made them a tad easier for both
subproject owners as well as release liaison. Please stick to the
latest version of the process as described in devref in master branch
of neutron repo.
Ihar
_______________________________________________________________________
___
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-
requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
