2008/3/9, Paul Benedict <[EMAIL PROTECTED]>:
> I am still interested in patching Struts 1.x bugs as they come in and
> queuing up releases. The delay between 1.3.8 and 1.3.10 was my doubt that I
> can count on +3 binding votes for the 1.x releases. Even if Struts 2 is the
> craze, I still am in
I've put down some thoughts as to how we could leverage Spring's XML
schema support to merge the Struts and Spring XML into one file. For
Struts apps, this might be a nice way to leverage all the XML loading
advantages of Spring and remove yet another configuration file,
however my main motivation
+1 for #1
Martin Cooper schrieb:
> I'm pondering the "right" way to update the developer list in our master POM
> for people who have gone emeritus. I can think of several options:
>
> 1) Prefix the role with "Emeritus", so "PMC Member" -> "Emeritus PMC Member"
> and "Committer" -> "Emeritus Comm
I still work on Struts 1.3 projects. So I keep evolving 1.3 (and put
everything in HEAD) also.
Paul
On Sun, Mar 9, 2008 at 5:54 AM, Antonio Petrelli <[EMAIL PROTECTED]>
wrote:
> 2008/3/9, Paul Benedict <[EMAIL PROTECTED]>:
> > I am still interested in patching Struts 1.x bugs as they come in an
What about #1 with 1 twist?
Prefix the role with "Emeritus (mm/YY)" to further clarify when they
went inactive.
Actually, my vote is for #3, since previous releases will have those
guys/gals still listed in the distribution. I think we should keep
the current list, ummm current. Just my $.02.
I'm not as concerned with "free-loaders" so much as I am with whether
there are actually very many people out there who really need these
new releases.
I don't mind helping test out a new build and voting based on that,
but I don't have any 1.3 apps in production that I can test/verify
with.
On
Is JIRA set up to use macros in comments? I thought it was able to render the
{code} macro in comments.
Thanks,
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Right now, comments are configured to use the Default Text Renderer, not the
Wiki Renderer, so that's why the {code} macro isn't working. We can switch
that easily enough, but I'd like to see if anyone has any security concerns
with that before we do so.
--
Martin Cooper
On Sun, Mar 9, 2008 at 2
On Sun, Mar 9, 2008 at 2:46 AM, Paul Benedict <[EMAIL PROTECTED]> wrote:
> PMC folk,
>
> I am still interested in patching Struts 1.x bugs as they come in and
> queuing up releases. The delay between 1.3.8 and 1.3.10 was my doubt that I
> can count on +3 binding votes for the 1.x releases. Even
On Sat, Mar 8, 2008 at 7:46 PM, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I am still interested in patching Struts 1.x bugs as they come in and
> queuing up releases. The delay between 1.3.8 and 1.3.10 was my doubt that I
> can count on +3 binding votes for the 1.x releases.
I'll make time to
10 matches
Mail list logo
