Re: [sleuthkit-users] Which is the best way to report TSK bugs?

[Brian C. <ca...@sl...>]

Hi Anton,

github issues and pull requests are the easiest at this point.  I should close the sourceforge trackers to new posts and redirect to github.  We've merged several of your pull requests over the past months.  Thanks for those. I saw that there was a bug reported a little while ago about long LFN.  

Like many open source projects, the developers who contribute to TSK/Autopsy are either volunteering their time or working as part of a project that uses them.   The reality of that is that random bug reports will eventually get looked at, but the time that it takes to look at it depends on many circumstances (and depends on the frequency and severity of the issue).   I usually review the list of bugs and such before we do a release to see if there is something that should be addressed.  We're due for a 4.2 release in the next couple of weeks and was going to merge in a bunch of the patches out there.

In terms of how long it takes for pull requests to get merged, the easier the patch, the faster it gets reviewed and merged.  The ones that hang out the longest are because they have a bunch of changes that require more thought. 

thanks,
brian




On May 5, 2014, at 4:40 AM, Anton Kukoba <ak...@ad...> wrote:

> We're actively using sleuth kit source code and tools, so we're finding  
> issues quite often. Sometimes we know how to fix the problem and we have a  
> patch for the source code. Sometimes we don't, but we want some feedback  
> about the bug we found, to know if it will be fixed by sleuth kit team, or  
> if we should try investigate on our own.
> I've tried creating the tickets at sourceforge, and it seems like it's no  
> good. Also I've tried to create pull requests when I had a patch, this is  
> unreliable also, because sometimes pull requests are hanging for weeks.
> So, I've decided to ask here...
> 
> -- 
> Anton Kukoba - Technical Leader
> ADF Solutions, Inc.
> 
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> sleuthkit-users mailing list
> https://lists.sourceforge.net/lists/listinfo/sleuthkit-users
> http://www.sleuthkit.org