At 12:44 PM 4/11/02, Bill Moseley wrote:
>It's hard enough finding time to work on swish development to then also
>maintain multiple versions.
Understood. That probably needs to get written into the ReadMe stuff!
People/companies using Swish need to understand that bug fixes require
upgrades, and there really won't be a "stable release" that gets bugs
fixed without changing anything else.
It might be nice, however, to keep around a series of snapshots that
the developers think are most stable. That way people could choose
to do a minor upgrade to something that seems safe instead of going
all the way to the current bleeding edge code.
That's where a less formal release process comes into play. Right
before really big changes, and especially before introducing any
known incompatibility with prior versions, save off a zip file with
whatever has been out there for a while and seems safer than it will
mailto:eckert(at)not-real.climber.org | http://www.climber.org/eckert/
Info on peak climbing email lists mailto:firstname.lastname@example.org
"The reasonable man adapts himself to the world:
the unreasonable man persists in trying to adapt the world to himself.
Therefore, all progress depends on the unreasonable man."
-- George Bernard Shaw
Received on Fri Apr 12 16:10:29 2002