On 23/01/13 10:00, Jody Garnett wrote:
> Usual check list, ensure it has a test case, submit JIRA etc…
>
> Maybe faster, submit pull request (rather than attach patch to the Jira)
>
> Finally if it is for a deadline, consider hiring one of the groups
> offering GeoTools support to get it done promptly (if not you are
> basically waiting on a developer to have some free time on the weekend
> they have not otherwise devoted to family).
>
> The number one thing is to include a patch with a test case, when this
> does not happen the developer has to go to a lot of work to verify the
> problem is real, and that your fix does something. Turns a 5 min apply
> patch, into a 30 min reverse engineer the problem and write test case.
> Since you have the benefit of having discovered the problem it is way
> faster for you to make the test case :-)
>
> Andrea wrote some nice words a while back, and we have a longer story
> in our user guide
> <http://docs.geotools.org/latest/userguide/welcome/support.html>.
>
> But yeah include a test case :-)
>
makes sense. do you have a suggested pattern for including a test case
for testing for an infinite loop? fire up the process in a separate
thread & wait for some time for it to finish?
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
