Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
09/25/12 10:54:04 (12 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Milestone
changed from
OMERO-Beta4.3.2
to
OMERO-Beta4.4.x
-
|
v1
|
v4
|
|
| 2 | 2 | |
| 3 | 3 | See #6296 |
| | 4 | |
| | 5 | == Content copied from #6948 "Working with code base" == |
| | 6 | |
| | 7 | Umbrella ticket for defining |
| | 8 | * code style/policy. |
| | 9 | * enforcing copyright. |
| | 10 | * Define header of files. |
| | 11 | * define how to work with github |
| | 12 | * how to work with tools like Eclispe, Pycharm |
| | 13 | * etc. |
| | 14 | |
| | 15 | Build process (previously #6951) |
| | 16 | * integration of insight build. see #3940 |
| | 17 | * training material |
| | 18 | * where to put it. |
| | 19 | * maintenance. |
| | 20 | * when to build |
| | 21 | * etc. |
| | 22 | * Let devs only build they need e.g. B-F, insight |
| | 23 | |
| | 24 | Branch merging (previously #6934) |
| | 25 | * In order to have continuous integration of active branches before they are merged into develop, we will need to have jobs which take properly marked branches from all github forks, merge them into a single branch, and then test that branch. |
| | 26 | * Moving to future for us to investigate when we again have multiple branches / PRs all simultaneously active. The hope would be that such a build would prevent us from having to manually push to merge-green / merge-blue. Any merge failures would be detected immediately. |
| | 27 | |
| | 28 | See #2125. Those stories should likely be added here as tickets. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.12835 sec.)
