|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as PEND... Damon Smith (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Colin Vipurs (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... JIRA
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Damon Smith (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-573) Step Marked as... Mauro Talevi (JIRA)
Some of us actually do work the way JBehave was intended and to suggest otherwise is disingenuous at best and plain arrogant at worst. When writing new stories we want them in source control and CI even though they haven't been implemented yet and absolutely do not want them breaking the build.