Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (herse.apache.org: domain of jmitchtx@gmail.com designates
 66.249.82.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
        b=bCHQrOD083Fl+9ZdfpTQ56JCFtlzQRHnKpitCVaimfGzELFesHyt53YxOtgPdf8tUUyW9pe2vLPUZVG3kxDAeH5Qec0GMCIJHnAIxhvLQhWjM/X4uCdqmuhycq+nHfWTmZzHecTa/ZynPp8wWUBx5EzmsPzs+thcY/kxs2F36SI=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <8b3ce3790704230504qe73aae2n8997df691bc3066d@mail.gmail.com>
References: <462A625B.7010202@apache.org>
 <aae96ca0704220511o2af4b4c5wca40b7198a30bfd4@mail.gmail.com>
 <8b3ce3790704220529x2ce7d7c1x248665113ec310a4@mail.gmail.com>
 <aae96ca0704222355q3586025ck840bb29d1bef97e@mail.gmail.com>
 <8b3ce3790704230504qe73aae2n8997df691bc3066d@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D438AC4C-C161-4482-B7E7-AAB64FDAA191@gmail.com>
Content-Transfer-Encoding: 7bit
From: James Mitchell <jmitchtx@gmail.com>
Subject: Re: PROPOSAL: s1 modules module
Date: Mon, 23 Apr 2007 08:58:24 -0400
To: "Struts Developers List" <dev@struts.apache.org>

Ted, I'm willing to do s2 releases.  However, even with the  
documentation on the wiki, the process still seems very complicated.   
As far as building and pushing bits around, I'm ok with it, but when  
it comes to the release notes and open/close jira issues, it's not  
totally clear (to me) what needs to happen.

If you don't mind a little hand holding, I don't mind volunteering  
the time.


--
James Mitchell


On Apr 23, 2007, at 8:04 AM, Ted Husted wrote:

> On 4/23/07, Antonio Petrelli <antonio.petrelli@gmail.com> wrote:
>> Probably because making releases is (or better "was") a painful
>> operation. What if with 2 mere commands you created a release?
>
> The Struts 2 process is documented here:
>
> * http://struts.apache.org/2.0.6/docs/creating-and-signing-a- 
> distribution.html
>
> I wouldn't call it painful, but it still "stings" a bit.
>
> I know Wendy has mentioned using the release plugin, but I'm not clear
> on what changes that would make to the workflow.
>
> One missing step is that we aren't generating "docs" or "J4"
> artifacts. I've been pulling them out of "-all" and zipping them up
> nonindependent. The J4 artifact might be problematic since we also
> need to run the backport utility, though I've heard there might be a
> plugin for that too.
>
> We're in desperate need of more Struts 2 release managers. I'm swamped
> this month, and I'll be very busy through the end of June. Unless
> someone else steps up, I'm afraid the S2 releases will grind to a
> halt.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org