Hey all,
I've created a new jira component, Wicket UI, so we can start dropping the ui
2.0 stuff in there and it does not collides with the old UI one.
it just seemed reasonable to me since by looking at the issues in the UI
modules made it hard to realize which ones relate to the new ui and which
ones to the old.
I also hope to use it as a means of coordination. I know you were extensively
using irc for the sake and I should of been more on, but still if decisions
are taken on irc I feel like it'd be good to write them down as jira issues?
open to comments.
cheers,
Gabriel
Gabriel Roldán ha scritto:
Hey all,
I've created a new jira component, Wicket UI, so we can start dropping the ui 2.0 stuff in there and it does not collides with the old UI one.
it just seemed reasonable to me since by looking at the issues in the UI modules made it hard to realize which ones relate to the new ui and which ones to the old.
I also hope to use it as a means of coordination. I know you were extensively using irc for the sake and I should of been more on, but still if decisions are taken on irc I feel like it'd be good to write them down as jira issues?
Agreed on both the category and the use of jira to turn decisions into tasks
Cheers
Andrea