Re: win32lib.ew .41
- Posted by simulat <simulat at INTERGATE.BC.CA> Sep 10, 1999
- 410 views
Just a thought - why not use the Linux method? Use odd numbered versions for untested programs, and even numbered versions for tried and tested programs. ie win32libv4.0 - A tried and stable version win32libv4.1 - A new version still under development win32libv4.2 - When 4.1 becomes stable change it's name to this and start win32libv4.3 - As the new development version. That way people get to choose between the latest beta version if they are adventurous, or they could take the latest stable version instead. Bye Martin ----- Original Message ----- From: Cuny, David <David.Cuny at DSS.CA.GOV> To: <EUPHORIA at LISTSERV.MUOHIO.EDU> Sent: Friday, September 10, 1999 4:51 PM Subject: Re: win32lib.ew .41 > In thinking about the problems Judith encountered with the latest release of > Win32Lib, I'm not sure what to do. I test the code before posting it, but > obviously bugs get through, especially when new features have been added. > > Perhaps I should designate two versions of Win32Lib - an older, "stable" > version, and the "most recent" version. That way, if people run into major > problems with a new release, they could easily fall back on an older > version. Otherwise, I guess I'd have to start using beta testers - that > requires the kind of coordination that I just don't have the time or energy > for. > > Robert, is this possible? > > Thanks! > > -- David Cuny >