On 31 May 2010 23:48, Steffen Mueller <smuel...@cpan.org> wrote: > The porting of all existing tasks to the new API is going to become > slightly problematic before merging the branch into trunk: I believe > quite a few plugins use the v1 task API and branching every plugin > separately would be a pain.
For me, the most interesting accidental feature for the new API is that both the old and new task managers are able to run in parallel. One option we could go with is to merge down to trunk straight away, and do a couple of releases with both task managers so that plugins have a few releases in which to migrate to the new API. The only downside of this approach is that we'd be stuck with using the Padre::Task2 namespace indefinitely, rather than being able to use Padre::Task. Personally, I wouldn't mind doing one last "stable" release of the current trunk (since we've had a bit of an island of stability) and then just breaking everything for a month or two, with a target of being back to full stable by the birthday party. We haven't had a particularly big breakage since Config 2.0, so maybe it's not unreasonable to have one again a year later. Adam K _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
