kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

This is dependent on the size of the change.  If it's small change,
patches are fine.  If it's a very large change, then I prefer that you
create a public repo on launchpad so I can clone it locally to review
and test it.  You have to use your best judgment on this.

It's important to get input from the developer list before you spend too
much time coding to avoid wasting time.

I am considering using launchpad blueprints for new feature development.
 Unfortunately I haven't figured out a way to restrict changes to the
blueprints so it a bit of a mess right now.  One nice thing with
blueprints is that we can collaborate on determining the feature design
without using email.  We can also link the blueprint to a development
series.  Until I figure out how to limit access to the blueprint
database I am a bit hesitant to go this route.

Cheers,

Wayne

On 01/30/2018 04:23 PM, Jeff Young wrote:
> If we implement a feature or an improvement to a feature, does it need an issue, or do we just send patches to the dev-list?
> 
> (Obviously this is for 6.0, so I’m just trying to understand the process.)
> 
> Thanks,
> Jeff.
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>