Task #137 (closed)
Opened 18 years ago
Closed 15 years ago
Move development related tiki pages to trac.
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | trivial | Milestone: | OMERO-Beta4 |
Component: | Trac | Version: | 3.0-M1 |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
This will help linking source code/changesets/tickets etc. Tiki pages then become more user oriented, and trac pages more developer oriented. Later tiki pages can be written up for the website.
See:
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Keywords iteration4 added
- Milestone changed from Unscheduled to cycle1
comment:2 Changed 18 years ago by jmoore
- Keywords iteration4 removed
- Milestone changed from 3.0-M2 to Unscheduled
comment:3 Changed 15 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4
- Resolution set to fixed
- Status changed from new to closed
This was done at the end of 2008.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Omero+Releases has been updated to contain links into the trac milestones. However, the tiki pages need to stay for more visibility. Perhaps we can come up with some reasonable separation of responsibilities.
Shelving this for a later date.