-
Notifications
You must be signed in to change notification settings - Fork 35
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
Comments
ghost
assigned yegor256
Apr 21, 2013
migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 4:06pm risk #72 added |
migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 4:06pm Enough risks for now, the task is closed. |
migrated from Trac, where originally posted by yegor256 on 23-Nov-2011 9:06am Milestone JUN11 deleted |
This was referenced Apr 21, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: