Open Stack

Hi Alfredo,

On Thu, 2 Feb 2023 at 23:44, Alfredo Moralejo Alonso
<amoralej at redhat.com> wrote:
>
> Hi,
>
>
> On Thu, Feb 2, 2023 at 12:18 PM Sean Mooney <smooney at redhat.com> wrote:
>
> Yes, there is that automation and that fixes most of the cases for minimal required versions, as when the change in the requirements.txt is merged, the version is already in RDO. This process has some corner cases and dependencies which delays the updates in some cases as it happened in this particular case. Said this, there are different levels of validation in RDO which catch those cases (as it happened this time).
>
>>
>> im sure similar automation could be done for the requirements
>> file if there is a min version bump.
>
>
> Yes, actually there may be several approaches to implement this such as triggering third party jobs to check changes in requirements.txt or enabling automatic package requirements generation from requirements.txt. Each one has its own problems and require to manage different types of exceptions. Anyway, it's something we are still investigating. The fact that we try to follow upper-constraints as close as possible fixes many (not all) of the cases related to changes in requirements.txt so we didn't implement automation on requirements.txt yet.

If you decide you want to do that I'd be interested in helping.

> Yes. Note that some upstream neutron developers are also maintainers of the neutron packages in RDO, which may have been misleading about the  destination for this message but you are right, this is up to RDO (core and package maintainers), not upstream neutron.

Ah yes, that does indeed clarify some of my misunderstanding.

Yours Tony.