On Tue, Jun 1, 2010 at 1:57 AM, Adam Kennedy <adamkennedybac...@gmail.com> wrote:
> 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. I don't like the whole huge unstable periods. I think every such period lowers the level of contribution to Padre. Now in the last couple of week we saw a lot less activity than before so I am not sure any further drop in involvement will be noticed :-( OTOH maybe the new and shiny Task will help generate some contributions. I'd say go ahead break everything but please be around helping people to fix issues. Regarding birthday and conferences ( I attend 3 conferences in June). I guess I'll need to install the currently released version of Padre and I won't be able to show it from SVN as it is going to be unstable. regards Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
