1  |   Order by index

Jan 11, 2003, 7:05pm

I've been following up in the Beta newsgroup and it looks like they have
went back to testing 443 for final bugs. That would be great if they decided
to release it heh? We wouldn't get all of the features, but we would get an
upgrade with some more, pretty cool features. Better than having to wait a
couple more months =\. Even if it meant having to wait for features like
jump and the others, it would be pretty cool. I hope that they release 443
^.^ What does everyone else think?

-Sk8man1 (346035)

Jan 11, 2003, 9:05pm

Although I believe v3.4 should have been released back then, now that the
work has been done(ish) my feeling is that they should finish the job and
release the new product as documented. Reverting back to a previous build at
this point is just makes an anticlimax out of what was going to be an
interesting release. It also makes a joke of the hard work that has already
been done on the new version by developers and testers alike.

To be honest, I'm not particularly interested in most of the new features,
mainly the sky, the additional SDK command (aw_avatar_set) and the "hide
chat" option, all of which were from the initial batch of enhancements.
However, in order to "rectify" the movement and seq problems they have in
the latest beta release, they need to go back to the design of the new
features and find the problems. From what YS was saying, the concepts that
have been implemented are flawed, rather than there being just plain old
bugs.

As an aside, although connected (in my head at least), this is the first
non-Roland release ... so they guys should be working extra hard on this
release because this is their chance to establish their reputations. If 3.4
becomes a buggy, descoped delivery, that will set the scene in many people's
eyes for future work. Some may say it would be a brave step to revert back
to 443, but I think it would be (a) a setting a dangerous precedent -
bucking out of a delivery, (b) risky - changing old code having worked with
later versions with different code/designs, (c) extremely annoying to many,
(d) forcing AW to effectively rush the delivery of an incomplete product
and, most importantly, (d) a total embarrassment!

Suggestions that AW should retrofit the subsequent bug fixes into build 443
is, to me, silly ... and particularly unconstructive. We've waited this
long, why not wait a little longer and get what we're expecting. Let the
guys get on with their job and let them deliver the product they want to
deliver and to the quality they believe it should be. Discretion is the
better part of valour (i.e. putting the problem off till later), but those
that run away don't get the rewards. My vote is for preseverence and
conviction from AW to complete the job they started, some forward planning
for future releases (and yet more conviction, this time on the scope of each
release and STICK TO IT) from AW and some much needed additional braincells
for a selected few in the beta team.

Grims.

[View Quote]

Jan 11, 2003, 9:08pm

Hmmm ... I really should have listened at school when they taught the
alphabet.

[View Quote] > (d) forcing AW to effectively rush the delivery of an incomplete product
> and, most importantly, (d) a total embarrassment!

Jan 11, 2003, 9:35pm

ROFL

[View Quote]

Jan 11, 2003, 9:40pm

I agree. It does no harm to release it. It will make alot of ppl happy. Most
ppl want new features but still be able to build and move easily. Exactly
that is what they get with 443.
But with 452+ they won't be able to navigate and move to where they need to
be for building and will have to wait many more months.

[View Quote]

1  |   Order by index