You might do a new release with all comited patches one day.

What do you think about passing to beta status? I'm using it since 3 weeks, with all the patches we both made, no big bugs or such. It lacks of community tests, but since you don't have any feedback..

I'm running two preprod environment with patched version of datasync, this is really hard to maintain with all these patches!

Notes, all patches I've tested and I currently use are:

What do you think?

Comments

andrewlevine’s picture

andrewlevine commented
Status: Active » Fixed

I created a new release with

I figure next week or so we can release a beta. Check the backtrace issue for my comments on that. By the way, you can use a CVS checkout of datasync DRUPAL-6--1 to keep track of all the versions as they are committed (might be easier for you)

pounard’s picture

pounard
Primary language French
commented

Yes! You're right, I could track with a CVS copy. The fact is we use SVN for our projects, so I'm forced to keep track patch by patch to synchronize our project's repo with this module code.
For the backtrace issue, I don't know if I'll be able to do it quick, I have a lot of work here, I'll see if I have some spare time to do it.

Thanks a lot

andrewlevine’s picture

andrewlevine commented

fyi, we use SVN here too. we checkout all projects with cvs and commit them to svn (including CVS folders). then when we want to update we run cvs up and then svn commit again. May not work in your case but figured you might be interested

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.