Hi,
On Fri, Aug 7, 2009 at 10:49 PM, Marshall Schorm...@schor.com wrote:
See this wiki page for info on the release plan:
http://cwiki.apache.org/confluence/display/UIMA/ReleasePlan2.3.0
I was browsing the release plan and noted the following:
After freeze, release candidates will be
Jukka Zitting wrote:
Hi,
On Fri, Aug 7, 2009 at 10:49 PM, Marshall Schorm...@schor.com wrote:
See this wiki page for info on the release plan:
http://cwiki.apache.org/confluence/display/UIMA/ReleasePlan2.3.0
I was browsing the release plan and noted the following:
After freeze,
Hi,
2009/8/26 Thilo Goetz twgo...@gmx.de:
So far, we've always followed that model. I still prefer it,
not least because it forces you to concentrate on the upcoming
release.
OK, sounds good.
You may want to keep this alternative in mind though for future, often
especially in bigger
Jukka Zitting wrote:
Hi,
2009/8/26 Thilo Goetz twgo...@gmx.de:
So far, we've always followed that model. I still prefer it,
not least because it forces you to concentrate on the upcoming
release.
OK, sounds good.
You may want to keep this alternative in mind though for
One way we have to ensure that the uima core generification is
correct is to use our API with generics, thats why I would like to suggest
to move our release a few days and use the time to convert existing
code outside of the core. That could be done after the code freeze.
Jörn
Marshall Schor
+1 I'm for doing testing of the new generification because of the
difficulty of doing this correctly... -Marshall
Jörn Kottmann wrote:
One way we have to ensure that the uima core generification is
correct is to use our API with generics, thats why I would like to
suggest
to move our release
Marshall Schor wrote:
+1 I'm for doing testing of the new generification because of the
difficulty of doing this correctly... -Marshall
What kind of testing do think of ?
Jörn
+1 for an update to uimacpp
On Fri, Aug 7, 2009 at 4:49 PM, Marshall Schorm...@schor.com wrote:
I'd like to freeze in 3 weeks, if that is reasonable. For all of you
with code that you want to have in the release, is 3 weeks (Aug 28 - a
Friday) too soon to freeze (stop developing, and see if
I'd like to freeze in 3 weeks, if that is reasonable. For all of you
with code that you want to have in the release, is 3 weeks (Aug 28 - a
Friday) too soon to freeze (stop developing, and see if we can cut a
release candidate)?
This means:
coding of any new things is done, tests written, and
