On Tue, 2010-06-01 at 10:32 +0300, Gabor Szabo wrote: > > 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.
Interesting observation... > 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. > Not that I'm any expert in these things, but I think that the lack of involvement in Padre at the moment is due in part to our "alphas" being busy with other things. There is certainly a buzz in #padre when Adam is around pushing changes through, or Ahmed (azawawi) doing GUI stuff and the things that no one else seems to take on, like the key bindings stuff etc... And even you Gabor with the debugging stuff.. If people see the "main" people active in the channel and changes being committed there's are real feel of expectation.. like "can't wait to see the next release".. and people hanging around to get a glimpse of what is likely to come.... When these guys are in the groove I feel the buzz is up, it gets people interested to see what's going on, and also gives us "low hanging fruit" to pick up along the way, thereby increasing the number of commits and committers. When these "alphas" drop off, there is less for us mere mortals to pick up. The buzz drops off and the level of involvement also slacks. > I'd say go ahead break everything but please be around helping people > to fix issues. > Agreed, that's the big thing.. No slight on Steffen here, but the big change we did last time to fix up the leaked scalars was tough going, just after we merged Steffen's branch to trunk, Steffen was busy and we were left scratching our heads a bit with the changes - which I gather was about the time Adam really looked into the task API and began the long road to where he is today with his version of Task2. If Adam will be around, and with the seemingly 'straightforward' ability to port previous tasks to the new task2 and some people taking this up, I think we should be fine in terms of people being around and available to answer questions and sort things out. I"m more than happy to be around and on call to make quick fire releases as bugs get fixed. I know any one can do releases any time they like, but I'm letting you all know I'll be around to get them done when ever the need arises. > 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. Or not... the last lot of "unstable" we had - especially as I was release manager - wasn't an eat your code and melt your CPU level of brokeness. It was more like "we want to let you know if we find a bug there will be a new release soon after".. and a warning to package maintaners to sit back a while and wait until we are stable before spending hours building packages that may quickly find themselves replaced with a new release. However if you want a long stable release, we can go with spending a lot of time at 0.62 or 0.63 ( next one ) while we work on getting all Task based stuff migrated to Task2 with a big merge at the end of June. Just a thought and I'm happy to roll with consensus on this. Peter.
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
