From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6459217651976634368 X-Received: by 10.25.87.84 with SMTP id l81mr60928lfb.1.1504022077454; Tue, 29 Aug 2017 08:54:37 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.64.146 with SMTP id r18ls247607lje.33.gmail; Tue, 29 Aug 2017 08:54:36 -0700 (PDT) X-Google-Smtp-Source: ADKCNb6oMNppVuBibXOqP964m3sZaO1uUBb71VarUsOKDxhe+5EDQ+3Ps1fNSo91xA75l96pWGEK X-Received: by 10.46.80.11 with SMTP id e11mr77951ljb.4.1504022076856; Tue, 29 Aug 2017 08:54:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1504022076; cv=none; d=google.com; s=arc-20160816; b=jMlJxFBEC4cgq/FIFrCLNb7QZ2zmPQhawfHh+Lqn9V/5EW7lsNtMe5I+FLTUudWO89 112przpZW6+yXkPG/o3PNV69qgTebFh0tpHxJf5ToF0HlNLctaGaiD1u/sJ0tlyIwAtZ Lqb2yS3LKKgQQNtBy7zq0c3TkQ0S01STshHH21BJi7lNfJBuCe3CbPuh8eKWp5ApuPrh vm6wFSOer5qHK1treoeNxFJGC7nWGruZVrdrCYl5scvQ6ygOGVM5gNONCUjn8PRqQYNc 1hPTqjJbt+1hhSI1Lrc6qi639vrLYlZ21QsYZnE5z7kRpJmgr/4rTieF/zrQtkpVq9w8 2vHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=ebeusqYLpMOf/l0doZ1yh9lWo39uICHuAc9/LlvnTxo=; b=jG5O3kwSu+l5lXWg9jDvWMirB2aRdsby7pGFb1IbbZL+8CbcbxbJxvxfS95+hSzwwP RlQGqAzYjfnqwub4I2M81+mXm6/ddSY0iFojmx+D9s/pARso9fd+SXF2sLocbKmf7D0V 8xf6kt1XwbTLOjG/AY4sP97AJt7otgQ2r0/T2IqA74WJJ6//zTXrutcp88FHGFq4xVBY KtIDBMc1pU88v2D6maOYInJb5wAT0vVaQCvkM27SXxcm0kgI8zAmenzRLN/WV5y8UEuM lCN4B3FXOa/ffuXHG3yCfiOgqsDpANAM0vNa/wzkBB+DnmeqHjZ5eJdEV5TS4nfgZ9p8 35BQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id h196si96033wmg.0.2017.08.29.08.54.36 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Aug 2017 08:54:36 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id v7TFsarO027088 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 29 Aug 2017 17:54:36 +0200 Received: from md1em3qc ([139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v7TFsa8S002082; Tue, 29 Aug 2017 17:54:36 +0200 Date: Tue, 29 Aug 2017 17:54:39 +0200 From: Henning Schild To: Alexander Smirnov Cc: Subject: Re: [PATCH] doc: Add maintainer process Message-ID: <20170829175439.2750b00c@md1em3qc> In-Reply-To: <20170828070254.15320-2-asmirnov@ilbers.de> References: <20170828070254.15320-1-asmirnov@ilbers.de> <20170828070254.15320-2-asmirnov@ilbers.de> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: KsBBwNEDaxTY Hey, in general it is nice to have that document. It describes processes we already have in place, but one essential point is missing. In the review process it seems like the maintainer is the only one that does reviews. It should be stated how the rest of the community can join that process. Henning Am Mon, 28 Aug 2017 10:02:54 +0300 schrieb Alexander Smirnov : > This patch adds basic maintainer process description, that has been > used so far since the project start. > > Signed-off-by: Alexander Smirnov > --- > doc/maintainer.md | 47 > +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 > insertions(+) create mode 100644 doc/maintainer.md > > diff --git a/doc/maintainer.md b/doc/maintainer.md > new file mode 100644 > index 0000000..ddaf39b > --- /dev/null > +++ b/doc/maintainer.md > @@ -0,0 +1,47 @@ > +# Introduction > + > +Isar maintainer is the person who keeps project development in > compliance +with contributing process definition. The purpose of this > document is to +describe the maintainer process in Isar project. > + > +# Responsibilities > + > +## Feedback on Contributions > + > +Isar maintainer should review each contribution that has been sent to The Isar maintainer > +mailing list and provide the feedback. Feedback could be on of the the mailing list and provide feedback Feeback could be out off the > +following categories: > + > + - Contribution accepted: If no quality and design issues were found. > + > + - Change request: If some small quality or design issues were > found, the > + maintainer requests next version with resolved issues. requests a new version > + - Contribution rejected: If there are major design issues or general > + benefit from the contribution is ambiguous. > + > +During the review, the maintainer may ask additional questions to > clarify +the details. > + > +## Repository Branches > + > +There are two official branches in Isar, intended to increase project > +quality: > + > + - next: The accepted contributions from mailing list are merged to > this from the mailing list > + branch. Basic CI checks should be run after each merge. This > branch > + could be forced. > > + - master: After passing full-cycle testing of next branch, it > should be > + merged to master. Master branch should contain stable releases > only, so > + all the features officially supported by current Isar version > (including > + features from previous releases) should be tested. I know what you want to say, how about? - master: Is the official stable branch. The only way patches go in here is coming from 'next', where they have passed all required tests and undergone the review process. On this branch force-pushing will never be used. > +The next branch is intended to be merged into master monthly. > Maintainer +could perform a merge to master before the ordinary The maintainer could > window if next branch +contains urgent patch series (bug fixes or if the next branch contains urgent patches > critical features). + > +## Issues at GitHub > + > +For each issue has been found in master and next branches the issue that has been found > maintainer +should create GitHub issue. create a GitHub issue.