2010/1/28 Philip Potter <[email protected]>: > As a lurker, user, and very occasional hacker, I wasn't at all aware > of this branch. I don't honestly know where most of the discussion of > padre happens, but my impression is that it's split between this list, > IRC, and trac.
Most of the coordination and debate happens on the IRC channel. People tend to use the mailing list for announcement of various kinds, and issues that can't be solved immediately by whoever happens to be around. Stuff like this thread that need more drawn out debate and a wider range of contributors. > I don't like the idea of releasing something which hasn't been tested. > Padre is now mature enough that I use it as my usual IDE to get things > done, and I think CPAN releases should aspire to some level of > stability. By releasing undertested code, you're making testing the > ordinary user's job instead of the people who choose to be involved > with the development process. I'd just like to note here that one of the main reasons we release so often is to allow us to deal with this stability problem. We're willing to tolerate an occasional bad/unstable release accident because, as a development tool, people don't HAVE to update to the absolute most recent version and can continue to do their job with an older release. By releasing regularly, we ensure that people skipping a release or two due to problems don't miss out on TOO many goodies. We all know that a time will come when CPAN releases need to become much more reliable and more stable, with a more thorough QA testing process and a slower release pace. We're already seeing 2 days of delays added to the original release tempo specifically to let translators catch up and resolve language issues. But I don't think the time has come yet that we need to protect the stability of the CPAN releases at a code level. The incremental improvements to things like the badcode tests, and the ongoing usage of trunk by whoever is doing development at any given time should be enough for the moment to keep things relatively sane, and we can resolve bad releases by getting a newer release out that fixes the problem within a few days. Adam K _______________________________________________ Padre-dev mailing list [email protected] http://mail.perlide.org/mailman/listinfo/padre-dev
