From dev-return-28704-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Fri Feb 01 11:13:38 2008 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 70781 invoked from network); 1 Feb 2008 11:13:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Feb 2008 11:13:38 -0000 Received: (qmail 24026 invoked by uid 500); 1 Feb 2008 11:13:29 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 23973 invoked by uid 500); 1 Feb 2008 11:13:28 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 23962 invoked by uid 99); 1 Feb 2008 11:13:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2008 03:13:28 -0800 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [129.67.1.165] (HELO relay1.mail.ox.ac.uk) (129.67.1.165) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2008 11:12:59 +0000 Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay1.mail.ox.ac.uk with esmtp (Exim 4.68) (envelope-from ) id 1JKtpQ-0000QJ-5q for dev@forrest.apache.org; Fri, 01 Feb 2008 11:13:04 +0000 Received: from oucs-rossg.oucs.ox.ac.uk ([129.67.101.125]) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JKtpQ-0005S8-8e for dev@forrest.apache.org; Fri, 01 Feb 2008 11:13:04 +0000 Message-ID: <47A2FEA0.40404@apache.org> Date: Fri, 01 Feb 2008 11:12:32 +0000 From: Ross Gardler User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: How to merge FOP94-branch References: <47A0564A.4080305@apache.org> <47A074B6.1040104@apache.org> <20080131002550.GB2051@igg.indexgeo.com.au> <47A18A76.1090504@apache.org> <47A1BBC5.5060602@apache.org> <20080201023750.GF2051@igg.indexgeo.com.au> <47A2F2B9.7010009@apache.org> In-Reply-To: <47A2F2B9.7010009@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Oxford-Username: oucs0040 X-Virus-Checked: Checked by ClamAV on apache.org Ferdinand Soethe wrote: > David Crossley wrote: > >> Ross are you talking about "using" Forrest plugins? >> IIUC, Ferdinand is talking about developing the code >> in svn trunk. As far as i can see there can only be >> one version. > > David is right. Is it at all possible to have two separate versions of a > plugin in svn? And how would that work? Ah, sorry. Then the answer is only if you branch. >> Ferdinand i don't understand why we would want to maintain >> two separate versions. > > Good point. If the old plugin is still available for download and the > new plugin is marked so that is works with 0.8 there is really no reason > to still have the old code in svn. Exactly. It's just like we don't maintain forrest 0.7 in SVN (other than in a branch). > So what I'd do is: > > - publish the current state of the pdf-plugin if there are > changes > just checked: last change was April 10, 2007 thus before > the 0.8-release thus no need to republish +1 > - update the version number of the plugin, move the libs and > stylesheets and test this with fop94-branch > - when working test the new plugin with forrest 0.8 and > head +1 > - when working publish the plugin and remove fop-code in > from head. I assume you mean libs and stylesheets in core, in which case +1 You will also need to increment the version number of the plugin in SVN to 0.4-dev We have never fixed our plugin release plan. It should really go through a PMC vote (otherwise the release is not really approved by the ASF) and we should also tag the source tree. And the process should be documented. Ross