On Fri, Jun 24, 2011 at 6:11 PM, Howard Lewis Ship <[email protected]> wrote: > I think we're coming to a collision in basic goals; I really want to > focus on a way to maximize exposure of Tapestry betas and RCs prior to > a final release, to help ensure that the final release really is > final.
Agreed. Clearly there are different approaches here which both are proven to work (e.g. JBoss vs. OpenBSD releases) with each their pros and cons. But like Robert, I just don't think there's such a thing for a framework as a final release and that's the crux of where our viewpoints differ. And even if there was, what difference would it make if 5.3.final+1 would be backwards compatible? But enough said, probably best to go forward with a vote if you want a consensus opinion. > its easy enough for people to temporarily accesss such a repository. > It could just be a matter of staging to the Apache Nexus and closing, > but not ever releasing, the repository. The good thing about the staging repos is that you can just drop them once you are done without ever having to release the bits to the wild (i.e. central in Maven's case). Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
