Ticket #5645 (assigned)
Re-categorise PythonAlgorithms
Reported by: | Owen Arnold | Owned by: | Nick Draper |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description (last modified by Nick Draper) (diff)
We have too many python algorithms for them to be categorised purely by the development language they were written in.
I suggest one of the following:
- Completely ignore the fact that the algorithms were written in Python and give them a category that only depends upon what they do.
- Do the above, but also keep them dual categorised as python algorithms too.
@Nick : I'm only writing the ticket so that it's recorded as a useful task to be undertaken. Reassign as required.
Change History
comment:2 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:6 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at the code freeze for R2.6
comment:7 Changed 7 years ago by Nick Draper
- Description modified (diff)
- Milestone changed from Backlog to Release 3.0
comment:8 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.0 to Backlog
Move tickets to Backlog that did not get into R3.0
comment:9 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6491
Note: See
TracTickets for help on using
tickets.
Moved at the end of release 2.2