So, I know we've kinda covered this ground before, but is there really no way for us to release now even if it's only on rollerweblogger.org?
Saying that they are going to talk about it next Wednesday is good, but like you said, that doesn't guarantee any decisions. We are getting *way* too far behind to continue to let the weeks slip by. It's already been 4 months since our last release and we basically have two completed releases finished and waiting to be let out. On top of that we are already well into Roller 2.1 development and I am expecting that in the next week or so we should be committing Roller 2.1 code to the trunk. I hate to be pushy about this because I do not want to back out of the incubator, but we have to make a decision. This problem is now starting to inhibit our ability to work on the project. -- Allen On Thu, 2005-11-10 at 19:59, Henri Yandell wrote: > Just an update on the LGPL issue. > > Various discussions on [EMAIL PROTECTED] about whether Roller can release > with LGPL dependencies. > > One thing that's pretty clear is that we'll have to ditch the LGPL'd > jars in SVN (and the BCL'd ones). It's ASF policy to have only ASF > licensed works within the source repositories; and I can't think of > any examples to the contrary. > > Hopefully we can make the releases before complicating things by > removing the jars. > > One item of note; the board are meeting next week (Wednesday at a > guess) and the LGPL issue is on the agenda, though I don't think items > have to be cleared off the agenda each time so that's not a guarantee. > > Hen
