I am also -1 because on #2 that's not how I understand the
voting process to work. It's cut a version, publish it out as
beta for developers to use, vote later on it. I model my thoughts
after what I've seen on Tomcat.
-- Paul
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> On 5/16/06, Don Brown <[
I am +2 with Don's idea. Quite frankly, my favorite Apache projects
besides Struts are Tapestry and Tomcat, and those PUT OUT BETA versions
on their website. The versions are specifically listed as beta, and then they
change the website to list it as GA if a vote changes it.
-- Paul
--- Don Brown
On 5/16/06, Don Brown <[EMAIL PROTECTED]> wrote:
I think the solution is to:
1. Make betas publicly available and widely known like our 1.1 betas were
+1
I think the notion that we can't announce and mirrors Betas is a
misunderstanding. We can mirror an announce *any* release, even an
Alpha.
What I dislike is spending untold personal hours fixing all known
issues and putting out a release, only to have it continually shot
down, not available to anyone. Specifically:
1. Our release plan states we only make GA's available on the mirrors
and from the download page, so anything less is
We've been cleaning up and reorganizing the API to make it more
intuitive and user friendly. Any feedback is much appreciated.
Bob
On 5/16/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
I don't remember an SPI being part of WW. Is this new to Action 2?
--- Bob Lee <[EMAIL PROTECTED]> wrote:
> I
Doh. Here it is:
http://issues.apache.org/struts/browse/WW-1314
Bob
On 5/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:
The list won't accept attachments. You should open a JIRA ticket instead.
-Te.d
On 5/16/06, Bob Lee <[EMAIL PROTECTED]> wrote:
> I've attached a patch with the API updates we
I think it would be a good idea if we either linked or transfered
some content from the Wiki pages to the user guide.
For instance, I just read the upgrade notes on 1.2.9 on the wiki
and it is fabulous. Those kind of things should be first-class
documents in our website.
Any thoughts about this p
I don't remember an SPI being part of WW. Is this new to Action 2?
--- Bob Lee <[EMAIL PROTECTED]> wrote:
> I've attached a patch with the API updates we discussed last week. I
> also fixed the Maven build to correctly build the API again.
>
> The latest Javadocs are here: http://www.crazybob.or
The list won't accept attachments. You should open a JIRA ticket instead.
-Te.d
On 5/16/06, Bob Lee <[EMAIL PROTECTED]> wrote:
I've attached a patch with the API updates we discussed last week. I
also fixed the Maven build to correctly build the API again.
The latest Javadocs are here: http://
I've attached a patch with the API updates we discussed last week. I
also fixed the Maven build to correctly build the API again.
The latest Javadocs are here: http://www.crazybob.org/javadoc/
Thanks,
Bob
-
To unsubscribe, e-ma
At 1:07 PM -0500 5/16/06, Joe Germuska wrote:
I've uncovered a couple of things in porting an old Struts 1.1
application to 1.3; I know they probably need to go in Jira, but I
wanted to get a little discussion about them before filing them.
Actually, now I think i'll send them separately with d
At 1:07 PM -0500 5/16/06, Joe Germuska wrote:
I've uncovered a couple of things in porting an old Struts 1.1
application to 1.3; I know they probably need to go in Jira, but I
wanted to get a little discussion about them before filing them.
Actually, now I think i'll send them separately with d
I hadn't made a point of responding since the vote was already
closed, but I've come to agree that the problems identified with the
1.3.4 build are sufficient to make it a "beta", and further, I've
just identified one or two other things that are worth nothing that
probably further justify that
13 matches
Mail list logo
