On 05/06/12 14:44, Richard Eckart de Castilho wrote: >>> - uimaFIT will maintain its own release cycle. >> >> I'd like to understand why this point is important to you. It seems >> to me our goal should be an integration of uimaFIT with the rest of >> UIMA, so why this insistence on a separate release cycle? >> >> Just to be clear, there will be nothing keeping you from making as >> many releases as you like (other than the usual community back and >> forth). > > DKPro Core and ClearTK are strong drivers behind uimaFIT and have their own > release cycles. If we run into issues or need a new feature in uimaFIT, we > would like to be able to resolve it in a timely manner, in particular if > releases of these products depend on it. It makes little sense to ask for > a full add-ons release every time. > > Mind, that we did not and do not implement project-specific features or > specific hacks in uimaFIT, but it may well be that these projects are the > first ones that require a new general functionality. E.g. movements in > DKPro Core, DKPro Lab and DKPro Spelling have driven forward the development > of the external resources code in uimaFIT and the DKPro projects were the > first to use this feature. > > Likewise, if any other project requires a bug fix or new feature which > may only be available in SVN at the time, we would like to be able to > react to that by making a new release without much delay.
Makes sense, thanks for explaining. As long as somebody is able and willing to do the work required for a release, that should not be an issue. --Thilo
