Slashgeo Log In
New Joint GRASS/OSGeo-Newsletter vol. 4
posted by Satri
on Wednesday December 20, @01:21PM
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the small-but-significant-steps dept.
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the small-but-significant-steps dept.
The GRASS GIS team and the OSGeo announced the first combined GRASS-News / OSGeo-News volume [pdf, 5.3Mb]. From the newsletter: "It is my pleasure to introduce the future expansion
of GRASS-News. The next edition will be morphed into a broader Open Source Geospatial Newsletter covering projects from the OSGeo Foundation and beyond. The aim is to bring relevant news and articles to a larger audience by widening the focus and changing the name." The newsletter is 34 pages long.
Related Stories
Technology: GRASS GIS 6.2.1 Released
[+]
markusN writes "GRASS 6.2.1 is a new stable release which fixes several bugs discovered in the 6.2.0 source code. This release is solely for stability purposes and adds no new features. Besides bug fixes it also includes a number of new message translations, updates for the help pages, and will better handle errors caused by missing or incorrectly installed support software. It also introduces a new 3D raster module which was left out of the last release due to time constraints." The rest of the PR below.
Technology: GRASS GIS 6.2.3 Released 1 comment
[+]
The powerful open source GRASS GIS team has just released version 6.2.3: "This release fixes a number of bugs discovered in the 6.2.2 source code. It is primarily for stability purposes and adds minimal new features. Besides bug fixes it also includes a number of new message translations and updates for the help pages. Highlights include further maturation of the GRASS 6 GUI, vector, and database code. Some improvements have been backported from the GRASS 6.3 development branch where new development continues at a strong pace of approximately one code commit every hour, including major work on an all new cross-platform wxPython GUI and a native MS Windows port." Below I copied a few related previous stories.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
