Currently constraint redirectiones that point to EOL releases don't work
as expected due to gitea needed to differentiate between tags and
branches. Rather than fix, and rely on multiple redirects lets just
craft 301's that point to the correct gitea url.
This means we now need to know when a target is a branch or tag but
that's pretty simple to intuit given our deliverable structure.
Change-Id: Ife030f8ee7b5d204b054f99e920a675f7d92da69
The placement team decided that os-resource-classes should
follow an independent release cycle as it eases various
aspects of integration with the multiple projects that
consume the package and the fact that the package is simply
a big enumeration of symbols pointing to strings.
The expectation is that henceforth there will be a new release
each time there is one or more new symbols available.
Change-Id: I6349fe9eaa65fe871f3ed13c8b066115c9a035c3
kuryr-libnetwork is unlikely to produce multiple releases during
a cycle, so change the release model accordingly.
Change-Id: I08b13dac0ee34cee0456d4941a12054d71c81dbc
This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: I9d2394ee3a2cfcf065bf54a1bd1d600ce2ccdf43
This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: I1f39fbe2ea916bef45e5c696727825647015e5c7
This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: Ic9a59b7e09dbedc030ee7312f0a9498412538bcc
This is the overall feature freeze work, so listing per-project feature
freezes is just redundant.
Change-Id: Ia7efba8462b3209c2f0a944179bd98412c01a54b
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This is a procedural review to tag a final release for each
deliverables.
It's possible that the release isn't needed (for example if
there are no code changes sine the previous release, sadly
that's non-trivial to detect en masse).
If you are the PTL or release liaison for this team please +1
this review if it is ready or -1 and take over the review to
correct mistakes.
Change-Id: I0f1cf16c6bb0a62f29d7403a0914cdfa4aa16012
This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: Ia12fbe9479a7f2556f0d1e58868643acf84748b7
