streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Blackmon <>
Subject Re: Planning for 0.6 release
Date Fri, 30 Mar 2018 15:12:28 GMT
 Thanks everyone who peer reviewed the changes that we merged in over the
last week.

I think we’re ready to get started on a release?  The three remaining
tickets in Sprint 0.6.0 can be done in tandem with the release.

Anyone want to volunteer for release manager?


On Feb 15, 2018 at 11:29 AM, Steve Blackmon <> wrote:


We’ve made some big changes that I think warrant another release.

- Incorporate streams-examples into apache-streams repo
- Revamped streams-config for more flexibility and ease of use

I’d like to also try to incorporate the following in this cycle and plan to
implement this month:

STREAMS-581: Add and Implement 'FullArchiveSearch' interface in
streams-provider-twitter (
STREAMS-578: Add and Implement 'AllAccountActivity' interface in
streams-provider-twitter (
STREAMS-584: Upgrade to Juneau 7.1.0 (
STREAMS-551: Add a distribution binary and container (

There is an immediate opportunity supporting Apache Kibble with social
media data once we have released a binary / container.

In order to do a binary release we need to do (at least) the following:

STREAMS-501: build a full dependency license report (
STREAMS-479: build comprehensive NOTICE file(s) including all transitive
dependencies (

There are also plenty of simple changes on the JIRA board that could be
wrapped up in the next month and incorporate in 0.6 as well (hint hint):

STREAMS-514: Scope scala-lang and scala-reflect optional in streams-pojo (
STREAMS-573: Change default scala from 2.10 to 2.11 (
STREAMS-554: Intermittent failure in (
STREAMS-503: MediaLink class is not being generated in streams-pojo (
STREAMS-577: Evaluate Streams TLP Website Check (
STREAMS-576: Generate svg diagrams for website with maven, rather than with
a manual step (
STREAMS-487: Test data originating within modules, used in other modules,
should be a stand-alone artifact. (

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