On Mon, Jul 11, 2016 at 03:02:45PM -0400, Doug Hellmann wrote:
> Yes, I think updating that branching script is the best course.
>
> We might want to modify the tox.ini to make it easier to edit with
> sed by defining a variable for the branch. It would be nice if we
> could just read the value f
Excerpts from Sachi King's message of 2016-06-30 14:24:45 +1000:
> On Tue, Jun 28, 2016 at 9:38 AM, Tony Breeds wrote:
> > On Mon, Jun 27, 2016 at 11:28:47PM +, Jeremy Stanley wrote:
> >
> >> I want to say there was a reason we were branching the requirements
> >> repo last, but now I can't re
On Tue, Jun 28, 2016 at 9:38 AM, Tony Breeds wrote:
> On Mon, Jun 27, 2016 at 11:28:47PM +, Jeremy Stanley wrote:
>
>> I want to say there was a reason we were branching the requirements
>> repo last, but now I can't remember what it is (or if we even did
>> branch it last). Thierry or Doug li
On Mon, Jun 27, 2016 at 11:28:47PM +, Jeremy Stanley wrote:
> I want to say there was a reason we were branching the requirements
> repo last, but now I can't remember what it is (or if we even did
> branch it last). Thierry or Doug likely recall but are indisposed
> this week so I suggest wai
On 2016-06-28 09:00:06 +1000 (+1000), Tony Breeds wrote:
[...]
> Or make the first repo process openstack/requirements ; sleep long enough for
> any mirroring to occur and then process the rest?
[...]
I want to say there was a reason we were branching the requirements
repo last, but now I can't re
On Mon, Jun 27, 2016 at 05:14:23PM +, Jeremy Stanley wrote:
> On 2016-06-27 15:27:47 +1000 (+1000), Tony Breeds wrote:
> [...]
> > Can't we extend the tools[1] that do that step with the updating
> > of tox.ini?
>
> The risk there is that you're breaking that new stable branch for
> developers
On 2016-06-27 15:27:47 +1000 (+1000), Tony Breeds wrote:
[...]
> Can't we extend the tools[1] that do that step with the updating
> of tox.ini?
The risk there is that you're breaking that new stable branch for
developers until a similarly-named branch is created for the
openstack/requirements repo
On Mon, Jun 27, 2016 at 03:08:18PM +1000, Sachi King wrote:
> To facilitate upper-constraints on developer systems we have a
> hard-coded URL in projects tox.ini. This URL needs to change when
> after the openstack/requirements repo has created a branch for the
> stable release.
>
> This is in re
To facilitate upper-constraints on developer systems we have a
hard-coded URL in projects tox.ini. This URL needs to change when
after the openstack/requirements repo has created a branch for the
stable release.
This is in reference to [0]. There was some mention of possibly
adding this to stabl
