----- Original Message -----
From: "Glen Daniels" <[EMAIL PROTECTED]>
To: "Axis-Dev (E-mail)" <[EMAIL PROTECTED]>
Sent: Sunday, June 08, 2003 12:20
Subject: 1.1 pre-release (please test)


>
> grab the package, install it, and test it a bit to make sure we don't have
any obvious problems.

will do

>
> 1.1 has been a while coming, and it certainly isn't perfect.

Nothing ever is, but shipping stable versions helps users stay up to date.

There are a whole bunch of things that need to happen (fixing the build/test
process, tackling the much-too-long bug list, etc), but we need to put
another stake in the ground rather than delaying the release still further.

>Myself and others plan to attack some of the to-dos soon after the release,
and I hope we can come out with >an even better 1.2 release within a month
or two (release early and often!).

What is a good update schedule for Axis in its current stage of life? I
think Axis1.1 did take a long time to get out the door, but it meant that it
has many, many fixes in. Would frequent & regular be better than every nine
months? A lot must depend on how & where axis gets used.

I ask as if we do have a discussion on Axis1.2 features, as well as the
outstanding bugs and various uncommitted changes, we should look at what
bigger, more profound changes we want to make.

If you do quarterly releases its very hard to add significant
features -unless we branch and release 1.1.x bug fix builds while working on
the 1.2 feature release.

-steve

Reply via email to