Requirement #6948 (closed)
Opened 13 years ago
Closed 12 years ago
Working with code base
| Reported by: | jburel | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4.7 |
| Component: | General | Keywords: | n.a. |
| Cc: | jamoore, cxallan | Business Value: | n.a. |
| Total Story Points: | n.a. | Roif: | n.a. |
| Mandatory Story Points: | n.a. |
Description (last modified by jmoore)
Umbrella ticket for defining
- code style/policy.
- enforcing copyright.
- Define header of files.
- define how to work with github
- how to work with tools like Eclispe, Pycharm
- etc.
Build process (previously #6951)
- integration of insight build. see #3940
- training material
- where to put it.
- maintenance.
- when to build
- etc.
- Let devs only build they need e.g. B-F, insight
Branch merging (previously #6934)
- 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.
- 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.
See #2125. Those stories should likely be added here as tickets.
Change History (5)
comment:1 Changed 13 years ago by jburel
- Summary changed from How to work code base to How to work with code base
comment:2 Changed 13 years ago by jburel
- Summary changed from How to work with code base to Working with code base
comment:3 Changed 12 years ago by jburel
- Milestone changed from OMERO-Beta4.4 to Future
comment:4 Changed 12 years ago by jmoore
- Description modified (diff)
- Milestone changed from Future to OMERO-Beta4.4.x
- Priority changed from minor to major
comment:5 Changed 12 years ago by jmoore
- Resolution set to duplicate
- Status changed from new to closed
Moved all content to #6380. Closing duplicate.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moving to Future, some actions completed but some will take longer.