Submitted patches

Page 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 [PATCH] ticket:1598 - Petascope supports delete coverage with error metadata   master   2017-08-10 16:30:00     PENDING    
 [PATCH] ticket:1357 - Make a WCPS 1.0 parsing service to parse WCPS in XML elements (abstract syntax, XML syntax)   release_9.5   2017-08-09 16:27:40     PENDING   SUCCESS 
 [PATCH] ticket:1560 - Rename test queries, test oracles of test wcs, wcps to be consistent and remove obselete tests wcs, wcps.   release_9.5   2017-08-09 13:36:07     PENDING   SUCCESS 
 [PATCH] ticket:1600 - WCS_Client logs the WCPS queries to console and records the time to execute queries   release_9.5   2017-08-09 10:47:06     PENDING   SUCCESS 
 [PATCH] ticket:1577 - modified output of 1-D csv to be standards-conformant and adjusted the corresponding system tests   release_9.5   2017-08-09 09:43:33     PENDING    
 [PATCH] ticket:1601 - Error when reloading GDAL native library by Classloader of JVM in new Petascope   release_9.5   2017-08-09 07:51:30     PENDING   SUCCESS 
 [PATCH] ticket:1497 - WCS_Client displays Coverages's Extents in WebWorldWind   release_9.5   2017-08-08 17:25:46     PENDING   SUCCESS 
 [PATCH] ticket:1533 - WCST_Import uses SECORE prefix from petascope's configuration as default crs_resolver   release_9.5   2017-08-03 16:08:01     PENDING   SUCCESS 
 [PATCH] ticket:502 - Support to migrate to different datasource (DBMS) in new Petascope   release_9.5   2017-07-26 12:51:27     PENDING   SUCCESS 
 [PATCH] ticket:1496 - WCS client displays the text result when not encode instead of downloading as file   release_9.5   2017-07-25 16:10:36     PENDING   SUCCESS 

Submit a new patch

Select your locally generated patch file below for upload. Note that the patch can only be accepted if you agree to the Rasdaman Contribution Agreement by ticking the checkbox.

See How to submit patches for a step-by-step guide, in particular regarding the patch subject format. In order to ensure quick processing and to avoid rejection, you may want to make sure your patch adheres to the rasdaman code guide.


Select the code branch below to which you want to commit (help); if you are not sure what this means just leave the default (master).



I agree to the Rasdaman Contribution Agreement.