streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sblackmon <>
Subject [DISCUSS] planning, categorizing, commencing issues in JIRA
Date Mon, 24 Oct 2016 19:26:25 GMT

Thanks to a lot of fresh attention recently (thanks Joey, Suneel) we’re down to ~50 Open
issues without a FixVersion.

There are a few themes:
- problems with streams-runtime-local / streams-monitoring
- improvements / alterations to schemas / data handoff patterns
- new / better providers and persisters
- documentation / website / examples
- other bugs

Additionally, there’s are a few big topics being tossed around that need to be scoped and
prioritized, such as
- Activity Streams 2.0
- changing core interfaces
- new runtimes
- streams API
- streams UI

Specifics aside,

Does anyone else see a need to start tagging issues with epics and/or components and/or labels?
 Preferences on how?

Does anyone have suggestions on how to start formalizing, breaking down, and scheduling these
larger efforts?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message