Apache projects have to do things transparently, so most of the work is (or should be) done in Subversion. Apache is all about the community.
On Thu, Oct 2, 2008 at 8:44 AM, Kristof Jozsa <[EMAIL PROTECTED]> wrote: > totally out of topic and excuse me for my curiosity, but do you use > subversion to the heavy lifting with such branching/merging there or > use some distributed version control system behind the scenes? > > K > > On Thu, Oct 2, 2008 at 9:25 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: >> yes we should make a 1.3.5 and a 1.4m4 asap, there are a lot of changes >> I think i will make some time this weekend to look over jira issues and also >> merge back a lot of changes i already did in 1.3.5 >> >> igor did also a lot of stuff already so for me within 1 or 2 weeks we could >> do both releases >> >> johan >> >> >> On Thu, Oct 2, 2008 at 8:15 AM, Stefan Lindner <[EMAIL PROTECTED]> wrote: >> >>> It's clear that it's not possible to estimate the release of 1.4 final. But >>> can anybody tell us whether a new snapshot (1.4M4) is in sight? >>> >>> Stefan >>> >>> -----Ursprüngliche Nachricht----- >>> Von: Timo Rantalaiho [mailto:[EMAIL PROTECTED] >>> Gesendet: Donnerstag, 2. Oktober 2008 05:37 >>> An: users@wicket.apache.org >>> Betreff: Re: wicket 1.4 release >>> >>> On Wed, 01 Oct 2008, lesterburlap wrote: >>> > I've searched everywhere and can't find an answer. I know this is kind >>> of a >>> > crappy question to ask the developers... >>> > >>> > Is there an estimate for a Wicket 1.4 GA release? Will it possibly be by >>> > January 2009? >>> >>> I think that it's impossible to estimate the releases of a >>> volunteer-based open source projects in any meaningful way, >>> unfortunately. If others know better, please pipe in. >>> >>> You can always follow the number of open issues >>> >>> >>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310561&fixfor=12313295&resolution=-1&sorter/field=issuekey&sorter/order=DESC >>> >>> ( http://tinurl.us/a2b895 ) >>> >>> but there might be some new ones coming in as well. Also >>> work continues on 1.3.5 at the same time (fortunately, many >>> of the issues can probably be fixed to both at the same time). >>> >>> Your good patches to the issues are bound to make the >>> release happen earlier ;) >>> >>> > I need to make a decision about whether or not to upgrade to 1.4-m3 from >>> > 1.3..... while intending to upgrade to 1.4 GA prior to my product release >>> in >>> > January. I need some stuff that's in 1.4, but I can't release our >>> product >>> > with beta libraries included. >>> >>> Fortunately, there is not a lot of special testing for the >>> releases, so a milestone is nearly good enough ;) What's more >>> problematic with releasing with a milestone dependency are >>> the possible API breaks. >>> >>> Best wishes, >>> Timo >>> >>> -- >>> Timo Rantalaiho >>> Reaktor Innovations Oy <URL: http://www.ri.fi/ > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
