From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6656722054226640896 X-Received: by 2002:a1c:147:: with SMTP id 68mr216525wmb.21.1549971562452; Tue, 12 Feb 2019 03:39:22 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:ce0a:: with SMTP id e10ls339153wmg.1.canary-gmail; Tue, 12 Feb 2019 03:39:21 -0800 (PST) X-Google-Smtp-Source: AHgI3IZLoRh/Rp6TUx9p9TBoZozkxuhABpDC+JyLSbixAdYsmuYhWokjBb+mxUh15hK50WhyBito X-Received: by 2002:a05:600c:2110:: with SMTP id u16mr253821wml.11.1549971561384; Tue, 12 Feb 2019 03:39:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549971561; cv=none; d=google.com; s=arc-20160816; b=nb1ohrTJlTacz4IJYmBKMvX+Y5V0MZV/wJlkWGmYNsEYuav1BvuasCsULgMIGVuWXU FRxkShruVM9kdg2DFFb4HPa0g9VYe3njh/K0/SCyAGtfGb9j0tjFvdFWKlIgxhTLiEtm 8pbHE8Wkq1KLO94Tci/UHoKHxqWpObfSJCNECpcDXmyK4cRXB1fNfOSqn0kPe2m2Jl3B hLT1pbr1S2nB80vj99Zs6vrwGNCtPEzyagA0eC/sf5K8fzQmn2/nppE00USgJcmfCKi1 vPSY+jv7ZIVvIlfmEl6iM69rL1642lx178UBa89ejxk5xilGKw1s1LwkZmm+y1q49TAn JfAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=jfvtpgCpUfP2GnFn37fLzaoVaZpYGpcyKcVRzhcRzws=; b=MAtk2FwPvSRIMRMLizSqDHI2+ooca3NBk0YaC18XLDoB6WpB/kdpt/YvRubaViHGqh rnM7I8rQ6HCovjgVWHmoKy4+OL5Qr4xXsHiYEp5b6hiSs513+6HbggMpKB1GVzn+pgQJ OCmNqbRB8AvLogeR3dQEcPDtNetgXeTJKozLFwWuJkAbjkQhnWYNAluxJ9uZp2344nEv bZbbvd/hy57s4GtV+ohPCE7jUDmEhpG6YNOth5w/dJQjgQn8BfkQbZ/H5Zn72cnUdnNt gz+AkrlxlzimnFLD/GP0mau7fgcgZj9OL6UcKGIM4nbEQ1QxXqN2qOjAPgo5L9RR4APp BHxg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id y200si146902wmd.0.2019.02.12.03.39.21 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 12 Feb 2019 03:39:21 -0800 (PST) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x1CBdJ5b014856 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 12 Feb 2019 12:39:20 +0100 Date: Tue, 12 Feb 2019 12:39:19 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH v2] remove RaspberryPi support Message-ID: <20190212113919.GI805@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <20190212093036.23464-1-claudius.heine.ext@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190212093036.23464-1-claudius.heine.ext@siemens.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: OjgqS45GLBrv On Tue, Feb 12, 2019 at 10:30:36AM +0100, claudius.heine.ext@siemens.com wrote: > RaspberryPi is removed from meta-isar, because > - there currently no maintainers for it > - there is no automated boot test for it > - forces burden on rest of isar to support jessie > - very old board, most users should have moved on to RPi 2 or 3 > > If those points change, support for it can be readded. - There is a maintaner (the process has to be improved) - Testing doesn't have to be automated (automation desired mid- to long-term) - There is value in supporting old boards as long as it is reasonable - I think we should strive for evolution and not discrete add-remove jumps The burden issue demonstrates one of the fundamental ideas behind Isar. After some time, people end up building for different suites. Many people who release stretch today will build for stretch and buster tomorrow. Maybe now is the time to make pluggable mechanisms for different suites. Without satisfying that need, Isar won't be serving people in the long run, IMHO. Regarding rpi1, I'd be reluctant to remove without understanding what went wrong first. Moving to stretch shouldn't be a problem, but the issue of elegantly supporting different suites remains nonetheless. With kind regards, Baurzhan.