-
Notifications
You must be signed in to change notification settings - Fork 53
Home
Update! - 6th October 2011
Hi all, Adam here again. For several years I didn't need to use MySQL, during which time I stopped maintaining mysqldiff. However, in my spare time I am now working on a new project which does use it, therefore I've started doing a bit of maintenance again.
I'm still very busy but I found time to merge two big patches, fix a number of issues, and upload a new release to CPAN. There's also a CPAN bug/issue tracker linked below. Please make sure your issue is submitted to that tracker.
- Documentation via CPAN: http://search.cpan.org/dist/MySQL-Diff/
For downloads, see the CPAN page: http://search.cpan.org/dist/MySQL-Diff/
However it's recommended that you install via normal CPAN installation procedures.
If you encounter a problem, please check the bug tracker to see whether it is a known issue:
If your issue is not listed and you are fairly sure it is a bug, please follow the "Report a new bug" link. Otherwise check out https://github.com/aspiers/mysqldiff/blob/master/CONTRIBUTING.md
The git development repository is here: http://github.com/aspiers/mysqldiff/
Please only submit patches via github pull requests.
Even better, if you feel that you can contribute code, there is a git repository available to make it easy for people to do friendly forks which could eventually get merged back into my releases. If you have patches, please read 7 principles for contributing patches to software projects, and then use git to make your patches available on github via pull requests.
Thanks a lot!
Here are some common-sense guidelines for maximising the chance of your patch being accepted:
- DON'T submit a patch without first checking the bug tracker to see if someone else has already worked on the same issue.
- Each patch should be a logical set of changes, containing not only code changes but any corresponding changes to tests and documentation.
- Don't mix different issues within the same patch.
- Write a good commit message that makes it clear what the patch does.
- If you have a series of patches which are related and cumulatively inter-dependent, submit them as a separate git branch.