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

Hello,

After some busy weeks, I found some more time to devote on
flexinode. I 
beleive flexinode is critical for 4.7. Also for the Drupal
4.7 release. It is 
a popular module, and rather a complex one. Without a 4.7
release we will 
have a big lot less testers and people who want to move to
4.7. 

Samc recently hopped in and is testing and making patches
like a madman, 
thanks for that! I am doing at least five to seven patch
tests and/or commits 
a day too, but we are still far from a release, that is by
far not enough to 
ensure a safe upgrade to 4.7 for flexinode users soon.

So:

* No. I will not drop flexinode in favour of CCK. CCK is not
tested in 
critical environments, there is no (tested, full-proof)
upgrade path, etc. It 
is just not ready for prime time yet (IMO). I will maintain
flexinode for at 
least one release cycle, depending on the speed of
development in CCK. 

* I would love to have someone maintain the 4.6 branch of
flexinode. I you 
have several or one sites running 4.6 flexinode, and some
time left, mind 
doing this? I do not actively maintain any myself, and I
would like to focus 
entirely on getting a solid 4.7 flexinode out. Just Do It,
its nothing 
official, but please announce it somewhere so we know who to
turn to.

* I would love help in that road to 4.7.  Both in testing
patches, and in 
committing them. Anyone in for some flexinode joy? Same as
above, its nothing 
official, but you'd need at least commit rights to CVS, and
some experience 
with patches and flexinode (otherwise it will cost us only
more time). 

Cheerios, and flexible greetings,

Bčr

Hi,

On 4/21/06, Bčr Kessels <berwebschuur.com> wrote:
> Hello,
>
> * I would love to have someone maintain the 4.6 branch
of flexinode. I you
> have several or one sites running 4.6 flexinode, and
some time left, mind
> doing this? I do not actively maintain any myself, and
I would like to focus
> entirely on getting a solid 4.7 flexinode out. Just Do
It, its nothing
> official, but please announce it somewhere so we know
who to turn to.

You probably saw some of my patchs and ideas in the
bugtracker.
Those mean that I use and develop things in flexinode for my
clients.
I'm glad to make some more patchs (I know I have to
refactor some of
them, that were sent) to fix and to add some features.

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.

What do you think?

Regards,
  Fernando Silva

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