← Back to team overview

widelands-dev team mailing list archive

Build 18

 

Hi everyone,

Build 17 was released 1 1/4 year ago. It's getting time to get Build18 out of the door. I already had a chat with Holger whether we name it Build18 or 1.0 - initially I wanted to make it 1.0, but with all the improvements and changes waiting in different branches, I am not sure, whether we should wait one more release 1.0 - however if we switch to SDL 2.0 with the release after Build18, we could directly go Widelands 2.0 as well ;).

An even more important reason for a soon Release of Widelands Build18: Widelands received a whole bunch of improvements, features, bug fixes and love :) - even in the current trunk state it shouldn't be hard to release "The best Widelands version ever".

To start the discussion about the release, I suggest the following time frame:
* Feature freeze 2013-08-04 23:59 CEST
* RC 1 2013-08-17
* Release 2 weeks later if no big bugs appear, else - as before - RC2, ...

There are some nice branches on lp, which I would be happy to see completed and merged before RC1, but
1) I don't want and can't rush anyone to to do the leftover work
2) Merging a new feature branch always brings new unforseen bugs (just take a look at the list of seafaring related bugs that appeared after my branch merge ;) ), so we should keep that in mind.
3) We shouldn't forget to keep some work for 1.0 ;)

Therefore I go the other direction and ask *you*:
Which branches would you like to bring further and merge until Feature Freeze? Who can help you and how can one help you?

And the most important question: How do you think about my suggested plan?


One more thing to say:
*Thank you everyone!*
I joined the Widelands Development Team about 6 years ago and there are quite some good reasons why I stayed until now (and most likely in the future :) ) - however the biggest reason is our great team :)!

Let's make our coming release even more shiny than all previous ones.


Looking forward for your replies
Peter


Follow ups