This is a great module. Thanks Jacque for your work. I've just donated 25 Euros. (Hey folks, make at least some of your money contribs in advance of it being done. Jacque is surely going to finish -- let's let him know we have faith in that!

I'd like to do some testing to help out. On the project page, only the 12/29/08 version 1.0-rc3 is listed. Looking into CVS it seems there has been a lot of commits happening since then. I just downloaded a version of node_import using CVS and I used the tag: 6--1, which seemed to work to give me all the latest commits -- though I haven't installed it yet.

In short -- I think you'll get a lot more help in testing if you describe, on the project page, what version you want people to test on and how to get that version.

Right now, a lot of people who read the project page will think that nothing has gone on since December, and that certainly isn't the case.

Again, thank you -- and I hope to get on board with testing.

Shai Gluskin
Content2zero

Comments

Robrecht Jacques’s picture

Robrecht Jacques commented
Status: Active » Closed (won't fix)

No.

The reason why: because if users download a -dev version it is harder to exactly detect what version they use AND the -dev is used for development so it is unstable by nature.
People who can handle how to interpret -dev version should have the knowledge to find the release, either by CVS or by looking at "View all releases".

But, I should create a -rcX release more often... maybe not each time a bug is fixed or a feature added, but at least more then I do now. I wanted to get all CCK stuff in -rc4, but I'll release a -rc4 later today.

BTW, thanks for the donation.