currently we need to maintain submission rule files in three different
branches (trunk, devbr6, relbr64). I would suggest to move these
documents from SVN to trac, similarly to GDAL [1]. In our case
something like
Hi,
submission rules shouldn't change too often and thus maintaining two
versions (GRASS 6 vs 7) shouldn't be a huge issue. Keeping them with
source has a benefit of being able to distribute them with source
Are there any other benefits besides "updating two versions"?
Just my 0.002 Verizon cents,
Maris.
2012. gada 13. aprīlis 01:53 Martin Landa <landa.martin@gmail.com> rakstīja:
Hi,
currently we need to maintain submission rule files in three different
branches (trunk, devbr6, relbr64). I would suggest to move these
documents from SVN to trac, similarly to GDAL [1]. In our case
something like
On Fri, Apr 13, 2012 at 8:38 AM, Maris Nartiss <maris.gis@gmail.com> wrote:
Hi,
submission rules shouldn't change too often and thus maintaining two
versions (GRASS 6 vs 7) shouldn't be a huge issue. Keeping them with
source has a benefit of being able to distribute them with source
+1
it is important to also keep them in the sources (also
for offline consulation)
