[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[infra][releases][requirements] Publishing per branch constraints files

Tony Breeds <tony at bakeyournoodle.com> writes:

> Hi all,
>     Back in the dim dark (around Sept 2017) we discussed the idea of
> publishing the constraints files statically (instead of via gitweb)[1].
> the TL;DR: it's nice to be able to use
> https://release.openstack.org/constraints/upper/ocata instead of
> http://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/ocata in tox.ini
> At the Dublin (yes Dublin) PTG Jim, Jeremy, Clark and I discussed how
> we'd go about doing that.
> The notes we have are at:
> https://etherpad.openstack.org/p/publish-upper-constraints
> There was a reasonable ammount of discussion about merging and root-markers
> which I don't recall and only barely understood at the time.
> I have no idea how much of the first 3 items I can do vs calling on others.
> I'm happy to do anything that I can ... is it reasonable to get this
> done before RC1 (March 18th ish)[2]?
> Yours Tony.
> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-September/122333.html
> [2] https://releases.openstack.org/stein/schedule.html#s-rc1

Could we do it with redirects, instead of publishing copies of files?