On 28/11/14 14:51, GRASS GIS wrote:
#2409: last call for options keys consolidation
----------------------------------+-----------------------------------------
  Reporter:  martinl               |       Owner:  grass-dev@…
      Type:  task                  |      Status:  new
  Priority:  blocker               |   Milestone:  7.0.0
Component:  Default               |     Version:  unspecified
  Keywords:  standardized options  |    Platform:  Unspecified
       Cpu:  Unspecified           |
----------------------------------+-----------------------------------------

Comment(by huhabla):

  I am not against renaming the options, but IMHO its completely
  unnecessary. However, if the majority thinks it is necessary then i am
  fine with that.

  But the recent changes in the option naming broke the temporal framework
  and as a result many temporal modules and tests.

  Why??!!

  If such invasive changes are performed, then i would expect that all the
  consequences of these changes are recognized and fixed before the commit!

  We have a wonderful testsuite, so please use it to detect possible issues.
  Please do not simply break GRASS and expect that other developers will fix
  it.

Yes, I've already stumbled upon one test which fails because of changed type name (r.slope.aspect test calls g.remove with type="rast").

I agree with Soeren that we have to be careful about these changes, especially if we want to release in a not too far future...

Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to