Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 68660 invoked from network); 21 Sep 2009 08:24:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Sep 2009 08:24:29 -0000 Received: (qmail 84172 invoked by uid 500); 21 Sep 2009 08:24:28 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 84078 invoked by uid 500); 21 Sep 2009 08:24:28 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 84068 invoked by uid 99); 21 Sep 2009 08:24:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Sep 2009 08:24:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fmeschbe@gmail.com designates 72.14.220.153 as permitted sender) Received: from [72.14.220.153] (HELO fg-out-1718.google.com) (72.14.220.153) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Sep 2009 08:24:18 +0000 Received: by fg-out-1718.google.com with SMTP id e21so674766fga.10 for ; Mon, 21 Sep 2009 01:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=pGNG+5KfVVMlmHdB6xwdeTKJX3pZ1dxCGdjw0/rzo7A=; b=bCdrNP4J+cqENeciF+Dlm92e5RWyHSusqW7jDU76h3OVDpuOH9hcDVG3ykLOJjtmyx V68kEi1lKJEar3D0cczHqMgMZjQrYTs7jAC94QOCwaU7pT503x7FkPGhIGPFqDCejWg8 gyrENphr77qENYBqyGP0m7mEJgW0OYk2TxM1o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=PA+y55GiVs7HqeATq4yfEyqHBFhoCGtHvlIaqK8axt0kLllcMjZKuevK7xnv6Y+BXQ MIUGN2OPZXvnJCpvq4BoheFuYy4/OadepO486xwA6c9Z1Xc+G7152AkkZ2AXXjKNnYxx 1KYOTzGLAdgfz74QyEq09Hnw9YyT1Cc0L79k0= Received: by 10.86.231.5 with SMTP id d5mr4285790fgh.53.1253521436992; Mon, 21 Sep 2009 01:23:56 -0700 (PDT) Received: from ?10.0.0.51? (bsl-rtr.day.com [62.192.10.254]) by mx.google.com with ESMTPS id 12sm3701773fgg.10.2009.09.21.01.23.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 21 Sep 2009 01:23:54 -0700 (PDT) Message-ID: <4AB7381A.5040609@gmail.com> Date: Mon, 21 Sep 2009 10:23:54 +0200 From: Felix Meschberger User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: dev@felix.apache.org Subject: Re: HttpService progress (help)... References: <67831c590909151423t1eb066b3mb724c3278d5a9292@mail.gmail.com> <4AB088CA.9030000@gmail.com> <67831c590909160531k77596f6fma2385437fd532f05@mail.gmail.com> In-Reply-To: <67831c590909160531k77596f6fma2385437fd532f05@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Sten, Sorry for the delay ... Sten Roger Sandvik schrieb: > Great. I do not want to release individual bundles under http. Always t= he > same version number (atleast for now). Fine. > Another question: What about > documentation?=20 Yes, please ;-) > Would really like to include a Confluence entry on how to use > the new http bundles. Any structures I should follow? Except that we document below "subprojects" there is to my knowledge no written prescription.... You need a Confluence account to be able to edit documents (you can create one yourself). Please tell me your confluence account ID so that I can enable your account for editing our site. Regards Felix >=20 > On Wed, Sep 16, 2009 at 8:42 AM, Felix Meschberger = wrote: >=20 >> Hi Sten, >> >> My =E2=82=AC.02 below... >> >> Sten Roger Sandvik schrieb: >>> I have now done the first step by importing the new httpservice >>> implementation into svn. The logical step further is to work towards = a >> 2.0.0 >>> release. This involves fixing some known bugs and releasing some >>> intermediate snapshot versions so people can try it out. Have some >> questions >>> regarding the process: >>> >>> 1) Can I assign issues to a version in JIRA? Can anyone create a vers= ion >>> label "http-2.0.0" or someting? Is this the way you guys do it? >> I don't know whether you have permission to do so (so I just created >> it). I also added you to the felix-committers group which gives you >> committers permission on the JIRA FELIX project. >> >> Are you planning on releasing single http modules or always everything= >> together ? My personal opinion would be to have an initial http-2.0.0 >> release encompassing "everything" and then release modules as required= =2E >> >> WDYT ? >> >>> 2) Who drives the release of individual components? I can drive the >> "http" >>> dev-release process if that suites everybody. >> According to [1] every committer can be a release manager, which is th= e >> person driving the release. So if you think a release is due, you migh= t >> want to post a quick poll on the list and then just do it. >> >> You do this by following the release management guide at [2]. >> >>> 3) Any rules regarding when to do a release or snapshot releases of >>> individual components? >> None that I would know of. Snapshot releases are done as required with= >> no formal processes. But keep in mind SNAPSHOT "releases" are not >> releases in the understanding of Apache. >> >> Whether you release all http parts together or indivually is up to you= >> as the release manager. As said above, I propose to do an initial "ful= l >> release" and later release modules as required. >> >> >>> Would really like release a 2.0.0 version as soon as possible. Have s= ome >>> issues that I want to resolve (will put it into JIRA in the next days= ), >> but >>> the sooner the release the better. For me atleast :-) >> Having a first release soon, would definitely be a good thing. >> >> Regards >> Felix >> >> >> [1] >> http://incubator.apache.org/guides/releasemanagement.html#glossary-rel= ease-manager >> [2]http://felix.apache.org/site/release-management-nexus.html >> >> >=20