On 2017-02-27 11:42:22 +0100 (+0100), Andreas Scheuring wrote:
> Thanks all for your feedback. Seeing things much clearer now.
>
> One last thing: How is the requirements bot being triggered?
>
> - For OpenStack libraries by the jenkins job that handles the tag
> (if the metadata is provided)?
Thanks all for your feedback. Seeing things much clearer now.
One last thing: How is the requirements bot being triggered?
- For OpenStack libraries by the jenkins job that handles the tag (if
the metadata is provided)?
- for external libraries? Is the a cronjob every 2 weeks or so? Or is it
On Fri, Feb 24, 2017 at 02:09:33PM +0100, Andreas Scheuring wrote:
> Hi, I have a couple of questions in regards of how updates of
> requirements are handled and what happens if I release a new version of
> a library. I read along the README [1], but a few points are still
> unclear to me.
>
> I
On 02/24/2017 07:09 AM, Andreas Scheuring wrote:
> Hi, I have a couple of questions in regards of how updates of
> requirements are handled and what happens if I release a new version of
> a library. I read along the README [1], but a few points are still
> unclear to me.
>
> I have the following
Excerpts from Andreas Scheuring's message of 2017-02-24 14:09:33 +0100:
> Hi, I have a couple of questions in regards of how updates of
> requirements are handled and what happens if I release a new version of
> a library. I read along the README [1], but a few points are still
> unclear to me.
>
Hi, I have a couple of questions in regards of how updates of
requirements are handled and what happens if I release a new version of
a library. I read along the README [1], but a few points are still
unclear to me.
I have the following projects:
* os-dpm [4]
* is a openstack library that gets
