[postgis-devel] WKT Raster: Bug tracking

[Pierre Racine]

I would not go with trac unless:

1) We know why PostGIS folks did not choose it. They must have a good reason. Anyone knows?

2) They actually plan to move to trac

If they accept WKT Raster in their Google code account, then maybe we can all move together some day. So there is no risk that we stay alone in our own system. I don't want to be alone :-(

I just wait for god benediction. But who's god?

Pierre

>-----Original Message-----
>From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
>bounces at postgis.refractions.net] On Behalf Of Mateusz Loskot
>Sent: 6 mars 2009 12:03
>To: PostGIS Development Discussion
>Subject: RE: [postgis-devel] WKT Raster: Bug tracking
>
>Obe, Regina wrote:
>> > Perhaps there is one, personally I've found it very helpful to be
>> > able to link
>> > from bug reports directly to source code revision/file/line easily,
>> > as it is possible in Trac (i.e. see http://trac.osgeo.org/geos/).
>> > Google Code lacks of such feature, so it requires more writing &
>> > time to deal with bugs.
>>
>> Good point.  At anyrate I would like to see both projects tracked
>> together  so if we eventually move back to trac for tracking, then both
>> should be moved at the same time.
>>
>> Or I suppose since WKTRaster is smaller at this point, it could start
>> off in trac and then we merge the core PostGIS into that trac.
>
>Good point.
>
>Best regards,
>--
>Mateusz Loskot
>Senior Programmer, Cadcorp
>http://www.cadcorp.com
>
>
>
>
>For the sake of simplicity, perhaps Frank's preference will make life easier.