From: Scott H. <tal...@ne...> - 2009-11-28 04:55:27
|
On Nov 27, 2009, at 6:09 PM, K Post wrote: > The MS approach definitely works, In theory at least, their updates > are (also theoretically) tested by a whole team of people before they > go out and on all sorts of configurations and hardware. ASSP would > only have Thomas and maybe Fritz to test on whatever configs they > have. What if they miss something? Also, keep in mind, we are talking server and client here. I am not aware of any server OS from Microsoft that deploys auto update. Apple comes about as close as you are going to get, with download in BG, and then an alert sit there and waits for you to dismiss it, or proceed. The change log is there on screen with it. Detailed url to more detailed change log is always available. Tutorials on setting up an OS X Server suggest the first thing you do is disable software updates. These are servers, this is not PhotoShop. Apache has the versions: • Version 2.2 • Version 2.0 • Version 1.3 I can not find it any longer, but would be willing to bet, there are still more 1.3 installs out there than 2.0 and especially 2.2. > I just can't afford for assp to crash when I'm not around. > Autoupdates are just asking for trouble IMHO. Agreed. It is trying to solve a problem, that being not enough people upgrading, with the completely wrong solution. There are a number of ways to solve the problem of getting people to upgrade, and be more interested in participating in the 2.x testing. Sorry, but an auto update mechanism is a feature of the software, and will do nothing to improve those numbers. If anyone would like to know my thoughts on why there is an apparent lack of interest in 2.x, how to solve it, rather easily, let me know, I will post a reply here. > FYI, I just put: > new\sassp\sversion.*is\savailable\sfor\sdownload\sat\ssourceforge > in my notifyRE. Got my first notification via email today when 0.6.4 > came out. > > I'd love to get a changelog emailed - and I think that would help to > incentivize admins to upgrade. Still that's extra coding for Thomas. And that is the thing, no extra code should be added. You just managed to get an alert with functionality already built in. That is awesome as it stands. Among many of the suggestions I have in mind, is that there needs to be a changelog online, and that means not in a package, but just at a url, you can see, with clear dates, clear version numbers etc. That url is stable, example.com/changelog or whatever. It is a waste of time and code to implement this into ASSP. You will find, that when you do, tutorials will pop up as usual, for helping with ASSP, step one of config, is going to be to turn of auto updates. I have a lot to say about this, and will close with some short comments. If I know someone would like to hear how I think ASSP can move forward with 2.x and get more testers, and more people willing to update, please ask. For example: http://assp.sourceforge.net/ 2.x not mentioned at all http://sourceforge.net/news/?group_id=69172 <- News 2.x not mentioned at all http://sourceforge.net/projects/assp/files/ <- Downloads 2.x not mentioned at all http://sourceforge.net/projects/assp/develop <- Develop within SF 2.x not mentioned at all There is a Develop link on the main page, that implies you want to help develop. People like to beta test, let them know about it, on the main page, do not make them work for it just to find it. Move the downloads into SF, it does not make a lot of sense, the url changes, you end up at a totally different domain, that has no trust like SF or the main page would. If I were a new user, looking to test 2.x, I would go to the main url, either not find 2.x, or abandon it, as I would not trust I even had the correct files when I see I am not in SF anymore. If SF is not conducive to development, find a new host. SF is is nothing but slow pain for me. For em to be certain about 2.x, I would have to join the list and ask. This got longer than I wanted, I have more comments, if anyone is interested, I will write them up, and hope we could see some of the suggestions implemented, all of which I would be more than happy to assist in. -- Scott * If you contact me off list replace talklists@ with scott@ * |