On Sat, Jul 26, 2008 at 10:20 AM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: >> Can you provide one example? Just curious.... > > While it was incubating, Wicket did a few non-ASF releases on their > old project site, to minimize disruption for their existing users > while they were repackaging and cleaning up for an ASF release.
And even after we had graduated. Wicket 1.2.7 (the final maintenance release for the 1.2 branch) was created in last March. We didn't use the Apache mirroring system and put a disclaimer in it that the release was non-Apache. [1] This is a service we provide for our users that were with us before we moved to apache and are counting on us to provide support on their production systems. However, since we are a volunteer effort with limited resources, we have discontinued to support the 1.2 branch (though we will act on security issues) and now focus on Apache software :). > I haven't followed all of this discussion, but IIUC that's a similar > situation. Yep, and it really is a problem IMO when incoming *open source* projects have to ditch their collected history. If we care about code provenance, having the full history available is best. Martijn -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
