Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 14:02:10)
* Windup general progress and priorities (lincolnthree, 14:37:19)
* Our release for Tech Preview is in TWENTY - 20 DAYS. (lincolnthree,
14:37:56)
* This includes documentation for RH associates to learn how to use
windup (lincolnthree, 14:38:20)
* It includes an actually working tool that doesn't run forever :)
(lincolnthree, 14:38:32)
* It must include feature parity with Windup 1 (lincolnthree,
14:38:45)
* It should be possible to write custom rules using our new API (I
think this is working) (lincolnthree, 14:39:12)
* We need: A reference guide, a presentation and a reproducible demo
of usage, as well as a presentation and demo of how to write rules.
(lincolnthree, 14:39:54)
* Those last things will probably be up to sgilda and robbg primarily,
with some help from us. (lincolnthree, 14:40:29)
* Status reports (lincolnthree, 14:04:28) * I have been working on
finishing up the port of visitors from the earlier "cdi" branch of windup
(jsightler, 14:06:20) * I am mostly done, but I am trying to get the class
file metadata over along with at least some method indexing (without too
much of a performance impact) (jsightler, 14:06:29) * Once that is
complete, I will work on putting some of this information into the reports,
and building queries to make the data actually useful (jsightler, 14:06:59)
* I've been working on WINDUP-104 - and have submitted a massive PR
updating about 318 files :p (lincolnthree, 14:09:38) * as part of this
issue, I've also refactored a few things (mostly around dependencies
between addons) (lincolnthree, 14:10:29) * I've also taken the opportunity
to add some tests for the reporting, to assert that we actually generate
something with content (lincolnthree, 14:11:40) * I've also reviewed a
number of PRs and been dealing with some crazy political fallout from our
"1 month release delay" (lincolnthree, 14:12:51) * I'm working on
refactoring of WindupProcessor, GraphContext/Factory, related tests.
(ozizka, 14:17:34) * I've observed interesting forge behavior WRT resolving
artifacts, which confused me a bit when changing between master and my
branch, and rebuilding (ozizka, 14:17:34) * I've also spend a while on CI -
but the job also fails due to the same Forge bug (ozizka, 14:17:34) *
Besides that, I'm documenting how the core works internally. (ozizka,
14:17:34) * I am also going to be working on the XML-config next (because
of some of this political stuff) - should be quick (lincolnthree, 14:20:32)
* Fixed the bug caused by java legacy rules. It is actually fun, because
they pointed out a bug in windup java file processing. The source java
files were not loaded to graph completely (opposed to binary java classes)
(mbriskar, 14:25:02) * XML legacy rules fully merged, however I am
suspicious of some problems caused by a lot of rebases. (mbriskar,
14:26:09) * LINK:
https://github.com/windup/windup/commit/700639f2eec5c7f997d7ee9b19c8e133f...
(jsightler, 14:28:51) * Trying to run the rexster embedded, so even during
the debugging there would be option to see how the graph looks like. This
is questionable, but I want to try (mbriskar, 14:32:38) * and also
implemented an option to run windup execution on one RuleProvider only (the
dependencies get counted).. this however is for discussion.. It is for
testing purposes (mbriskar, 14:34:34)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."