Tim Legant <[EMAIL PROTECTED]> writes: > This sort of transition is something that we might do when making a > big change to a release after 1.0.
Not exactly. What I plan to do is have two branches at that point. An "unstable" branch where we can do whatever we want (perhaps 1.1.x), similar to what we do now. And a "stable" branch which will begin with 1.0. Only bugfixes will be committed to this branch, so the 1.0.1, 1.0.2, etc. releases will have the same functionality, just with increased stability. No new features or changes. Users can choose their path based on their aversion to risk, etc. > Yeah, upgrading hasn't been a big priority -- many of the recent > changes aren't things I particularly need. That's true. There's value though in using the latest and greatest simply to catch bugs. More users == more squashed bugs. > Do you find it annoying when cron sends you an error mail? Absolutely. I'm usually already aware of the problem and feel cron is trying to force me to fix it immediately. I also don't like coming back to 500 identical cron messages because the network interface failed for a few hours for example. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
