Citerar Jonathan Aquilina <eagles051...@gmail.com>:

> Dont worry though if you arent seeing all the bugs yet from source forge im
> working on migrating them as we speak. But for any new bugs or patches go
> ahead and create a new issue
>
> https://github.com/LMMS/lmms/issues?state=open
>
> and tag accordingly please.

1. The wiki should be updated to point people towards Github. The  
instructions for how to participate should be updated, too. (I know I  
read the wiki long before I joined these lists...)

2. The new issue tracker could do with better labels, my suggestion is  
something along these lines:
- enhancement/patch -> split into enhancement and patch
- crash! (even redder than "bug" if possible), maybe "important" too?
- one label for each plugin
- automation, pattern editor, midi, ui...
- "not our bug" as a resolution for stuff external to LMMS (libs it  
depends on and so on)



-- 
ra...@iki.fi
http://www.mikseri.net/radioproject



------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to