[GRASS-dev] Some migration news

GRASS GIS GRASS GIS developer
1

Hi developers,

Martin has prepared the final SVN dump of the migrated CVS
repository with all tags brought into common form and
other nice fixes. The dump is currently transferred to
OSGeo and will be imported there later tonight.

Meanwhile Trac (which should serve us as developers platform
while the user Wiki remains Mediawiki) is getting populated:

# Main page:
http://trac.osgeo.org/grass/wiki

# Releases
http://trac.osgeo.org/grass/roadmap?show=all

# Tickets (have to be migrated from GForge and maybe also RT)
http://trac.osgeo.org/grass/report

More to come soon,
Markus

2

Markus Neteler wrote:

# Tickets (have to be migrated from GForge and maybe also RT)
http://trac.osgeo.org/grass/report

Working on it [1]. Propably can do for GForge; propably
won't-do for RT - too much mess there; I'd leave as it is.

I'm still keeping an eye on RT, closing tickets for issues
that get fixed in CVS, adding new commets from time to time
etc. If anybody (*especially* original reporters) would like
to skimm through their old RT reports to validate them or
mark for closing, They are always more than welcome. That
would certainly be much help.

[1]http://wald.intevation.org/tracker/index.php?func=detail&aid=560&group_id=1&atid=162

Maciek

3

Hi Maciek,

2007/12/10, Maciej Sieczka <tutey@o2.pl>:

Markus Neteler wrote:

> # Tickets (have to be migrated from GForge and maybe also RT)
> http://trac.osgeo.org/grass/report

Working on it [1]. Propably can do for GForge; propably
won't-do for RT - too much mess there; I'd leave as it is.

good to know taht you are working on it. Thanks! I put today on the
wiki two notes [1]. But the export from GForge failed (maybe I just
wrong), e.g.

http://wald.intevation.org/tracker/?atid=188&group_id=21&func=browse
->
http://wald.intevation.org/export/tracker.php?atid=188&group_id=21

Martin

[1] http://grass.gdf-hannover.de/wiki/GRASS_Migration_to_OSGeo#Migration_of_GForge.2FRT_bugtracker_to_OSGeo_Trac

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

4

Martin Landa wrote:

But the export from GForge failed

How did you do this "export"?

If all goes well we'll get an SQL dump of GRASS GForge
trackers content from Sascha. Would it be easy to import
this into Trac?

Maciek

5

Hi,

2007/12/10, Maciej Sieczka <tutey@o2.pl>:

Martin Landa wrote:

> But the export from GForge failed

How did you do this "export"?

this URL should generate XML file with tickets definition of the given
group (atid=188) (which can be used as an input for
sourceforge2trac.py script)

http://wald.intevation.org/export/tracker.php?atid=188&group_id=21

but it is generating invalid, almost empty file...

Martin

If all goes well we'll get an SQL dump of GRASS GForge
trackers content from Sascha. Would it be easy to import
this into Trac?

Maciek

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

6

Martin Landa wrote:

this URL should generate XML file with tickets definition of the given
group (atid=188) (which can be used as an input for
sourceforge2trac.py script)

http://wald.intevation.org/export/tracker.php?atid=188&group_id=21

but it is generating invalid, almost empty file...

Interesting. Is this export feature documented somwhere? How
did you find it out?

Maciek

7

Hi Maciek,

2007/12/11, Maciej Sieczka <tutey@o2.pl>:

Interesting. Is this export feature documented somwhere? How
did you find it out?

http://lists.edgewall.com/archive/trac/2006-April/007535.html

Martin

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *