Re: [Widelands-public] Build 15, launchpad, bzr -- what i've learned so far

[Holger R. <Hol...@gm...>]

Hi,
> 
> if i can make a suggestion. how about holding an (irc)
> meeting/discussion to vote on which bluerints will be targeted for the
> next build. I think it might be helpfull so everyone knows that after
> build15 scons is going to disapear, lua code will be in build16,
> opengl not in build 16 but soon after, maybe build17 etc (just
> examples, not saying anything about these timelines specifically)
It is hard to do this in one meeting, I guess. First because it is hard to get all developers at one time and second because those things are quite rarely decided beforehand. In fact, most of these decision only factor out over time. I'd like to improve the process here, but I am without idea how this could be achieved. 

> 
> of course no deadlines written in stone. but just knowing which
> branches are 'interesting'/i want to use in developing my own features
> and which ones are 'a far off build/just experimenting'  would be
> helpfull
There is at least the Status of branches on launchpad. You can set branches to experimental (and most developers already do this) if you are not sure that what you try is a good idea. It would also be useful to add a short description of the branch on it's whiteboard if it is not completely clear from its name. 

Holger