On 3/1/07, Ted Husted <[EMAIL PROTECTED]> wrote:
We choose not to re-use a tag after a build has been released, where "released" means the PMC has voted on the build. But, if it's still a test-build, and it would be helpful to retag it for some reason, then "no harm, no foul". I've been known to reset a tag up to three times before calling a vote. This situation is nebulous, since there is a vote thread, but no actual votes :)
I agree with what Ted - from a purely practical PoV the effort required to re-tag and rebuild a 1.3.7 version would be no different from creating a 1.3.8 version. So for me I think its less confusing to just roll 1.3.8 - but I don't have a strong opinion so would leave it down to the RM whose actually doing the work. Niall
If a tag is reused, it's important to delete the old one first. * svn delete https://svn.apache.org/repos/asf/struts/struts1/tags/STRUTS_#_#_# -m "STR-### Removing first try at #.#.#." -Ted. On 2/28/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > Michael Jouravlev wrote: > > Paul, do you think that STR-3009 -- ActionRedirect from ForwardConfig > > not redirecting properly -- should be fixed for 1.3.7 to minimize the > > impact of 1.3.5 ActionRedirect behavior? > > > I believe once a release is tagged, it cannot be undone. There is a > ticket list for 1.3.8 which you can work on. If you believe the 1.3.5 > forwarding behavior is an issue, you can give your unbinding -1. What do > you think? > > Paul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
