[postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines

[PostGIS]

#841: Commiter Responsibilities Guidelines
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  robe            
     Type:  task     |      Status:  new             
 Priority:  medium   |   Milestone:  OSGeo incubation
Component:  postgis  |     Version:                  
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by strk):

 To be honest, I haven't updated the release_notes.xml file, just the NEWS
 file (assuming the former can be derived by the latter)

 I'm not against the HISTORY trick on itself, just doesnt' sound like
 something
 developers are doing right now.
 I tried a git log --grep=HISTORY and found only 5 hits (3 of yours, 2 of
 Mark),
 last of which from March 2009...

 If tagging really helps automation I'm all for it, but it sounds like
 something easy
 to forget, in which case you end up needing to commit something void just
 for the sake of enterying the NEWS item, which wouldn't be much different
 than committing
 a change in the NEWS file directly

 NEWS editing seems more common:

 {{{
 git log NEWS | grep ^Author | sort -u
 Author: mleslie <mleslie at b70326c6-7e19-0410-871a-916f4a2858ee>
 Author: mschaber <mschaber at b70326c6-7e19-0410-871a-916f4a2858ee>
 Author: nicklas <nicklas at b70326c6-7e19-0410-871a-916f4a2858ee>
 Author: pramsey <pramsey at b70326c6-7e19-0410-871a-916f4a2858ee>
 Author: robe <robe at b70326c6-7e19-0410-871a-916f4a2858ee>
 Author: strk <strk at b70326c6-7e19-0410-871a-916f4a2858ee>
 }}}

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/841#comment:8>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.