OK, the eagles are landing. I'll check on them again in an hour to see
if everything is uploaded, and make sure the permissions are correct.
Other than that, it's back to you, James :)
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROT
Since we seem to be good to go here, I'll plan on rolling 11 at 7
tonight EST. Hopefully this one won't crap out :)
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
1. Use JIRA search to find the tickets you want to modify. For instance,
maybe you want to find all unresolved 2.0.11 defects.
2. Then on the RHS above the search results there is a "bulk change" link.
Click that.
3. Check the tickets. You can also take all by selecting the checkbox in the
table
Thanks for the heads up. How do you do that? I did each ticket individually and
was thinking there must be a better way.
On Tue Sep 18 14:58 , 'Paul Benedict' <[EMAIL PROTECTED]> sent:
>James, if you do a mass update of tickets in JIRA, you can select to turn
>
>off email notification. That way
James, if you do a mass update of tickets in JIRA, you can select to turn
off email notification. That way 100 tickets don't produce 100 emails.
Paul
On 9/18/07, Ted Husted <[EMAIL PROTECTED]> wrote:
>
> On 9/18/07, James Holmes <[EMAIL PROTECTED]> wrote:
> > + Create 2.0.11 release notes? (I can
On 9/18/07, James Holmes <[EMAIL PROTECTED]> wrote:
> + Create 2.0.11 release notes? (I can do this)
You might want to bring the 2.0.10 notes forward, since it died in committee.
> + Roll the release (Ted - will you still do this?)
Sure.
-Ted.
--
So far:
+ I fixed the issue with Component.determineActionUrl()
+ I setup a 2.0.12 release in JIRA
+ I moved all of the tickets in JIRA that were assigned to 2.0.11 to 2.0.12
+ I cleared up the issue/concern about the escapeAmp attribute
(https://issues.apache.org/struts/browse/WW-2190)
What'
