Re: [udig-devel] Move KML Import/Export Capabilities into a separate bun

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle

From: Jody Garnett <jody.garnett@xxxxxxxxx>
Date: Sat, 14 Apr 2012 16:06:45 +1000
Delivered-to: udig-devel@xxxxxxxxxxxxxxxxxxxxxx
List-archive: <http://lists.refractions.net/pipermail/udig-devel>
List-help: <mailto:udig-devel-request@lists.refractions.net?subject=help>
List-subscribe: <http://lists.refractions.net/mailman/listinfo/udig-devel>, <mailto:udig-devel-request@lists.refractions.net?subject=subscribe>
List-unsubscribe: <http://lists.refractions.net/mailman/options/udig-devel>, <mailto:udig-devel-request@lists.refractions.net?subject=unsubscribe>

In case you like the idea, should I create a new RFC for this
enhancement as well as a new issue in jira? Do you have other
suggestions?

We do not have to do RFC for everything :-) I would like to keep it for API changes or "strategic direction" questions such as change of license.

We can use JIRA for most purposes.

Jody

References:
- [udig-devel] Move KML Import/Export Capabilities into a separate bundle
  - From: Frank Gasdorf

Prev by Date: Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
Next by Date: Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
Previous by thread: Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
Next by thread: [udig-devel] pom-libs dependency:tree trick
Index(es):
- Date
- Thread

Back to the top