[development] flexinode towards 4.7: update, and it needs additional maintainer(s)

[Bèr Kessels]

Op vrijdag 21 april 2006 14:14, schreef Fernando Silva:
> But to do this, I must have some "garantie" that the work I would do
> in flexinode 4.6 would have a port to 4.7; so I can then upgrade and
> not loose work.

Unfortunately non of us can guarantee this. In fact, I think that we can 
safely assume that work done for 4.6 flexinode will not be ported to 4.7 
without lots of additional effort.

On top of that, my #1 priority now, is to get 4.7 stable. After that, we can 
see what to do with new features for 4.6 and 4.7. and with non-critical 
bugfixes for 4.6.

Unless we have a dedicated 4.6 flexinode maintainer, I also think it is good 
idea to state that we do not allow ANYTHING but critical bugfixes into the 
4.6 flexinode branch. 

Bèr