Open Stack

Hi Tony and all,

Sorry for the delay to reply. 

We are planning to create the stable/pike branch soon. I am contacting the PTL Sampath Priyankara(samP) for the exact date.

Thanks and Regards,
Dinesh Bhor | App. Software Dev. Cnslt.
dinesh.bhor at nttdata.com | nttdata.com/americas


-----Original Message-----
From: Tony Breeds [mailto:tony at bakeyournoodle.com] 
Sent: Wednesday, August 09, 2017 5:25 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

On Wed, Aug 09, 2017 at 06:39:52AM +0000, Bhor, Dinesh wrote:
> Hello everyone,
> 
> I would like to ask for the FFE for adding "python-masakariclient" in global-requirements.
> 
> Earlier, we were not having "check-requirements" job for masakari-* projects. At that time, we use to manually add "python-masakariclient" as a requirement in masakari-monitors project [1].
> Now we have added "check-requirements" job for masakari-* projects, 
> but we missed to add "python-masakariclient" in global-requirements and now the bigger issue is it is not possible to manually update the "python-masakariclient" requirement in masakari-monitors project as the "gate-masakari-monitors-requirements" requirements job keeps failing on the patch [1].
> To resolve this problem permanently, we need to add "python-masakariclient" library requirement in global-requirements.
> I have submitted a patch [2] for adding the python-masakariclient in global-requirements.
> 
> Please consider my request and grant FFE to solve this problem.
> 
> [1] https://review.openstack.org/#/c/457491/
> [2] https://review.openstack.org/#/c/491692/

Are you intending to create a stable/pike branch and perform releases from it?  Looking at masakari-monitors the whole history can be seen on one page so it's clearly very new.

Yours Tony.

______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.