I realized that the indent after line-wrapping setting was wrong in
the Eclipse code style preferences file that I posted. I set it to
"8", thinking that meant 8 spaces, but it looks like it was actually
interpreted as 8x the normal indent, so 16 spaces. That's way too
much and caused some reall
[ http://issues.apache.org/jira/browse/UIMA-62?page=all ]
Adam Lally updated UIMA-62:
---
Fix Version/s: 2.1
> Provide an example CasMultiplier that merges CASes
> --
>
> Key: UIMA-62
>
[ http://issues.apache.org/jira/browse/UIMA-66?page=all ]
Adam Lally reassigned UIMA-66:
--
Assignee: Eddie Epstein (was: Adam Lally)
Assigning to Eddie for review since I believe he is the most interested in
using a merger.
> Create example SimpleTextMerg
[ http://issues.apache.org/jira/browse/UIMA-67?page=all ]
Adam Lally resolved UIMA-67.
Fix Version/s: 2.1
Resolution: Fixed
Assignee: Eddie Epstein (was: Adam Lally)
Implemented the appropriate Flow Control for the example aggregate that doe
[ http://issues.apache.org/jira/browse/UIMA-69?page=all ]
Adam Lally closed UIMA-69.
--
website looks ok now
> update website with SVN commit comment guidelines for JIRA issue tracker
>
>
>
On the general @ incubator list, robert burrell donkin wrote:
good open source release notes tend to have a different tone from
close source ones
one major aim of the release notes should be to encourage downstream
users (and in particular packagers) that your product is important and
interesti
Michael Baessler wrote:
To just inform the other UIMA committers about an absence, I think we
can also use the private
UIMA mailing list. This list is only distributed to the committers, right?
+0. In addition to committers, our Mentors and perhaps other Apache PMC
members can see the private
Marshall Schor wrote:
I don't feel strongly but have a slight preference for this kind of
info to be communicated via email.
This is for 2 reasons:
1) it needs to be read in a timely way - and email is more timely
than wiki reading. (although people might
subscribe to wiki changes)
Thilo Goetz wrote:
All,
if we want to cut a release early next year, we need to get all our
ducks in a row. My impression from following incubator-general is
that getting the release right is a *lot* of work. It is common
practice in Apache projects to have a release manager that takes care
[ http://issues.apache.org/jira/browse/UIMA-69?page=all ]
Michael Baessler resolved UIMA-69.
--
Resolution: Fixed
> update website with SVN commit comment guidelines for JIRA issue tracker
>
[
http://issues.apache.org/jira/browse/UIMA-69?page=comments#action_12453841 ]
Michael Baessler commented on UIMA-69:
--
We can do both add the issue ID and add the whole link. But the issue ID must
occur separate from the link since otherwis
[ http://issues.apache.org/jira/browse/UIMA-69?page=all ]
Work on UIMA-69 stopped by Michael Baessler.
> update website with SVN commit comment guidelines for JIRA issue tracker
>
>
> Key: UIMA-69
>
[ http://issues.apache.org/jira/browse/UIMA-69?page=all ]
Work on UIMA-69 started by Michael Baessler.
> update website with SVN commit comment guidelines for JIRA issue tracker
>
>
> Key: UIMA-69
>
13 matches
Mail list logo
