> > This would be disastrous, as it would break existing rc files that use Exec
> > expecting it to spawn a shell as it has done thus far. *If* a new keyword is
> > added, it has to reference the new functionality, not break the existing
> > functionality.
> >
> > Randy
>
> SO WHAT! This is the reason that 2.0.x is labelled BETA. Breaking people's
> configurations is not sufficient reason to prevent a design change. It
> should be announced prominently, but people using beta software can be
> reasonably expected to make small (or even large) changes to their
> configuration files in the interest of having better quality in a RELEASE.
No, you make sweeping changes in alpha. When you've reached the beta stage,
you have to consider the scope and impact of your changes much more carefully.
In addition, 2.0.45 may be labelled "beta", but it has also been in circulation
for quite a while now, and has an established user base.
Randy
--
===============================================================================
Randy J. Ray -- U S WEST Technologies IAD/CSS/DPDS Phone: (303)595-2869
Denver, CO rjray_at_uswest.com
"It's not denial. I'm just very selective about the reality I accept." --Calvin
===============================================================================
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Apr 17 1997 - 12:53:11 BST