This looks like a great module. I'd love to share it with more people by moving it to the devel package. kbahey would still be the maintainer. It would get its own component in the issue queue so mostly support would run as today.

I do request though that we post to D6 and D7 before integrating it. I try to keep devel up to date with HEAD, as crazy as that sounds. I really want to support the brave developers who work on core and the sites that are playing around with not yet released drupal.

If you prefer to keep this project independant, thats fine too.

Comments

kbahey’s picture

kbahey commented
Status: Active » Postponed (maintainer needs more info)

I am up for merging this to devel, an deprecating this project (will leave it here with a notice and no releases).

How about I start with committing the D5 stuff and branching it, so it is available in 5 while I work on porting to D6 then D7.

This way, I can quickly deprecate this project, and move the issue queue to devel.

Thoughts?

moshe weitzman’s picture

moshe weitzman commented
Status: Postponed (maintainer needs more info) » Reviewed & tested by the community

Sounds good. You now have devel commit access. Please make your own new subfolder in devel project for this module. We need to start using those best practices.

In D7, you can use multi-inserts and the DELAYED keyword (will be ignored by other DBMS) so that DB based logging is quite reasonable in prod IMO.

kbahey’s picture

kbahey commented
Status: Reviewed & tested by the community » Postponed (maintainer needs more info)

OK, code committed to devel's HEAD.

Re: branching for 5.x, i will add it to DRUPAL-5--1 so you can do a release (5.x-1.1) soon.

Is that OK?

kbahey’s picture

kbahey commented
Status: Postponed (maintainer needs more info) » Fixed

Marking as fixed.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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