It was me who brought this up. A couple of years ago, I got educated about this topic by an Apache Member (unfortunately, I don't remember who that was) and from that point on, I didn't allow releases in XML Graphics with snapshot JARs. Indeed, I haven't found any hard evidence myself about this policy so I brought this up among the ASF membership. The discussion is still going on and it's not clear, yet, what the outcome will be. It will probably be somewhere between "no problem with snapshots" and "no go with snapshots". At the moment, just ignore this and I will update you when I can say more. Hopefully, this will result in an update of the release handling documentation on www.apache.org/dev. What I can already say is that releasing Forrest with snapshot JARs means the Forrest PMC takes responsibility for those snapshots and what's in them.
rgardler wrote: > > Thorsten Scherler wrote: >> On Sat, 2007-12-01 at 10:49 +0100, Ferdinand Soethe wrote: >>> An Apache colleague looking at Forrest 0.8 just noticed that >>> we have used unreleased Cocoon Code in our release and told >>> me that this is not longer permitted. >> >> Can this colleague point out the board note or any other resource that >> is stating this. It strikes me odd since we are talking about open >> source whether released or not. Meaning for me I/we can include what we >> want if it is compatible with our license. > > I agree. This just feels wrong and I do not recall seeing any resolution > supporting this view. > > There is nothing (legally speaking) to stop us taking the code from > Cocoon SVN, adding it to our own SVN and releasing it as Forrest code. > Of course forking Cocoon in this way would be bad from a community point > of view. Having a release restriction forcing us to do this would be > contrary to the Apache approach to software development. > > Unless I see some documented evidence of this restriction I have no > problem with continuing with our me of a 2.2 snapshot. if I see such > documentation then I will certainly be questioning the bogie behind it. > > If we need to take any action it is to ensure we make it dear we are > using a tested snapshot of Cocoon 2.2 but that this tenting is confined > to its are in a standard Forrest install. > > Ross > > Ross > > -- View this message in context: http://www.nabble.com/Unreleased-Coccon-Code-in-Forrest-0.8-tp14103682p14291494.html Sent from the Apache Forrest - Dev mailing list archive at Nabble.com.
