Opened 17 years ago
Closed 16 years ago
#33 closed task (fixed)
structure subversion for mainline and CABB enhancement
| Reported by: | VincentMcIntyre | Owned by: | VincentMcIntyre |
|---|---|---|---|
| Priority: | major | Milestone: | 6. Branch code, project tracker set up |
| Component: | miriad4cabb project | Version: | |
| Keywords: | Cc: | ||
| Estimated Number of Hours: | Add Hours to Ticket: | 0 | |
| Billable?: | no | Total Hours: | 3.0 |
Description
We need to structure the repository so it can handle the mainline and various enhancement branches, such as for project 106.
An important aspect of the structure is merging changes from those branches back into the mainline. Is it important to be able to pull bug fixes from mainline to the development tree?
Change History (4)
comment:1 Changed 17 years ago by
| Billable?: | unset |
|---|---|
| Component: | Subversion → miriad4cabb project |
comment:2 Changed 16 years ago by
| Status: | new → assigned |
|---|
comment:3 Changed 16 years ago by
| Add Hours to Ticket: | → 1 |
|---|---|
| Total Hours: | 0 → 1.0 |
oops, link should be Meetings/20071123
comment:4 Changed 16 years ago by
| Add Hours to Ticket: | 0 → 2 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
| Total Hours: | 1.0 → 3.0 |
After a bit of discussion the usual trunk/, tags/, branches/ structure seems sufficient. Some thought and work was required to set permissions on the repository so that developers can only update branches, while "powerusers" and "admins" can manipulate trunk/ and tags/ as well.
Note: See
TracTickets for help on using
tickets.
discussed this at 2007-11-23 weekly meeting?