Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of jason.dillon@gmail.com
 designates 64.233.184.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=mp0AjB02Al8ODwlp8/gDOw5pMVBh7XW0MRF30gdstrn/Hdhk8fgdBblWLeldYyYyeoRQl8OxZoC+VgT0lS77RvCKgKu/myC7vX2V98ZlcHJyhclY7SPgUM1H5AdEECFwsr8OIsaNSGijtUMPLWklj2QsCN77tSCzfPHbsV0pO0k=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <838ADB20-30CE-4956-9433-06DF6F27CA37@iq80.com>
References: <A330200B-12DC-41AF-A5BA-70A5FF45376E@gmail.com>
 <21df75940612111052h49fc37cem961ef3e65f14ba63@mail.gmail.com>
 <B0543621-6915-449B-B432-C7E940D6CAAC@iq80.com>
 <4F6F4A5E-2BCE-405B-98E6-B94A81D519CC@planet57.com>
 <838ADB20-30CE-4956-9433-06DF6F27CA37@iq80.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <954CDE20-C5FF-46D3-A2E0-A0FEFCB76A04@planet57.com>
Content-Transfer-Encoding: 7bit
From: Jason Dillon <jason@planet57.com>
Subject: Re: [DISCUSS] specs versioning
Date: Mon, 11 Dec 2006 14:08:07 -0800
To: dev@geronimo.apache.org
Sender: Jason Dillon <jason.dillon@gmail.com>

On Dec 11, 2006, at 1:53 PM, Dain Sundstrom wrote:
>>> Um.. that's not true.  Maven has full support for this.  Also it  
>>> doesn't make the release manager's job harder.
>>
>> Sure it does Dain, running one set of `mvn release:prepare && mvn  
>> release:perform` vs, running one per spec module.  That is  
>> significantly more work for the latter.
>
> You are implying that we tend to release gobs of specs at one.  The  
> reality is specs rarely change and when we do find a problem it is  
> with one module not everything.

In several cases, you must release more than one spec at a time.  But  
my point was more general... as in general its easier to manage  
releases for a set of modules together instead of one by one.


>> Also, if you consider hooking up this process to a build  
>> automation tool, so that each build gets released by that tool,  
>> then the specs project effectively needs to get split up into a  
>> project per-module, which is a bunch of unneeded overhead.
>
> Only the specs being worked on would need build automation, and  
> event then I would suggest G never uses SNAPSHOT specs.  Instead  
> when the specs are mostly complete we release a M1 and when they  
> are finished we release 1.0.  In that case no automation is necessary.

It is still much easier to just setup one project for all of the  
specs rather than add/remove projects as needed.

  * * *

If you folks really want to version spec modules independently, then  
I suggest you also consider versioning server modules independently.

I certainly don't recommend doing either, but IMO they are both the  
same problem from a build perspective, just with slightly different  
context.

--jason