Re: 3.13.0beta1 ?

> On Aug 15, 2024, at 9:30 PM, Regina Obe wrote: > > I assume that GEOS there is meant to be GDAL? > What does upgrading CMake buy us. > > That ticket you reference was fixed a different way. > > I'm still hesitant to up the CMake version just for the sake of upping the > CMake version espec

Re: [geos-devel] CoordinateArraySequence == CoordinateSequence

> On Oct 4, 2022, at 10:15 AM, Daniel Baston wrote: > > - Allowing the use of an external buffer instead of the one managed by > std::vector, so we could have a zero-copy method of bringing data into GEOS > from an interleaved buffer This. In PDAL's (albeit unusual) usage, we pass through

Re: [geos-devel] Changes to the website and Github page

> On Feb 21, 2022, at 10:23 AM, Regina Obe wrote: > > Well touching the homepage and closing a ticket, I could not find where we > tell people how to get support from the project. > > It wasn't on the home page - https://libgeos.org/ > > But instead was buried in the Development header - >

Re: [geos-devel] GEOS Maintenance Grant

22, at 9:37 AM, Howard Butler wrote: > > GDAL PSC, > > When we wrote the GDAL RFCs on sponsorship, we provided an escape clause to > allow us to direct resources to other projects upon which GDAL depends. Our > sponsorship numbers are still increasing, which provides us an

Re: [geos-devel] Motion: Adopt OSGeo Code of Conduct

+1 Howard > On Feb 16, 2022, at 7:04 PM, Daniel Baston wrote: > > +1 > > Dan > > On Wed, Feb 16, 2022 at 5:46 PM Sandro Santilli wrote: > On Wed, Feb 16, 2022 at 12:31:06PM -0800, Paul Ramsey wrote: > > I noticed that the GDAL CoC is in fact just the OSGeo CoC, which is > > convenient, as

[geos-devel] GEOS Maintenance Grant

with a $50,000 USD grant to address performance, API, and other work that does not attract directed funding in GEOS. The GEOS PSC will be responsible for coordinating work tasks, rates, and development timelines. Howard Butler or Even Rouault of the GDAL NumFocus liaison team will coordinate

Re: [geos-devel] GEOS RFC 10 - Move Project to GitHub

> On Nov 2, 2021, at 5:00 AM, Sandro Santilli wrote: > > More dependence on single corporation being the only one which can do work on > the infrastructure. Anyone can be a contributor on OSGeo > infrastructure so "only they can do" is a misleading picture, as if "they" > would not be all of us

Re: [geos-devel] GEOS RFC 10 - Move Project to GitHub

> On Oct 29, 2021, at 2:13 PM, Paul Ramsey wrote: > > http://libgeos.org/development/rfcs/rfc10/ > > GitHub has been the largest source of 3rd party code contribution via > pull-requests for some time now. > > Moving to Github has the following components: > > • Move the canonical (wr

Re: [geos-devel] PSC Vote: Host geos.osgeo.org on GH pages

> On Aug 24, 2021, at 11:22 AM, Sandro Santilli wrote: > >> One of the many advantages of the GDAL, PDAL, and PROJ documentation setup >> is we practically never have to mess with it. It just works. When it doesn't >> work, or when someone wants to make a documentation contribution, anyone ca

Re: [geos-devel] PSC Vote: Host geos.osgeo.org on GH pages

> On Aug 24, 2021, at 5:10 AM, Sandro Santilli wrote: > >> You guys hate the evil GitHub empire, but the way to do this is to create a >> GitHub action that pushes the site whenever the branch that contains the >> active docs is pushed. See PROJ, PDAL, GDAL, and others for examples of this

Re: [geos-devel] PSC Vote: Host geos.osgeo.org on GH pages

> On Aug 23, 2021, at 11:52 AM, Sandro Santilli wrote: > > Setting up a cron job or git hook to build & publish the site > upon commit to a git repository would be easy (under Gitea). You guys hate the evil GitHub empire, but the way to do this is to create a GitHub action that pushes the si

Re: [geos-devel] CAPI GEOSUnionCascaded

> On Jul 15, 2021, at 1:01 PM, Paul Ramsey wrote: > > Just stumbled over this old stub, > > https://github.com/libgeos/geos/blob/main/capi/geos_ts_c.cpp#L1425 > > In addition to GEOSUnaryUnion, which calls a cascaded union as required, we > have this explicit hook into cascaded polygon uni

Re: [geos-devel] Motion: Adopt RFC-7 (Discontinue use of autotools)

> On Jan 13, 2021, at 7:41 PM, Daniel Baston wrote: > > Hi, > > I'd like to thank everyone who contributed to the recent discussion of RFC-7 > [1]. Considering the feedback received, and our early position in the release > cycle, I do not anticipate problems from removing autotools for our n

[geos-devel] Motion: Add Dan Baston to GEOS PSC

All, I would like to nominate Dan Baston to the GEOS PSC. His contributions for the 3.8.0 release were substantial, and he is very actively supporting PostGIS as well. I'll start with a +1. Howard ___ geos-devel mailing list geos-devel@lists.osgeo.or

Re: [geos-devel] Compiling geos on windows

I made a PR that fixes these issues. It can be found at https://github.com/libgeos/geos/pull/226 On Thu, Sep 19, 2019 at 3:23 PM Daniel Baston wrote: > Hi Paul, > > I suspect you're running into the same problem documented in this ticket: > https://trac.osgeo.org/geos/ticket/975 > I think the CI

Re: [geos-devel] RFC 9: Restore C++ API as public API

> On May 16, 2019, at 6:49 PM, Regina Obe wrote: > > -1 > > Not much has changed since we made this decision to make it non-public. In > fact ironically I feel like more people are using GEOS than before. > I was hoping removing the C++ public would scare more people away so we could > do so

Re: [geos-devel] pragma once

On 12/19/18 11:26 AM, Greg Troxel wrote: > Paul Ramsey writes: > >> "non standard but widely supported" >> >> https://en.wikipedia.org/wiki/Pragma_once >> >> Includes MSVC! :) > As much as I hate to depart from standards, that does look near > universal. Go for #pragma once. We haven't regrette

Re: [geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote

On 9/11/18 6:44 AM, Sandro Santilli wrote: > On Mon, Sep 10, 2018 at 01:15:25PM -0700, Paul Ramsey wrote: >> Same. 2-spaces hurts my little brain. > I'm happy as long as you give me a recipe to make my editor > (vim) automatically use what we choose AND `make check` > ensures any future change st

[geos-devel] Motion: Approve Commit Access for Kurt Schwehr

Dear PSC, Kurt has been undertaking security fuzzing related activities in numerous open source geo projects including PROJ and GDAL, and his ticket traffic on the topic in the GEOS project has been stopped up due to lack of developer interest. I motion to give him push access to pursue the secur

Re: [geos-devel] PSC Vote release of GEOS 3.7.0alpha in 1-2 weeks

+1 On 6/5/18 7:59 AM, Dale Lutz wrote: > I approve +1 > > (Sorry for the delay) > > > > ___ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel signature.asc Description: OpenPGP digital signa

Re: [geos-devel] GIT repo url updated

> On Dec 19, 2017, at 2:55 AM, Regina Obe wrote: > > strk, > > I'm so proud of you. You kept your cool and answered well. I can't say I > would have handled Hobu's negativity as well. > Looking forward to using gitea more. Thanks for all the hard work. My negativity stems from arbitrary ch

Re: [geos-devel] GIT repo url updated

> On Dec 17, 2017, at 6:42 AM, Sandro Santilli wrote: > > Following an upgrade of OSGeo GIT hostign services technology > from Gogs to Gitea [1] the official GEOS git repository URL > changed to: > > https://git.osgeo.org/gitea/geos/geos.git > > Assuming your official remote is called "origin

Re: [geos-devel] Alternative licensing for GEOS

On Wed, Nov 8, 2017 at 2:08 PM, Sandro Santilli wrote: > > And that's the whole point of the GPL licences ! > > You want to spread proprietary applications ? It has to be painful :) > Ah, there's that contributor, right on cue. ___ geos-devel mailing l

Re: [geos-devel] Alternative licensing for GEOS

James, The answer to the question of the possibility of relicensing GEOS is "no" with near 100% certainty. There are a few significant GEOS contributors who are steadfast in their contribution only being released as LGPL software. This question has come up a few other times and there's never been

Re: [geos-devel] MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) - Summarize of votes

> On Oct 5, 2017, at 1:35 AM, Regina Obe wrote: > > Just to confirm intention and the fact I misquoted Hobu as strk pointed out. > > The MOTION for geos 3.7.0 is to put a warning in theG eometry.h header file > that will show whenever a user compiles a project source against the GEOS C++ > AP

Re: [geos-devel] RFC6 - Discourage use of C++ API by requiring a configure switch to install the c++ headers and SDK

> On Oct 4, 2017, at 12:08 AM, Regina Obe wrote: > > According to RFC1 – it says the motion can not pass > https://trac.osgeo.org/geos/wiki/RFC1 > with a -1 and I have to give Hobu a chance to debate his point J > > "Respondents may vote "-1" to ve

Re: [geos-devel] [postgis-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8

> > On Oct 3, 2017, at 9:33 AM, Regina Obe wrote: > > Strk, > > Is there a way to get rid of the shared C++ library and just have a C library > or is that what you were talking about with the static C++ library. > > That extra library I have to carry around annoys me as it's so easy for one

Re: [geos-devel] Ready to switch from SVN to GIT ?

+1 for moving to git as primary source control. > On Apr 4, 2017, at 5:36 AM, Regina Obe wrote: > > +1 for move. > > > -Original Message- > From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of > Sandro Santilli > Sent: Tuesday, April 04, 2017 6:09 AM > To: geos-de

Re: [geos-devel] RFC 5: C++11 Compilation Mode

> On Apr 3, 2017, at 3:55 PM, Mateusz Loskot wrote: > >> but I too would note that range-based for loops don't work in MSVC 2013. > > Hmm, I'm not sure it's clear to me - I've not noticed any problem there. > Range-based statement should work pretty well in VS2013, even in VS2012: > https://msd

Re: [geos-devel] RFC 5: C++11 Compilation Mode

> On Apr 1, 2017, at 11:44 AM, Sandro Santilli wrote: > > On Sat, Apr 01, 2017 at 06:25:09PM +0200, Mateusz Loskot wrote: >> I'd rather wait for more votes than two. >> If no more votes arrive, I'll mark the RFC 5 as referred or withdrawn. > > You might have noticed that PSC has not been very a

Re: [geos-devel] Will GEOS license follow JTS?

On Feb 24, 2014, at 4:38 AM, Pepijn Van Eeckhoudt wrote: > Hi all, > > As part of the move of to LocationTech it seems JTS is going to be relicensed > to BSD and/or EPL. Since JTS is kind of the upstream project for GEOS, I was > wondering if GEOS was going to follow this example or not? No

Re: [geos-devel] GEOS Usage

On Oct 16, 2013, at 5:51 PM, Greg Troxel wrote: > > Howard Butler writes: > > You make a good point that a BSD-licensed geos equivalent would be > useful to those who wish to create proprietary derived works. > >> That this community is hostile to contribution from

Re: [geos-devel] GEOS Usage

On Oct 11, 2013, at 8:09 AM, Malcolm Toon wrote: > Good morning! > > We are evaluating spatialite with GEOS extensions for inclusion in an iOS > project we're working on. Because we're targeting iOS, we cannot dynamically > link the library in, so we'd have to statically link it in (unmodifie

Re: [geos-devel] Motion to give Regina commit rights - PSC members who haven't Please respond

On Jul 19, 2013, at 8:43 AM, Sandro Santilli wrote: >> Any current committer can add another committer by adding the person to the >> list. No special admin needed. > > Which list ? Where from ? https://www2.osgeo.org/cgi-bin/auth/ldap_group.py?group=geos > Once we have that, I'd like not to

Re: [geos-devel] Motion to give Regina commit rights - PSC members who haven't Please respond

On Jul 19, 2013, at 2:48 AM, "Paragon Corporation" wrote: > So far > Strk http://lists.osgeo.org/pipermail/geos-devel/2013-July/006419.html > Pramsey http://lists.osgeo.org/pipermail/geos-devel/2013-July/006420.html > , and of course robe > http://lists.osgeo.org/pipermail/geos-devel/2013-July/

Re: [geos-devel] PSC refresh

On Jul 1, 2013, at 5:07 AM, Sandro Santilli wrote: > I've noticed that the PSC page on the wiki is outdated: > http://trac.osgeo.org/geos/wiki/PSC > > Some PSC members likely changed their email addresses, while are likely > not interested in being part of the commettee anymore. > > According

Re: [geos-devel] C API / DLL only?

On Jul 2, 2012, at 1:44 PM, Chris Krycho @ GEOS wrote:Sorry if this has been asked before, but I have not been able to find it after a couple of days of Googling, including the list archives. I've just started work on an existing piece of in-house software that uses GEOS, which is built against the

Re: [geos-devel] newbie user and visual studio

On Jun 21, 2012, at 11:55 AM, Jeff McKenna wrote: > I am not aware of a Visual Studio solution file that you ask for. You can easily generate a Visual Studio solution of any vintage (2005, 2008, 2010) you want by issuing the appropriate command to cmake. $ cmake -g "Visual Studio 10 Win64" ……….

Re: [geos-devel] RE: Project Officer

On Mar 21, 2012, at 11:10 AM, Dale Lutz wrote: >> So, +0 here for me as chair. As per RFC1 it takes +2 (and no -1) to go. >> Martin, Howard, Gary, Dale and Paul: cast your votes please. > > +1 from Dale +1 Howard ___ geos-devel mailing list geos-dev

Re: [geos-devel] Call for test of the 3.3 branch

Fixed in 3.3 branch http://trac.osgeo.org/geos/ticket/506 Please test. I don't think this is worth a new release, as very few folks build this on windows themselves. Howard On Jan 6, 2012, at 2:30 PM, Jeff McKenna wrote: > I'm trying to compile 3.3.2 on Windows (MSVC 2008/9.0) and getting th

Re: [geos-devel] Moving to github

On Sep 20, 2011, at 8:35 AM, Sandro Santilli wrote: > On Tue, Sep 20, 2011 at 08:26:12AM -0500, Howard Butler wrote: >> On Sep 20, 2011, at 3:32 AM, Sandro Santilli wrote: > >>> I'd have to create a "geos" organization and re-import the data >>&

Re: [geos-devel] Motion: Commit access for Oliver Tonnhofer

On Sep 20, 2011, at 3:32 AM, Sandro Santilli wrote: > On Tue, Sep 20, 2011 at 10:17:47AM +0200, Oliver Tonnhofer wrote: >> >> On 18.09.2011, at 11:10, Sandro Santilli wrote: >>> Oliver: are you aware of the git mirror ? >>> Does it make your contribution workflow easier ? >> >> The one on your

Re: [geos-devel] OS X 10.7 Lion llvm problem

On Jul 31, 2011, at 1:18 PM, Sandro Santilli wrote: > On Sun, Jul 31, 2011 at 12:23:39PM -0500, William Kyngesburye wrote: >> Lion's Xcode now defaults to the llvm compiler (symlink gcc and g++ to the >> llvm). I get an error: >> >> Linking CXX shared library ../lib/GEOS.framework/Versions/3/G

[geos-devel] Motion: Commit access for Oliver Tonnhofer

All, I am currently at the #foss4g code sprint in Denver, and I have been working with Oliver on a small patch to streamline setting CoordinateSequence via the C API, and it would much less hassle if Oliver simply had commit access to the GEOS repository to apply and work with patches of this t

Re: [geos-devel] segfault against 3.3.0 C++

On Sep 9, 2011, at 12:46 PM, Peter Körner wrote: > *) the docs say, that the C-wrapper is recommended and the C++ interface is > not, although I don't really know why. Because the implied developer contract of GEOS, which you signed before you downloaded GEOS ;), is to do our best to preserve

Re: [geos-devel] TopologyException makes GEOS/JTS very difficult to employ in my production environments...

On Sep 29, 2010, at 8:31 AM, G. Allegri wrote: > I anticipate the critics: put the money on the table and someone could > invest time to solve it. Holy words, this is how foss should work. But > I'm not the boss of my company, and I've suggested to employ > PostGIS->GEOS in a big job... and now I

Re: [geos-devel] use of STRtree functions in C API

On May 4, 2010, at 10:54 AM, Martin Davis wrote: > Sure, why not? At least for in-memory indexes - there are no plans to extend > this to disk-based indexes. > > Reasons are: > i) The code is there and well-tested > ii) The index is designed to work well with GEOS objects (although as you > poi

Re: [geos-devel] use of STRtree functions in C API

On May 4, 2010, at 9:26 AM, Roger Bivand wrote: > Thanks for the suggestion. > > I'm sorry, but I don't see any documentation whatsoever, after successfully > building. So "quite easily" is maybe not my impression, I'm afraid, coming > from C and interfacing with R. If you've coded with GDAL o

Re: [geos-devel] Motion: Add Paul Ramsey as PSC Member

On Apr 11, 2010, at 11:34 AM, strk wrote: > On Wed, Apr 07, 2010 at 08:14:02AM -0500, Howard Butler wrote: >> PSC Members, >> >> I would like to add Paul Ramsey to the PSC, subject to his acceptance of RFC >> 2 (which he wrote ;). His history with the project is w

Re: [geos-devel] use of STRtree functions in C API

Roger, I would suggest at least investigating libspatialindex, which is an R* tree (and linear and quadratic splitting as well) implementation that is much more featureful than the unexposed internal indexing of GEOS. I have just added a C API (GDAL or GEOS-style, it's a total rip-off of them)

[geos-devel] Motion: Add Paul Ramsey as PSC Member

PSC Members, I would like to add Paul Ramsey to the PSC, subject to his acceptance of RFC 2 (which he wrote ;). His history with the project is well known, and now that he's more deeply in the technical realm, it makes sense to have him on the PSC. +1 Howard ___

Re: [geos-devel] deprecate non-thread-safe CAPI interfaces

On Feb 11, 2010, at 11:36 AM, strk wrote: > On Wed, Feb 10, 2010 at 09:42:56PM -0600, Howard Butler wrote: >> >> On Feb 10, 2010, at 5:26 PM, strk wrote: >> >>> I'd like to deprecate non-thread-safe version >>> of CAPI interface in next release,

Re: [geos-devel] deprecate non-thread-safe CAPI interfaces

On Feb 10, 2010, at 5:26 PM, strk wrote: > I'd like to deprecate non-thread-safe version > of CAPI interface in next release, and stop providing > them for new methods. > > If anyone sees a reason not to do that please scream > before it's too late (you've plenty of time). The proposal would be

Re: [geos-devel] Porting LengthIndexedLine.project?

Filing a ticket and attaching the patch is the best way to ensure it doesn't get lost. Putting a milestone on it (like 3.2) will also help ensure someone looks at it. Howard On Aug 11, 2009, at 8:22 PM, David Turner wrote: Did I send this to the right place? Or should I create a ticket s

Re: [geos-devel] Automake 1.10 vs. Automake 1.9.5

On Mar 20, 2009, at 1:13 PM, Philip Mason wrote: In terms of substantive code changes, there were only 4 or 5 source files that I needed to merge into my working copy ... Are you maintaining your own internal fork of GEOS? The license police might not like that... Howard

Re: [geos-devel] astyle --style=kr

On Mar 10, 2009, at 1:03 PM, Paul Ramsey wrote: I propose running astyle --style=kr on the whole GEOS code base just prior to releasing the final tarball and tagging 3.0.0. This will put everything to the same code formatting, so hopefully patches going forward will contain all logic a

Re: [geos-devel] Chuck Thibert as Committer

On Jan 13, 2009, at 11:08 AM, Paul Ramsey wrote: PSC, Chuck has now created and had accepted a large patch to the code base, I'd like to make him a committer. I caused more trouble applying his patch than any other process would :) +1 subject to acceptance of RFC 2 http://trac.osgeo.org/geos

Re: [geos-devel] Steven Wong as Committer

+1. On Nov 26, 2008, at 1:21 PM, Paul Ramsey wrote: Steven works at Safe, and has contributed a number of patches... http://trac.osgeo.org/geos/search?q=swongu&wiki=on&changeset=on&ticket=on I'd like to see these folks who are actively producing patches have direct access to the repository, s

Re: [geos-devel] Thread Safe CAPI RFC3 approved

On Nov 10, 2008, at 9:27 AM, Chuck Thibert wrote: Hi all, I have: Paul, Howard, strk and Frank all at +1, and Martin abstaining. Sandro isn't on the PSC, so his vote doesn't count for this RFC. I think he should be, however. I will motion that in a separate email. Additionally, http

[geos-devel] Motion: Add Sandro Santilli to GEOS PSC

PSC Members, I would like to motion to add Sandro Santilli to the PSC. Sandro wrote a lot of GEOS, and his input, direction, and historical perspective is beneficial to the project. /me starts with a +1 Howard ___ geos-devel mailing list geos-de

Re: [geos-devel] Thread Safe CAPI RFC acceptance...

On Nov 3, 2008, at 6:10 PM, Martin Davis wrote: I agree. Some parts of the JTS API are not reentrant, and I'm not sure if this got transferred to GEOS. And I have no idea what other non-reentrant things might have crept in. Since I can't vote knowledgeably, I will simply abstain. (Like a

Re: [geos-devel] RFC for Thread safe CAPI announced

On Oct 17, 2008, at 2:06 PM, Frank Warmerdam wrote: I'd add that I'd like the RFC to define the context of the context structure. I also think that the application visible handle should be declared: type void *GEOSContextHandle_t; I would suggest we change this to: typedef struct GEOS

Re: [geos-devel] Participating in OSGeo Project Sponsorship Program

+1. On Oct 10, 2008, at 5:17 PM, Paul Ramsey wrote: PSC members, I'd like to get official approval from you to engage in the OSGeo Project Sponsorship program. The upshot of the Program is: http://wiki.osgeo.org/wiki/Project_Sponsorship - OSGeo acts as the banker, invoicing sponsors and hold

Re: [geos-devel] Re: [postgis-devel] Shhhh....

The 3.0 branch of GEOS does not have anything in it about prepared geometries. http://trac.osgeo.org/geos/log/branches/3.0 Did you mean to say release a 3.1 version of GEOS with non-leaky prepared geometries? I don't think we should do minor releases with major features in them. Howard On

Re: [geos-devel] Tabs versus spaces?

On Aug 29, 2008, at 11:03 AM, Charlie Savage wrote: +1 for spaces on my side. And just to really stir things up, I'd go for an indentation of 2 spaces I think it is an OSGeo standard for all source code to be spaces with an indentation level of 4 spaces :) We don't want to jeopardize

Re: [geos-devel] Tabs versus spaces?

On Aug 29, 2008, at 10:42 AM, Mateusz Loskot wrote: Sean Gillies wrote: I'm finding a lot of tabs in the GEOS source -- is this our convention? Sean, AFAIR, Sandro preferred to use tabs. I've also found it inconvenient as I personally believe in spaces :-) Perhaps, if others will agree

Re: [geos-devel] [Agreement] GEOS RFC 2: Committer Guidelines

Ramsey (124, 2007-12-21) * mbdavis - Martin Davis (1, 2003-02-11) * hobu - Howard Butler (17, 2006-11-10) * mloskot - Mateusz Loskot (136, 2008-08-01) * csavage - Charlie Savage (102, 2007-09-21) * frank, warmerdam - Frank Warmerdam (27, 2008-07-19) * sgillies - Sean Gillies (10, 2008

Re: [geos-devel] RFC1 - Call for Vote

+1 On Apr 9, 2008, at 6:19 PM, Gary Crawford wrote: +1 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Mateusz Loskot Sent: Wednesday, April 09, 2008 3:26 PM To: GEOS Development List Subject: Re: [geos-devel] RFC1 - Call for Vote Paul Ramsey wrote

Re: [geos-devel] Bootstrap PSC

+1 for me. I'm still willing to participate as PSC member. Additionally, I would also like to nominate Mateusz Loskot for the GEOS PSC membership list. His work has left a huge imprint on GEOS, and he's kept things rolling through the various developmental lulls in the project after Sandr

Re: [geos-devel] GEOS 3.1

+1. Let's go final with what's in trunk (RC5 + a few small OSX Leopard tweaks). Howard On Dec 20, 2007, at 5:39 PM, Frank Warmerdam wrote: Paul Ramsey wrote: It may seem precipitate to talk about 3.1 when we've spend over a year in 3.0.0rcX, but Ben's work on the JTS upgrade and Prepare

[geos-devel] Nightly/Hourly distros

It appears that the nightly distro isn't being built against the new subversion server. I attempted to fetch it this morning looking for Mateusz's updates for OS X, but they hadn't been applied in http://geos.refractions.net/geos-svn.tar.bz2 Can someone look into this? Thanks, Howard _

Re: [geos-devel] Bugs Migrated

On Nov 21, 2007, at 6:37 PM, Mateusz Loskot wrote: Howard Butler wrote: All, The bug list has now been migrated to Trac on OSGeo's infrastructure: http://trac.osgeo.org/geos/report/6 I've tried to clean tickets according to milestones, versions and components. It's possi

[geos-devel] Bugs Migrated

All, The bug list has now been migrated to Trac on OSGeo's infrastructure: http://trac.osgeo.org/geos/report/6 To edit the wiki pages and bug/enhancement/task tickets, you'll need to login with an OSGeo Userid. http://www.osgeo.org/osgeo_userid Hopefully, someone will login and update the

Re: [geos-devel] SVN Repository Move

If you are planning to commit to the repository, you should probably use the SSL version: https://svn.osgeo.org/geos/ to slow down your ability to make commits too quickly and pacify your paranoia :) Howard On Nov 12, 2007, at 2:57 PM, Paul Ramsey wrote: The SVN Repository HAS MOVED. It