The impression this gives is wonderful. Wonderful because it invites people to get involved and stay involved. It gives the impression that contributions are welcome and that there is even someone ready to leverage the power of the many developers who do not yet have commit access as well.
What is also shiny is that by using terminology like "sprint" notions of agile project development come into focus. I am not advocating a new MediaWiki release every four weeks, but having four or more releases a year will be less stressful then the current waterfall of functionality that is in release 1.17.
So check out the list of open bugs and help us get properly ready for the next release. There is one fringe benefit for a good relation with the bugmeister... your JavaScript has to be upgraded next. You might as well get your feet wet now.
Thanks,
GerardM
2 comments:
Thanks for the blog post. I've been taking patches people submit and applying them and using the opportunity to get new MW committers. So, yes, patches that people leave as attachments on those bugs will likely get applied.
I think 4 releases a year is a little ambitious right now. I'd like to see us hit 3 this year, and manage to get 1.17, 1.18 (current trunk) and 1.19 by the end of the year.
Post a Comment