Re: [weaver] next steps

Hi Matt, 2013/8/13 Matt Benson > Benedikt, I take your point about prematurely promoted components, and as > one of the primary remaining participants in [functor] I take > responsibility for that; however the promotion was made in good faith only > last-minute discussions about the API (like th

Re: [weaver] next steps

Benedikt, I take your point about prematurely promoted components, and as one of the primary remaining participants in [functor] I take responsibility for that; however the promotion was made in good faith only last-minute discussions about the API (like the suggestion I carefully offered wrt CSV)

Re: [weaver] next steps

I'm not saying that we cannot promote it. I'm just saying that we should only promote it if it is ready to be released. 2013/8/13 Romain Manni-Bucau > Hi > > I think the point with weaver is more that some other apache projects (bval > for instance) needs it for next release. > > *Romain Manni-

Re: [weaver] next steps

Hi I think the point with weaver is more that some other apache projects (bval for instance) needs it for next release. *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http:/

Re: [weaver] next steps

Hi, I haven't been working on weaver so I cannot really comment on it's state. IMHO it's important that we only promote components to proper that are very close to a release. We have several components in proper that I think have been promoted to early. Examples are: csv, functor, imaging. After