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.

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

to identify 5 most critical technical risks/concerns #2

Closed
yegor256 opened this issue Apr 21, 2013 · 5 comments
Closed

to identify 5 most critical technical risks/concerns #2

yegor256 opened this issue Apr 21, 2013 · 5 comments
Assignees

Comments

@yegor256
Copy link
Owner

migrated from Trac, where originally posted by yegor256 on 7-Sep-2010 10:35am

We should identify 5 most critical concerns about possible design/architecture. Every concern has to be documented in a separate ticket.

@ghost ghost assigned yegor256 Apr 21, 2013
@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 8-Sep-2010 2:31pm

risks #3, #4, #5, #6, and #7 are identified

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 9-Sep-2010 12:11pm

risks #10, #11, #12 are identified

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 4:06pm

risk #72 added

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 4:06pm

Enough risks for now, the task is closed.

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 23-Nov-2011 9:06am

Milestone JUN11 deleted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant