Home

Version 199 (Sickboy, 03/18/2010 11:00)

1 1 admin
h1. A.C.E
2 135 Sickboy
3 135 Sickboy
{{>TOC}}
4 97 Sickboy
5 179 Sickboy
!http://pufu.kellys-heroes.eu/signature4.png!:http://updater.dev-heaven.net/main
6 179 Sickboy
!http://updater.dev-heaven.net/images/stats.png!:http://updater.dev-heaven.net/stats
7 126 Sickboy
8 126 Sickboy
Welcome to the A.C.E. Advanced Combat Environment Mod for ArmA 2!
9 125 Sickboy
10 199 Sickboy
* "*Documentation WIKI (Howto/FAQ/etc)*":http://ace.dev-heaven.net
11 170 Sickboy
12 198 Sickboy
* "BI Forums, v1.0 Stable Thread":http://forums.bistudio.com/showthread.php?t=96371
13 144 Sickboy
* "BI Forums, Beta 2 Thread":http://forums.bistudio.com/showthread.php?t=92466
14 143 Sickboy
* "BI Forums, Beta 1 Thread":http://forums.bistudio.com/showthread.php?t=91500
15 97 Sickboy
* "BI Forums, Discussion Thread":http://forums.bistudio.com/showthread.php?t=73531
16 97 Sickboy
17 180 rocko
h1. Reporting issues, bugs, feedback
18 136 Sickboy
19 194 Sickboy
Please check the following link: [[Bugz]]
20 136 Sickboy
21 97 Sickboy
22 177 Sickboy
h1. Development
23 171 Sickboy
24 189 Sickboy
h2. AllInOneConfig
25 189 Sickboy
26 189 Sickboy
http://dev-heaven.net/issues/9108
27 189 Sickboy
28 190 Sickboy
h2. Function Documentation
29 1 admin
30 1 admin
* "ACE":http://dev-heaven.net/docs/ace/index.html
31 193 Sickboy
* "CBA":http://dev-heaven.net/docs/cba/index.html
32 193 Sickboy
** "Generic Functions and Macros Doc":http://dev-heaven.net/projects/cca/wiki/Function_and_Macro_Libraries
33 1 admin
34 190 Sickboy
h2. Workflow
35 192 Sickboy
36 192 Sickboy
h3. Goals / Scope
37 192 Sickboy
38 192 Sickboy
http://ace.wikkii.com/wiki/Goals_and_Scope_of_ACE
39 1 admin
40 191 Sickboy
h3. Versioning
41 191 Sickboy
42 188 Sickboy
Currently: MAJOR.MINOR.PATCHLVL.BUILD
43 195 Sickboy
x.x.0 is (Pre) Release Candidate
44 195 Sickboy
x.x.1+ is Release Candidates, where the first one stable enough, is "The Stable Release"
45 1 admin
46 177 Sickboy
h3. Coordinated work
47 177 Sickboy
48 171 Sickboy
Noone can bear the whole mod development on it's own.
49 171 Sickboy
In that regard it appears to be useful to coordinate workflow to achieve current tasks.
50 171 Sickboy
51 171 Sickboy
_*Personal ticket*_
52 171 Sickboy
For better overview if a developer plans to work on a certain feature (further called feature X) there should be a TASK ticket created with detailed information about the feature component and who is going to work on it as main author.
53 171 Sickboy
54 171 Sickboy
_*Skype announcement*_
55 171 Sickboy
Addtionally the author should inform other developers in the Skype groupchat about the creation of the ticket, so developers are aware of it and can respond to the ticket if needed.
56 171 Sickboy
57 171 Sickboy
Responds can include:
58 171 Sickboy
- Notification about a similar (maybe unknown) project already going on
59 171 Sickboy
- Stating ones interest in the project and asking for participation
60 171 Sickboy
61 171 Sickboy
_*Sharing tasks*_
62 1 admin
Due to the nature of hobbiest developing it should become common sense to ask for help or support, rather than trying to achieve a certain goal all alone.
63 171 Sickboy
64 171 Sickboy
The benefits of sharing tasks are:
65 171 Sickboy
- Faster achievement of a goal
66 171 Sickboy
- Less workload
67 171 Sickboy
- Bug hunting during design
68 1 admin
- Feedback during design
69 1 admin
70 178 Sickboy
h3. Documentation
71 178 Sickboy
72 178 Sickboy
Each feature should be documented. At least it's description. But especially usage information, if applicable.
73 182 Sickboy
Once a component is added to the repository, basic documentation should be up in approx. 2 weeks. Write it up yourself, or ask the document maintainers to help.
74 178 Sickboy
75 171 Sickboy
76 177 Sickboy
h3. Bugs
77 171 Sickboy
78 171 Sickboy
Insufficient bug reports that lack of RPT, reproduction steps or anything else that would be needed to fix, are replied with the general wiki page about bugs.
79 171 Sickboy
Reference: http://dev-heaven.net/wiki/ace-mod2/Bugz
80 1 admin
81 171 Sickboy
Bugs ideally, if requirements are met, should be assigned to the original author of the component.
82 171 Sickboy
83 1 admin
84 177 Sickboy
h3. Features
85 1 admin
86 171 Sickboy
Features are to be rejected when they don't fit into ACE2 scope. A short explanation is helpful to stress out mismatch with set scope.
87 171 Sickboy
Features are generally free to be assigned to oneself if a certain feature attracts a developers liking.
88 171 Sickboy
If a feature fits ACE, but is not possible due to *lack of resources*, the ticket should be added to the Future Milestone, and set to Low priority.
89 1 admin
90 177 Sickboy
h3. Blocked
91 1 admin
92 171 Sickboy
If certain tickets are not able to be completed, before others are done, please don't reject these tickets but set the blocking ticket to 'blocks' this ticket.
93 171 Sickboy
If more tickets appear about the same, set them to Duplicate, and not Rejected :)
94 171 Sickboy
95 177 Sickboy
h3. Expired
96 171 Sickboy
97 1 admin
When tickets are set to feedback, if there is no response within 14 days, the ticket is set to Expired.
98 171 Sickboy
99 171 Sickboy
_Tracker clearance_
100 171 Sickboy
101 171 Sickboy
To avoid abandoned tickets or identify possible expired tickets, it would be useful to set a due date to each ticket once it is created.
102 172 Sickboy
Due date should cover the 14 days timespan (to help filtering), so tickets that are theoretically due and have little to no useful feedback can be set to expired.
103 171 Sickboy
104 177 Sickboy
h3. Rejected
105 171 Sickboy
106 171 Sickboy
Rejecting tickets should be done with a short explanation or at the very least; reason.
107 171 Sickboy
Rejected tickets should disappear from the Roadmap. So please remove version on reject.
108 197 Sickboy
109 197 Sickboy
110 197 Sickboy
h2. Developers
111 197 Sickboy
112 197 Sickboy
"Devs":http://dev-heaven.net/projects/ace-internal/wiki/Developers