L.S.,
How about doing the rename when moving the repository to git as the main repository? We already have git read-only repositories and I think everyone by now is using git-svn anyway. We will probably have to keep using that for the site, docs, dist areas, ... anyway for a while. When we make the move to git as the official (writable) repository, we could just ask infra to move the codebase into a git repository called "servicemix" and have both things done in one go. Regards, Gert Vanthienen Regards, Gert Vanthienen On Sun, Feb 16, 2014 at 2:41 PM, Krzysztof Sobkowiak <[email protected]> wrote: > Hi all > > Apart from the result of the vote about releasing ServiceMix based on Karf > 3.x or not, I'd like to propose to rename the current repository servicemix5 > to servicemix, as this repository should contain next ServiceMix releases > (we can move the current code base in a new branch servicemix-4.9.x and > start the new codebase for ServiceMix 5 on trunk). It means we should also > rename the git repository in Apache and Github. > > Regards > Krzysztof > > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect | Technical Architect @ Capgemini > Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center > <http://www.pl.capgemini-sdm.com/> | Wroclaw > e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak
