This began by asking for a branch. If there's reason to branch,
there's reason to release. Now, we seem to be saying there not a
reason to branch either.
There just might be a misunderstanding about when we create branches.
Typically, we just tag each milestone. Later, if we need to go back
and p
Ted,
Because no one is asking for a 1.3.6, and the new actionId feature (a
semi-major one inmo) is already committed, can we just continue to
develop this release and call it 1.4 afterwards? I really don't see a
need to get this release out the door quickly. Even if 1.4 sounds too
big of a le
On 11/27/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
Ted,
Do you want the open tickets to hold up the release? Please respond. If
you respond in the negative, please tag. Afterwards, I will:
If there's a patch attached to a bug ticket, or we otherwise know how
to fix the bug, we should resolv
On 11/27/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
Do you want the open tickets to hold up the release? Please respond. If
you respond in the negative, please tag. Afterwards, I will:
* Re-assign the open tickets to 1.3.7
* Write the release notes
* Update the maven projects to 1.3.7-SNAPSHO
Ted,
Do you want the open tickets to hold up the release? Please respond. If
you respond in the negative, please tag. Afterwards, I will:
* Re-assign the open tickets to 1.3.7
* Write the release notes
* Update the maven projects to 1.3.7-SNAPSHOT
Paul
Ted Husted wrote:
In my experience, th
In my experience, the only difficult part of a release is catching up
the release notes. The rest is just mechanics. I'll setup a release
notes page for Struts 1.36, and if someone wants to bring it up to
date, I'll take care of the rest.
-Ted.
On 11/26/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/26/06, Ted Husted <[EMAIL PROTECTED]> wrote:
My best suggestion would be to tag and roll a 1.3.6 build now, before
getting into a new line of development. Creating a branch would then
be less important.
I think a 1.3.6 release goes in the 'would be nice' column. There
were a few fixes, e
My best suggestion would be to tag and roll a 1.3.6 build now, before
getting into a new line of development. Creating a branch would then
be less important.
If we did create a branch, we should give it a name (like i18n). Then,
if we find the changes joyful, the branch can be merged back into th
Dear committers,
I would like to propose branching HEAD because of forthcoming locale
resolution strategy. I am still working on s1 with the focus of bringing
S1 to a full set of customizable internationalization capabilities.
Because the locale resolution is more powerful and may behave sligh
