Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactoring of specific code areas (load nexus algorithms) - investigate and distribute #12591

Closed
NickDraper opened this issue May 13, 2015 · 2 comments
Closed

Refactoring of specific code areas (load nexus algorithms) - investigate and distribute #12591

NickDraper opened this issue May 13, 2015 · 2 comments
Assignees
@martyngigg
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@NickDraper
Copy link
Contributor

This issue was originally TRAC 11753

Identify areas of code that are in severe need of refactoring (e.g. LoadEventNexus).

If there are more that NEED attention than you can handle yourself then talk through a shopping list with Nick

Keywords: Maintenance
@NickDraper NickDraper added Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@NickDraper NickDraper added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestone: Release 3.6 Jan 22, 2016
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@stale
Copy link

stale bot commented Mar 3, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martyngigg martyngigg

Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martyngigg @NickDraper