[Libosinfo] [osinfo-db][PATCH] opensuse-unknown: Adjust the volume-id regex

[Fabiano Fidêncio]

On Thu, May 31, 2018 at 2:23 PM, Christophe Fergeau <cfergeau at redhat.com> wrote:
> On Thu, May 31, 2018 at 11:57:51AM +0200, Fabiano Fidêncio wrote:
>> On Thu, May 31, 2018 at 10:54 AM, Christophe Fergeau
>> <cfergeau at redhat.com> wrote:
>> > On Sat, May 26, 2018 at 10:29:43PM +0200, Fabiano Fidêncio wrote:
>> >> The regex to match unknown openSUSE prereleases is becoming
>> >> bigger and harder to read.
>> >>
>> >> Basically, what it's doing is:
>> >>
>> >> (15\.[1-9]|(1[6-9]|[23]|[5-9])[0-9]\.[0-9]|4[3-9]\.[0-9])
>> >> ---------   -----  ----------------   ---- -------------
>> >>     |         |         |                |       |
>> >>     v         v         v                |       v
>> >>   15.1+      16     20, 30, 50 - 90      v     43.0+
>> >>                                   .0, .1, ..., .9
>> >>
>> >> I'm desconsidering both the 13.x series or older and 42.x series as
>> >> those are not going to have new releases anymore.
>> >
>> > "desconsidering"? Dropping?
>>
>> I'll change it to "Dropping" before pushing.
>>
>> > Note that
>> > https://en.opensuse.org/openSUSE:Roadmap does not entirely closes the
>> > door on another 42.x release "There are currently no plans to release an
>> > openSUSE Leap 42.4 aligned with the next service pack of SLE 12", but
>> > that's close enough.
>> > Are they really going to release 43.x in parallel to/after 15.x?
>>
>> No, they have no intention to release 43.x. I've talked to Richard
>> Brown about this during openSUSE conference last weekend and
>> explanation he gave me is that they're moving back to a number that
>> would match SLES.
>> The whole 42.x series was in order to totally distinguish between the
>> old base they had with the new shiny system that Leap was supposed to
>> be.
>>
>> So, they're now following 15.x ... if at some point SLES will have a
>> 16.x opensuse 16.x will come to the playground as well.
>
> Your regexp in the commit log and in your patch has a 43.x part, so this
> can be dropped.

I see where the confusion came from.
So, if you don't mind I'd prefer to keep it there because the regex is
keep everything:
15.1+, 16-41,  NOT 42, 43-99

>
> Christophe

If you have some strong feelings about this, then I'll drop it.

-- 
Fabiano Fidêncio