I am not opposed to a 1.1 alpha/beta. (a.k.a +1) Build/ship it on Monday? Then set a schedule for 1.1 final.
-- Tom Jordahl Macromedia -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Today's IRC log -couldnt make the IRC; tuesday am is one of my weekly meetings, and next week I'm off-line for the whole of the day. The key points from the log are axis1.1 is the current bugfix version; big changes come out in 1.2. Seems ok to me. There are advantages in cutting a 1.1alpha and making it available real soon; axis-users can get an early drop and find any regressions we have slipped in. If we go straight to final, something will burn us. Actually something will burn us no matter what, but that's just a fact of life. once a timeline is agreed, we should communicate to axis-user. ----- Original Message ----- From: "Glen Daniels" <[EMAIL PROTECTED]> To: "'Axis-Dev (E-mail)'" <[EMAIL PROTECTED]> Sent: Tuesday, November 26, 2002 14:01 Subject: Today's IRC log > [13:11] <tjordahl> Schedule for 1.1 and release manager? > [13:12] <GlenD> Next week we'll schedule a call and go over the list and see where we're at. > [13:12] <davanum> Schedule: How about before christmas? > [13:12] <GlenD> Criteria for 1.1 first, maybe. Are we good with releasing the current codebase, or should we wait for the bug scrub? > [13:12] <GlenD> Oh, before Xmas should be OK, I would think. > [13:13] <GlenD> I can release manage. > [13:13] <davanum> Glen: I think we should bring down the bug count to around 60-70... > [13:13] <tjordahl> Do we need a beta or RC? OR shuld we just cut a 1.1 and ship it. > [13:14] <davanum> Cut 1.1 directly. > [13:14] <GlenD> I think we can just cut 1.1 and ship it when we think it's ready, personally. > [13:14] <GlenD> We can always do a 1.2 (release early and often) > [13:14] <davanum> yep. > [13:14] <DaveChapp> What's the rush to get it out before XMas? > [13:14] <GlenD> Holiday shoppers. > [13:15] <GlenD> Oh, wait.... > [13:15] <GlenD> "The perfect gift for your Java geek friends!" > [13:15] <davanum> Dont' want 3 months before releases... > [13:15] <GlenD> Seriously, I think before the end of the year would be nice, and that means before XMas, realistically. > [13:16] <tjordahl> It would sync up with some stuff interally. But mainly its to get users using a bug fixed release post-1.0 > [13:16] <DaveChapp> Always a good idea. Nobody dares to use a 1.0 product. > [13:16] <tjordahl> There is alrady lots of stuff we are telling people to check in the nightly's. > [13:16] <tjordahl> (Faults, doc/lit WSDL, headers, etc) > [13:16] <GlenD> Plus that servlet thingy > [13:16] <davanum> Remember we need to run TCK Test Harnesses again :( > [13:17] <GlenD> good reasons to ship soon > [13:17] <GlenD> yup > [13:17] <tjordahl> Did Sam every get that automated and passing? > [13:17] <tjordahl> s/every/ever/ I have diverged my buildTest.xml and httpunit somewhat, but am leery of committing as things arent full functional. -httpunit is moved into place for automated execution -but it is excluded from the functional tests as somehow TcpListener gets involved and bad things happen. Probably configuration or something. -also added proxy support for all tests -offline is in there, but the patterns arent working yet -I need to move AxisTestBase In terms of other bugs I'd address 1. look at the wsdl i18n issues; should be a matter of declaring the encoding 2. simon fell mentioned way back that some sizes of attachments dont work 3. I'd like to start a configuring.html doc listing the options for global server config 4. Come up with a nice way of omitting the stack trace from exceptions, by default. 5. add a cover doc to the ant tasks (one that has examples, talks about <mapping>) -Steve ps: is there a checklist of all that is done for a release? I've attached the ant one that could be taken and changed. Shorter intervals, more mention of interop testing, different mail lists &c.
