View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002519 | Slicer4 | Core: Building (CMake, Superbuild) | public | 2012-09-13 14:15 | 2014-03-07 10:51 |
Reporter | jcfr | Assigned To | jcfr | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | |||||
Target Version | Slicer 4.4.0 | Fixed in Version | Slicer 4.4.0 | ||
Summary | 0002519: Discuss with the community and setup a branchy workflow | ||||
Description | From Sankhesh: I suggest setting up a branchy-workflow for Slicer where changes are submitted to a "next" branch and dashboard testing is done on this branch as well. Once, the dashboard is green for a particular changeset in "next", it can be merged into master. This ensures a stable development HEAD and allows addition of bug-fixes and features with least regression. Currently, we can test our topics only on a certain configuration(e.g. I just have a laptop with Ubuntu 12.04 and gcc-4.6.3). This does not allow me to catch all regression errors before merging to HEAD. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2012-09-13 14:15 | jcfr | New Issue | |
2012-09-13 14:15 | jcfr | Status | new => assigned |
2012-09-13 14:15 | jcfr | Assigned To | => jcfr |
2012-09-13 14:15 | jcfr | Target Version | => Slicer 4.3.0 |
2012-09-13 14:16 | jcfr | Relationship added | parent of 0002059 |
2012-09-13 14:18 | jcfr | Relationship added | parent of 0002520 |
2012-09-14 05:26 | jcfr | Assigned To | jcfr => sankhesh |
2013-04-01 10:21 | jcfr | Assigned To | sankhesh => jcfr |
2013-08-27 11:41 | jcfr | Target Version | Slicer 4.3.0 => Slicer 4.4.0 |
2014-03-07 10:50 | jcfr | Relationship replaced | child of 0002059 |
2014-03-07 10:51 | jcfr | Relationship replaced | related to 0002520 |
2014-03-07 10:51 | jcfr | Status | assigned => closed |
2014-03-07 10:51 | jcfr | Resolution | open => fixed |
2014-03-07 10:51 | jcfr | Fixed in Version | => Slicer 4.4.0 |