|
From: Sebastian M. <seb...@un...> - 2007-10-11 07:13:33
|
Am Thu, 11 Oct 2007 09:26:03 +0530 schrieb "Nageshwar M" <wha...@gm...>: > > Create a branch in vimplugin's repository and importing all code in > > eeedit into that branch. Then start off developing eeedits current > > state (respective change of namespace) > > > > why cant we use eeedit current source as main trunk. I think no part It was meant that way. I have imported eeedits code now to the branch .../vimplugin/branches/eeedit. Please check it out and review it. If you have no objections, I will move/copy it to trunk in the coming days. Other things I plan to do next days: * update the update site (new release) * establish automated build for update site (releases, nightly build) * update the wiki, allowing developers to post. * register a permanent irc-channel at freenode.net. Then I would like to make some roadmap. There are a lot of ideas flying around, let's collect and priorize them. (e.g. I've seen Martin did something to integrate with eclim, sounds interesting ... ) Last thing: please let's use the vimplugin-devel list for such discussions. Thanks, Sebastian. |