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:
-
07/04/12 13:46:32 (12 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Priority
changed from
minor
to
major
-
Property
Milestone
changed from
OMERO-Beta4.4
to
OMERO-Beta4.4.x
-
Property
Summary
changed from
How to work code base
to
Working with code base
-
|
initial
|
v4
|
|
| 6 | 6 | * how to work with tools like Eclispe, Pycharm |
| 7 | 7 | * etc. |
| | 8 | |
| | 9 | Build process (previously #6951) |
| | 10 | * integration of insight build. see #3940 |
| | 11 | * training material |
| | 12 | * where to put it. |
| | 13 | * maintenance. |
| | 14 | * when to build |
| | 15 | * etc. |
| | 16 | * Let devs only build they need e.g. B-F, insight |
| | 17 | |
| | 18 | Branch merging (previously #6934) |
| | 19 | * 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. |
| | 20 | * 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. |
| | 21 | |
| | 22 | 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.12126 sec.)
