How to publish patches and upgrades.
If you are capable of coming up with software you can use, and want others to be able to use it also, you probably just need a few reminders of how to cooperate with others:
1. Appropriate languages are sh, perl, C, awk. Don't expect that others will learn another language just to use your tool.
2. If the patch is a defect fix, post a copy to the news.software.nntp newsgroup, and CC
3. If the patch is a feature/enhancement, it is better not to publish the code itself to the newsgroup.
- Include a description of the defect (symptoms, etc)
- Include what versions contain the defect.
- Include a context diff. (Obtained by running diff -c oldfile newfile)
- Publish a description and a pointer to a WWW or FTP site, with a TAR or SHAR file of everything they need.
- Patches should be generated by running diff -c oldfile newfile
- Explain how it differs from what exists, how it is an improvement.
- Describe your experiences with it as a summary in the announcement,
and provide a README with the distribution.
- Include a Known Bug/Limitations list. This serves as a warning, and will cut down on e-mail.
- Note whether it is available without cost, or if it is a commercial product.
- Mention how can you be contacted to provide support or assistance (or not.)
RKT Rapid-Links:[Search] [RKT Tips] Path:Usenet RKT / For Developers / How to improve news / 0048.htm
You are reading from the Usenet RKT
Comments? DocID: USERKT/0048.htm
Copyright 1997, Forrest J. Cavalier III, Mib Software, INN customization and consulting