Just a question: are you keeping good notes as to what you're
doing? I'd like for the details of the process to end up on a wiki
page if they are not already there. After reading these messages I
have no clue what you are doing :-)
Greg
On Dec 19, 2006, at 7:49 PM, Rahul Akolkar
On Dec 19, 2006, at 10:46 PM, Craig McClanahan wrote:
The updater
should be our long term direction, unless/until the Maven release
plugin
does all the stuff we need for staging votes.
What's missing in the release plugin? Just that there's no way to
stage a release? Do we use the
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
What's missing in the release plugin? Just that there's no way to
stage a release? Do we use the release plugin to publish a release?
Neither Struts nor Shale has so far used the release plugin at all.
The default distributionManagement
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
Just a question: are you keeping good notes as to what you're
doing? I'd like for the details of the process to end up on a wiki
page if they are not already there. After reading these messages I
have no clue what you are doing :-)
snip/
So you've probably already read the thread on the struts dev list,
but just to be proper about it...
Do you guys want any jira reports setup for your project?
Here's what I have so far:
http://people.apache.org/~dblevins/tmp/shale-attachments.txt
On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/19/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
OK, if everyone's fine with that, I will create the 1.0 branch (called
SHALE_1_0_x unless there are better suggestions) when we get closer to
the release (after all 1.0.4-SNAP
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
On Dec 20, 2006, at 2:01 PM, Rahul Akolkar wrote:
On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I would have a mild preference for naming the branch SHALE_1_0 but
I'm not
going to choke if we go with what you proposed either. I'm
On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
* I like the habit I've seen Rahul and others do in Commons, of
adding contributor entries for those who have posted
patches. A quick scan of our issues might be useful.
snap/
This becomes hard after the fact. If we decide to
On Dec 20, 2006, at 2:51 PM, Craig McClanahan wrote:
* Since the trunk is being continuously built by Continuum,
trying to do our release cutting there (including removing
SNAPSHOT from the version numbers) would cause Continuum
to publish a release, with the real version number, before
we
The Shale project currently does not have a bylaws document. I
propose that we adopt the Struts bylaws[1] as the basis for our own
bylaws document and make changes in the following areas:
1. Change all instances of Struts to Shale.
2. Discuss the Subprojects section. Specifically, do we
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
On Dec 20, 2006, at 2:51 PM, Craig McClanahan wrote:
* Since the trunk is being continuously built by Continuum,
trying to do our release cutting there (including removing
SNAPSHOT from the version numbers) would cause Continuum
to
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
The Shale project currently does not have a bylaws document. I
propose that we adopt the Struts bylaws[1] as the basis for our own
bylaws document and make changes in the following areas:
1. Change all instances of Struts to Shale.
2.
On Dec 20, 2006, at 7:54 PM, Wendy Smoak wrote:
On 12/20/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
So the first thing we'd do when we decide to release is - after
finishing up business - start a branch for the release. Then we
work
On 12/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Wed Dec 20 23:37:50 2006
New Revision: 489275
URL: http://svn.apache.org/viewvc?view=revrev=489275
Log:
Document the support for dealing with SHALE-61 issues (back and forward
buttons) that will be present in the
14 matches
Mail list logo
