| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:new_developers [2009/08/14 02:36]
michael |
dev:new_developers [2009/08/14 02:42]
michael |
| One common source of breakage is where one developer adds new files that are called on by other files, and forgets to add those files before committing changes. Now, thank you very much, the entire repository is broken for everyone. It is especially obnoxious when someone does this right before going to bed, or to work, or worst of all, on vacation/holiday, where they can't be reached to correct the problem for hours or days. | One common source of breakage is where one developer adds new files that are called on by other files, and forgets to add those files before committing changes. Now, thank you very much, the entire repository is broken for everyone. It is especially obnoxious when someone does this right before going to bed, or to work, or worst of all, on vacation/holiday, where they can't be reached to correct the problem for hours or days. |
| |
| Another common source of breakage is where one developer fires off a few incidental lines of code without testing to notice that they cause the entire application to crash at startup, or they break the notation editor completely, etc. This kind of thing is impossible to avoid completely, but making a reasonable to do some sanity checking before a commit is a good neighbor policy. | Another common source of breakage is where one developer fires off a few incidental lines of code without testing to notice that they cause the entire application to crash at startup, or they break the notation editor completely, etc. This kind of thing is impossible to avoid completely, but making a reasonable effort to do some sanity checking before a commit is a good neighbor policy. |
| |
| If your work is highly likely to cause problems for other developers while it is under way, then please consider doing the work in a branch instead. See [[Branching|Working with branches]]. | If your work is highly likely to cause problems for other developers while it is under way, then please consider doing the work in a branch instead. See [[Branching|Working with branches]]. |
| |
| If you're not already subscribed to rosegarden-bugs@lists.sourceforge.net you should consider subscribing. This list tracks activity from bug reports, feature requests, commits, and changes to the wiki all in one place, and a lot of things go on which you can keep up with through rosegarden-bugs but might get no hint of if you only follow rosegarden-devel and rosegarden-user. | If you're not already subscribed to rosegarden-bugs@lists.sourceforge.net you should consider subscribing. This list tracks activity from bug reports, feature requests, commits, and changes to the wiki all in one place, and a lot of things go on which you can keep up with through rosegarden-bugs but might get no hint of if you only follow rosegarden-devel and rosegarden-user. |
| | |
| | ===== The Wiki ===== |
| | |
| | You've found the wiki. While you're here, you should create an account. We use the wiki for all kinds of things, such as user documentation, development notes, electronic napkin drawings, and so on. You might want to have a look from the main page to see how it's all laid out, and if you have any grand ideas about how we can make the wiki better and more productive, then please jump in. I feel like it all has a lot more potential than anything it has really lived up to so far. |
| | |
| | Most particularly, I'd be very interested in porting all of our user documentation to this wiki. |
| | |
