From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6659262894210809856 X-Received: by 2002:a17:906:9701:: with SMTP id k1mr1671393ejx.13.1550483898527; Mon, 18 Feb 2019 01:58:18 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:3645:: with SMTP id r5ls2428596ejb.4.gmail; Mon, 18 Feb 2019 01:58:18 -0800 (PST) X-Google-Smtp-Source: AHgI3IbJ+xsG1eKnIXvnsiJG4z9RsXluU8cFIZVOgiZxhAmk5F8adWEyaBaQML2DZcRHh4IdilE9 X-Received: by 2002:a17:906:34c3:: with SMTP id h3mr2307734ejb.3.1550483898133; Mon, 18 Feb 2019 01:58:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550483898; cv=none; d=google.com; s=arc-20160816; b=Sf81ShNlrtswGMwlkATAAcEETmu8C8ZEu9ulKqZF6zI5sYVzpAw7IwBtWJZjqhCUwX wWnzEcT8BhDIlA7xjHBGNOOUwZkyJBGW6VEOAPsghlip0JqUDNEIfWr+80PVn+XH2c2p yHTRZsDenpSZV1zovxiCp8nr+MdpW5SWckXabTk2ve0Y+G6EBZwDmNlvPCq7Rn2Himwo GZFwADLuO9whBYVkEsdUG7pmPocAipIhREoccPTHAZPNpgDyQbFQtADvmy6ZpO/yA5wA 63zQiVwu1A/bFDDbmRPd8edYAzUkrhz0JRD6VeH4OegrJJylDYYf0qndTq3uqqfz/XAb OJLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=d6VsNNduo2pNX5C07BsWGMGOLs85RE01wz8QSE0wZR0=; b=NRQx7lqnSoK3XvneHma+HUb6fz7ZdxDheypiiKrbo9cNqfkK8BJ13TNhIyEbK5UKKo W+rfaZOPrI4So7Yi6XxQ7azTzVEgNzTeSg7CHGfF1XA8lJopqotgOpt8cJuA/DOPnykG zAG3UBBLHVFD9OMsBi/5zhuckYdGIlrEH5X82OIvm6Mb5btTx1LQ/eO028hIe8qvWrM2 Gvblii/4gUQRmCJzdQ96nzzovRZ5qaMYDxdjlJHv7g3QsF6l29Tgygum4BmX8cc3Ypl7 FLWLVTa43jD8nEZ0yCMQeuvmMT/zZ+vscxOLZtj/fKFrHud7gRQgMQnTmwLzsJTy7qgi mBJA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id c7si289248ejx.1.2019.02.18.01.58.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Feb 2019 01:58:18 -0800 (PST) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x1I9wHgx031930 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 18 Feb 2019 10:58:17 +0100 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x1I9wGaB028916; Mon, 18 Feb 2019 10:58:16 +0100 Subject: Re: [ANNOUNCE] Upcoming ISAR release To: "Maxim Yu. Osipov" , isar-users References: From: Claudius Heine Message-ID: <96e3ec90-3a4d-dcb0-1645-725d5d7d7094@siemens.com> Date: Mon, 18 Feb 2019 10:58:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: XrJ5HDhUTWMu Hi Maxim, On 18/02/2019 10.01, Maxim Yu. Osipov wrote: > Hello everybody, > > Last release (v0.6) was made on 1st of October 2018. > > We plan to release the next version of ISAR on 1st of March, 2019. > > BTW, what do you think about making a 1.0 release? IMO we need a lot more cleanup stuff before we can do a solid 1.0 release. We should make a list of issues that should be done before 1.0 release. Here is a suggested checklist before 1.0: - Remove jessie support - Improve documentation - Cleanup the user interface variables - Consistent variable nameing style - Use feature variables instead of many VAR="1" ones. They can be more easily bundled together in code and docs. - Consistent and clear naming of things - Build, host, target in line with GCC and Debian definition - meta, meta-isar -> either meta and meta-example or meta-isar and meta-isar-example. Currently 'meta-isar' sounds like it is required. - Clearly defined task pipeline for all recipe types - no more do_build with stuff in it, that should be treated a the default target not some real one - dpkg_runbuild should be a task with postfunc and prefunc attributes to wrap mounts around it - Cleanup meta-isar layer to show best practices of using isar - multiconfig should not contain other variables than DISTRO and MACHINE I am sure I will find a lot more of those if I think a bit harder about it. All of those issues makes adopting Isar for new, OE or Debian people alike very difficult. With the 1.0 we should try to bring Isar to a level were we don't expect many breaking changes on the next 1.1 release. > At the moment I'm busy with testing/applying pending patches, I plan to > finish this activity in a couple of days and make a first release > candidate and code freeze (only bug fixes will be applied in the 'next') > after that. Shouldn't we open a release staging branch for that, so that feature submissions can continue to next? Cheers, Claudius > I'll submit later Changelog describing major changes since the last > release and sort out the issues present on the project's wiki. > > Please inform me about any open issues that may be a subject to postpone > a release. -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de