[Dltk-dev] Patch submission procedure

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

[Dltk-dev] Patch submission procedure

From: Perry Bhandal <perry.bhandal@xxxxxxxxx>
Date: Sun, 27 Jul 2014 04:22:09 -0400
Delivered-to: dltk-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/dltk-dev>
List-help: <mailto:dltk-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/dltk-dev>, <mailto:dltk-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/dltk-dev>, <mailto:dltk-dev-request@eclipse.org?subject=unsubscribe>

Hi all,
I recently began using DLTK for Ruby development, and was hoping to give back by adding a few features.

I've never contributed to an Eclipse plugin before, so I'm unfamiliar with the exact process. Is it as simple as creating a bug report (in Eclipse's Filezilla) which outlines the feature, then responding to my bug report with a patch that implements said feature? Or have I overlooked a step?

Thanks,
Perry

Follow-Ups:
- Re: [Dltk-dev] Patch submission procedure
  - From: Kaloyan Raev

Prev by Date: Re: [Dltk-dev] Avoid emptying / recreating the H2 index upon every project close / open ?
Next by Date: Re: [Dltk-dev] Patch submission procedure
Previous by thread: [Dltk-dev] Avoid emptying / recreating the H2 index upon every project close / open ?
Next by thread: Re: [Dltk-dev] Patch submission procedure
Index(es):
- Date
- Thread

Breadcrumbs