I think this workflow works well.
On 15 Jan 2014 22:17, "Paul Giblock" wrote:
> Agreed, I'd rather discussion stay on the mailing lists. If someone has a
> bug: sure, report it straight to the tracker. But, regarding developer
> discussion, issues shouldn't be created until the discussion has le
I will need to add them since I have been made co-owner by toby.
On Wed, Jan 15, 2014 at 6:01 PM, Raine M. Ekman wrote:
> Here's some kind of starting point.
>
> Broad classifications: bug, crash, enhancement, discussion
> Resolutions: duplicate, invalid, question, wontfix, not our issue, later
Got it will make amendments to the tags on the tracker.
On Wed, Jan 15, 2014 at 10:16 PM, Paul Giblock wrote:
> Agreed, I'd rather discussion stay on the mailing lists. If someone has a
> bug: sure, report it straight to the tracker. But, regarding developer
> discussion, issues shouldn't be c
Agreed, I'd rather discussion stay on the mailing lists. If someone has a
bug: sure, report it straight to the tracker. But, regarding developer
discussion, issues shouldn't be created until the discussion has led to
concrete feature or bug requests.
On Wed, Jan 15, 2014 at 11:34 AM, Tobiasz Kar
That is me paul i will let the list know when migration is complete.
On Wed, Jan 15, 2014 at 8:36 PM, Paul Giblock wrote:
> As documentation and other features migrate to GitHub: could the person
> performing any of these operations please let Toby, me, or the mailing list
> know when a system
As documentation and other features migrate to GitHub: could the person
performing any of these operations please let Toby, me, or the mailing list
know when a system is fully-migrated so we can make the old SF.net
equivalent either read-only or a redirect?
Thanks,
Paul
On Wed, Jan 15, 2014 at 1
Hi,
feel free to introduce labels as you like it. You really don't need
permission from me for things like these ;-)
Toby
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosi
Here's some kind of starting point.
Broad classifications: bug, crash, enhancement, discussion
Resolutions: duplicate, invalid, question, wontfix, not our issue, later
Components: zynaddsubfx, mixer, sf2player, vestige, midi, build
system, automation, audio file processor
BTW, I signed up for G
I'd prefer to stay here, as I'm gonna be cut off while on mobile and
offline. I write and read here mostly this way.
On 15 Jan 2014 16:53, "Tres Finocchiaro" wrote:
> From my experience, forums/trackers are not a great place to look for
> active discussions any more.
>
> They can serve as a nice
On 15 January 2014 20:51, Jonathan Aquilina wrote:
> Then I am in trouble as I posted my idea about the logic pro stuff in the
> tracker already :(
Don't worry, its okay what's done is done. :)
--
Gurjot Singh
Blog: http://bhattigurjot.wordpress.com
---
Then I am in trouble as I posted my idea about the logic pro stuff in the
tracker already :(
On Wednesday 15 January 2014 20:49:15 Gurjot Singh wrote:
> On 15 January 2014 20:46, Jonathan Aquilina wrote:
> > Good point, but i still feel right now with the community being so small
> > it
> > won
On 15 January 2014 20:46, Jonathan Aquilina wrote:
> Good point, but i still feel right now with the community being so small it
> wont be much of a problem to be honest.
Let's see what others have to say about this. Only then we should
decide what is best.
--
Gurjot Singh
Blog: http://bhattig
Good point, but i still feel right now with the community being so small it
wont be much of a problem to be honest.
On Wednesday 15 January 2014 20:43:51 Gurjot Singh wrote:
> On 15 January 2014 20:37, Jonathan Aquilina wrote:
> > Hey guys just an idea.
> >
> > Can we try and keep all discussio
On 15 January 2014 20:37, Jonathan Aquilina wrote:
> Hey guys just an idea.
>
> Can we try and keep all discussions on the issue tracker and i will create
> another tag called discussion along side the enhancement/patch tag and if we
> could tag any new discussions and or feature requests as such
Raine I am migrating the bugs from the SF bug tracker to the git hub issue
tracker.
Can you provide me with a list of tags you would like to see I would more the
happily include them. Seeing as Toby is busy I am going to take this by the
horns instead of waiting for him to respond.
Isnt this w
OK, I was thinking of how to leverage the new opportunities or
something. My reasoning is that labels on github seem like a
user-friendly way of categorizing the issues. You see immediately in
the issue list what the issue relates to, and even get cool statistics
:)
Another thing is that
@toby see below on your thoughts.
Raine I am going by the labels toby had initially setup. Its really up to him.
The problem with too many labels is that things can easily get mistagged + it
would be easier to just classify them as a bug in general and specify what
part of the program. Then aga
Citerar Jonathan Aquilina :
> 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
18 matches
Mail list logo
