On 11/14/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
Eric Crahen wrote: > You're going to do an offical release where all you have done is changed > package names? Why not just bump the version, leave it in cvs as a > development branch and keep it there until significant effort and testing > has been done. > > I don't see what a quick release where you rename everything would do, it's > only of interest to developers. As a user of 1.4, the only reason I would > upgrade would be bugfixes. Changing around the package names just means > work > for me updating my taskdefs to match. As well as an an antlib, we could code some very thin classes in the original location that relay stuff to the new place. They would just extend the org.apache ones, maybe with a warning on <resolve> that you'd used the (deprecated) name. We'd need some ok from jayasoft to do this, or they could release a shim jar themselves that did the bridging.
The ok from jayasoft is not a problem, we can provide an antlib in the jayasoft package for backward compatibility.
Maybe this begs a broader question of should you simply freeze major > changes > on 1.4 and backport only major bug fixes, and do all new development in cvs > under a new major version which is in no rush to be released? The goal for a move to apache without big changes is to get a transition out of incubation without sitting down to do a big code roll. They always take longer than you think, even when you take that fact into account.
+1 What apache wants is not a new rewrite of the code, that is not a prereq
to getting out of incubation. What is is (a) code that isnt contaminated with copyright and similar problems and (b) an active community of developers. There are lots of people on the list with opinions, so we are making a start. I have one other requirement, which we can start as soon as ivy is on SVN, That is "ivy builds on Gump". there is a static version of Ivy 1.3 up there, but we need SVN_HEAD. Otherwise projects that use Ivy 1.4+ don't build on gump: http://vmgump.apache.org/gump/public/antbook/antbook-diary-core/gump_work/build_antbook_antbook-diary-core.html I'd like to fix this this week. What is the current SVN status?
The current svn status on jayasoft site corresponds to Ivy 1.4.1, with commit disabled. I've prepared an svn dump ready to be imported in apache, I'm only waiting for maarten to get an apache username, so that people from infrastructure can map his name in old jayasoft svn repo to his apache username. Maarten sent his ICLA by snail mail about two weeks ago I think, so it shouldn't take too much time to be registered. Then I hope Maarten will be able to say which username he wants, but he is currently overbooked with a very happy family event. Xavier I'll set
up the gump descriptors unless Stefano, Stefan or Stephane want to. All apache committes whose name is a variant of Stephen gets commit rights to Gump :) -steve -steve
