On Tue, Oct 25, 2016 at 12:37 AM, sblackmon wrote:
> Wanted to send a general internal progress report, from my perspective.
>
> Per https://issues.apache.org/jira/issues/?filter=12338530 0.4-incubating
> resolves/closes
> 50 issues. Some of them impacted 5 or more modules.
>
Can't access that
Wanted to send a general internal progress report, from my perspective.
Per https://issues.apache.org/jira/issues/?filter=12338530 0.4-incubating
resolves/closes 50 issues. Some of them impacted 5 or more modules.
Record participation, which will be quantified in the incubator report shortly.
Steve Blackmon shared a search result with you
-
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+STREAMS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+0.5+ORDER+BY+priority+DESC
--
This message was sent
Steve Blackmon shared a search result with you
-
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+STREAMS+and+fixVersion+%3D+0.4
JIRA Query: project = STREAMS AND fixVersion = 0.4
--
This message was sent by
+1 binding
On October 24, 2016 at 12:41:19 AM, Suneel Marthi (suneel.mar...@gmail.com)
wrote:
+1 binding
On Mon, Oct 24, 2016 at 1:07 AM, sblackmon wrote:
>
> I've created a combined 0.4-incubating release candidate, with the
> following artifacts up for a vote:
>
> incubator-streams-mas
On Mon, Oct 24, 2016 at 3:26 PM, sblackmon wrote:
> Hello,
>
> 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 / altera
Hello,
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
(a) +1 for sure.
STREAMS-348: Create coding guidelines document for website
STREAMS-349: Maven plugin that can validate all classes have a sensible javadoc
header
STREAMS-350: Bring codebase into compliance with requirement for sensible
javadoc headers.
(b) +1 I think.
I agree with minimizin
(1) We could start with a bare minimum ground rules For FindBugs and refine
those as we move along.
(2) CheckStyle is a good idea -
- do we wanna 2 spaces or 2 tabs as beginning of each line, my
personal pref is 2 spaces (and no tabs)
On Mon, Oct 24, 2016 at 1:20 PM, Timothy Spann
wro
That makes a lot of sense.
Maybe run FindBugs, PMD and CheckStyle.
I had 2 things in mind that we need to work in tandem with adding/improving
functionality in Streams.
(a) Remove author info from all code that has it, and add sensible JavaDocs
for each class
(b) Now that we are officially Java 8, minimize Guava API use and migrate
most Guava stuff to Java 8 whe
11 matches
Mail list logo
