Re: Introduction before commit.
peter-4lf8KW9E9MLMqX/[email protected] Tue, 28 Oct 2003 14:23:27 +1100
| Newsgroups | gmane.comp.java.spice.devel |
|---|---|
| Message-ID | <02ad01c39d02$daa24970$21e7809d@fisg2> |
Hi, From: "Ryan Hoegg" <[email protected]> > I wanted to introduce myself before you guys starting seeing random > commit messages from me. So, hi! Hi! > Seems like theres lots of little independent projects here, so I wanted > to make sure I understood the common courtesies. Don't commit on > something without talking to people first? Depends on what you are doing (and how well the codebase is unit tested) but thats generally a good idea. Non-design changes are generally ok as long as everything still passes unit tests but design changes should definetly be talked about. > Chat about it on -devel > before adding anything to /components? Anything else? yep! Basically anything that is migrated to components should be really well unit tested, stable and generally fairly solid. ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/