I'm a newcomer to this list, so treat my opinion with suspicion... I think that there's a governance policy involved. I don't think that the committers should feel obligated to support something that is not in their interest. OpenSUSE verification needs a champion, and if that champion does not emerge than I'd think that the only rational thing to do is to drop it.
FreeBSD, for example, has a policy of tiers (see https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html) for platform support. Such a system allows for new platforms to get incorporated, but makes it clear how they relate to project and responsibilities. Things that exhibit developer support move up the tiers to where they are formally fully supported by the project. Platforms that fail to maintain developer support move down the tiers to their eventual demise. Perhaps a similar policy would work here. dave c On Thu, Dec 14, 2017 at 6:04 AM, Damjan Marion (damarion) < damar...@cisco.com> wrote: > > Folks, > > I'm hearing from multiple people that OpenSUSE verify job is failing > (again). > > So generally speaking i would like to question having verify jobs for > multiple distros. > Is there really a value in compiling same code on different distros. Yes I > know gcc version can be different, > but that can be addressed in simpler way, if it needs to be addressed at > all. > > More distros means more moving parts and bigger chance that something will > fail. > Also it cost resources.... > > Thoughts? > > Damjan > > > > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev > -- Kailua, Hawaiʻi US +1 (808) 728-3050 UK +44 (020) 3286 2808
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
