Thursday, November 15, 2001, 12:03:38 PM, you wrote:
One thing being added is an 'upgrade.pl' program which upgrade you
automagically, provided you have not made significant changes to the
base code. In following the design, you should never need to change
the base code (just add your own hooks when necessary) so you should
always be able to upgrade with a simple './upgrade.pl stable' or
something of that nature. The idea is that you will get new OSRS
offerings without having to reinvent your system.
I believe development is a couple of weeks away from pulling this off
but it is in the works. And NOTE: you will not be able to
'./upgrade.pl stable' from the non-SF version to the SF version.
That would be cool but is not in the cooker at the moment.
-tom
JC> i agree with #1 as well - I have gone live on SF and upgraded to a new
JC> release after going live - took me next to no time at all to upgrade
JC> compared to my old exercises - very happy with SF (apart from the RENEW
JC> side - but that will improve )
JC> cheers
JC> Jim Carey
JC> www.OZbcoz.com discount domain registration
JC> www.iluvoz.com affordable hosting services
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>> Behalf Of [EMAIL PROTECTED]
>> Sent: Friday, 16 November 2001 4:43 AM
>> To: Scott Allan
>> Cc: [EMAIL PROTECTED]
>> Subject: Re: Client innovation
>>
>>
>>
>> On Thu, 15 Nov 2001, Scott Allan wrote:
>>
>> > We are about to make the SF release of the client the official
>> release for
>> > OSRS, and I would like some feedback on our approach. There are
>> basically
>> > two ways we can do this:
>> >
>> > 1. Hard cut: make SF official and only "innovate" on that version. This
>> > would mean that any new functionality would only be developed by us ion
>> > that code base
>>
>> I choose #1 with the assumption that you will fix any bugs in the last
>> version of the "legacy client" as they are discovered.
>>
>> > Would like your comments on all this. We do not mind supporting both,
>> > however it just means we will in general innovate less from a feature
>> > perspective as we will have an increased maintenance overhead.
>> We feel the
>> > SF client is far superior, however we appreciate the pain in migrating
>>
>> For those with customizations, the pain also exists when upgrading to a
>> new client version. So I say just go for it. As I stated above,
>> enhancements/bug fixes to the SF client and bug fixes only to the legacy
>> client.
>>
>> > Also, the old clients will always (for the forseeable future) work,
>>
>> Yes, this is a basic requirement.
>>
>> Regards,
>> Bill
>>
>>
