From 7188b1f264a136dba17ac0fdb27bee3d173b3a68 Mon Sep 17 00:00:00 2001 From: prescience Date: Mon, 19 Nov 2001 04:43:43 +0000 Subject: [PATCH] Added rules.php3 for developer guidelines git-svn-id: http://mantisbt.svn.sourceforge.net/svnroot/mantisbt/trunk@511 f5dc347c-c33d-0410-90a0-b07cc1902cb9 --- cvs.php3 | 2 +- rules.php3 | 38 ++++++++++++++++++++++++++++++++++++++ side_menu.php3 | 1 + 3 files changed, 40 insertions(+), 1 deletion(-) create mode 100644 rules.php3 diff --git a/cvs.php3 b/cvs.php3 index f9facd8..83884c4 100644 --- a/cvs.php3 +++ b/cvs.php3 @@ -2,7 +2,7 @@ CVS

-Mantis uses CVS to store and control its source code. Anonymous cvs access allows anyone to download the most current snapshot of the code. Warning: the latest build may not always function correctly. I will *not* support CVS snapshots. Only use this is you feel confident in being able to deal with any problems that will arise. +Mantis uses CVS to store and control its source code. Anonymous cvs access allows anyone to download the most current snapshot of the code. Warning: the latest build may not always function correctly. I will *not* support CVS snapshots. Only use this if you feel confident dealing with any problems that arise.

Follow the link and follow the commands there. The module name you want to use is mantisbt.

diff --git a/rules.php3 b/rules.php3 new file mode 100644 index 0000000..484595c --- /dev/null +++ b/rules.php3 @@ -0,0 +1,38 @@ + + +Rules for Development +

+

+ +Coding Style +

+Please follow the Mantis Coding Conventions. + +

+CVS commits +

+Please keep comits short and focused. Ideally you would check in all the files affects by your change(s) at one time. You should try to commit after every bugfix or feature addition. Make sure your commit note tells enough so that another developer (familiar with the project) can make sense of what changes were made. Information might include files, functions, and variables that were modified. +

+eg. cvs ci -m "Modified view_all_bug page so that column alignment is better across browsers" view_all_bug_page.php3 +

+Occasionally you can make do with a trivial message like "updates for release" or "tweaked formatting". This might be when you update the Changelog, or reformatted and cleaned up code, etc. + +

+Communication +

+Please use the mantisbt-dev mailing list or forums. You can monitor forums so that every post is emailed to you. This way there is a public record of development. If you have a matter you would like to discuss in private them emailing me directly is fine. + +

+Testing +

+In general I would prefer that you test using at least two browsers. This way most browser dependencies can be caught. I recommend testing with Internet Explorer and Mozilla. This captures the vast majority of actual users. Others that might be considered are Opera, Netscape, Konqueror, and OmniWeb. + +

+Other rules +

+Make sure you signup on the bugtracker and received developer access. +

+You can mark a bug as resolved if it is commited in CVS. Please don't close bugs until that release is publicly available. +

+ + \ No newline at end of file diff --git a/side_menu.php3 b/side_menu.php3 index 2549450..582a3d8 100644 --- a/side_menu.php3 +++ b/side_menu.php3 @@ -112,6 +112,7 @@ Getting Started
Coding Guidelines
+ Developer Rules
Dev Notes
Roadmap
Polls