Hello. > > It thus becomes urgent to tackle the remaining blocking issues. > > Can we please make a list of those, and of all practical matters that > > prevent the preparation of the release? > > > > > > Thanks and best regards, > > Gilles > > > As far as I'm concerned, I have been concentrating recently on > MATH-677 and MATH-722. However, both issues are non-blocking, because > I don't foresee any interface change now (regarding MATH-677, exposing > the complex roots would just be a feature addition, as it is a private > class right now). MATH-722 would merely be a bug correction.
It was my impression that an identified bug is a blocking issue. Is it difficult to solve? If so, maybe that we can postpone it, and add a warning in the release notes (?). > There is one thing I would like to reshape a little bit : that's the > interface for IterativeLinearSolvers, which I found (after having used > it) poorly designed. As this is blocking, maybe I should concentrate > on this issue right now ? This, in my opinion, is not blocking. Maybe the design must be improved (as your own usage has shown already, it seems) but it could be done in 4.0. This design issue should not delay the release of 3.0. Of course, you can do whatever changes you think would be for the better. :-) > Otherwise, I'm available for anything that would take us nearer to > releasing 3.0 (how exciting! First release since I joined!). Same for me (first _major_ release). Those who know what must be done, could you please post here some pointers to a document that decribe the currently recommended and necessary steps for preparing a release? Thanks, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
