Week in Review
- From:
- David Winslow
- Date:
- 2011-05-07 @ 18:42
Hey all,
I missed last week's mail so I'll try to cover a couple of weeks' events in
this email.
On the master branch, some minor bugs have been resolved:
#952<http://dev.geonode.org/trac/ticket/952> preventing
the keywords in GeoNode from propagating to GeoServer, and
#940<http://dev.geonode.org/trac/ticket/940> which
caused some i18n errors in IE.
Matt Bertrand from WorldMap has been working to bring functionality into
GeoNode which will allow uploaded data to be imported straight to PostGIS.
The necessary improvements to gsconfig have already been reviewed and
merged, and Matt is working on the changes to the GeoNode application.
Gabriel Roldan from OpenGeo has been working on some changes to the way
GeoServer integrates with Django, which promise great speed improvements for
GeoServer operations such as map tile requests.
A Continuous Integration<http://en.wikipedia.org/wiki/Continuous_integration>
server
has been set up on OpenGeo hardware to automatically run GeoNode's test
suite. Ariel Nuñez from the World Bank and Jeff Johnson from OpenGeo have
been working on increasing the quality and quantity of tests in that suite.
If you would like to see the test reports, they are publicly viewable at
http://geonode-testing.dev.opengeo.org:8080/ . There are charts on the
pages for the subprojects, varying a bit based on the nature of the
subproject. For example, we don't have an automated test suite for the
JavaScript components ("geonode-client") so there are no charts, but the
"geonode-server" project has test and test coverage reports at
http://geonode-testing.dev.opengeo.org:8080/job/geonode-server/
The upload patch submitted by Ariel Nuñez and Ole Nielsen is nearly ready
for integration into the core geonode project - the issues raised in review
have been addressed and we are just waiting to give the original authors a
chance to provide feedback on those changes.
The GeoNode Project Steering Committee has decided to make the next release
of GeoNode 1.1 Beta (instead of 1.0.1), to allow us to start focussing on
compatiblity with GeoServer 2.1 and taking advantage of some performance and
stability improvements in that revision. There are more details at this
previous post on this mailing list:
http://librelist.com/browser//geonode/2011/5/5/geonode-stability-and-the-1-1-release-series/
Finally, OpenGeo will be providing some recommendations on setting up
production GeoNode sites to reduce the stability problems users have been
reporting. I hope that these will be available early next week.
--
David Winslow
OpenGeo - http://opengeo.org/
Re: [geonode] Week in review
- From:
- Ariel Nunez
- Date:
- 2011-04-18 @ 13:24
David, excellent write up.
I am very proud of the response of the GeoNode community (and the
organizations behind us). Personally I would like to thank you and
Jeff for setting up the test suite, CI server and making progress in
debugging the GeoNetwork issues. Officially I would like to thank
OpenGeo and Sebastian for upgrading the priority of these tasks
I look forward to helping through these week and finalizing the upload
refactor patch.
Ariel
On Fri, Apr 15, 2011 at 6:07 PM, David Winslow <dwinslow@opengeo.org> wrote:
> Hey all,
> I just thought since more folks have been expressing interest in GeoNode
> development (especially the testing stuff) I'd try and start sending
> periodic status updates on the project (I will aim for weekly frequency but
> I make no promises since I am easily distracted :) Anyway, this week has
> seen a big push on automated testing, prompted largely by feedback from
> Ariel and the AIFDR crew. (AIFDR is developing a GeoNode-based tool called
> Risiko, and since GeoNode is their foundation its stability is quite
> important to them.)
> In that interest, we at OpenGeo have set up a continuous integration server
> at http://geonode-testing.dev.opengeo.org/ which will monitor the software
> repositories and re-run our test suite automatically after changes are made.
> (We still expect developers to test their own code, but having this service
> allows us to make some guarantees.)
> While we did have a basic test suite before this week, it missed some
> important pieces of functionality such as file upload and permissions, so
> Jeff has been working with Ariel on improving it. (You'll note this code is
> not yet in the master branch. So far, the tests are dependent on a patch
> Ariel submitted earlier this week which is still pending review; hopefully
> we'll be able to pull this in next week.) Jeff is also developing a more
> extensive test suite (using sample data provided by AIFDR) to verify cases
> which require more extensive setup than the unit tests included with each
> project.
> Jeff's unit test
> branch: http://github.com/jj0hns0n/geonode/tree/bulletproof/
> Jeff's extended unit testing
> suite: https://github.com/jj0hns0n/geonode-tests/
> Beyond improving the automated testing situation for GeoNode, here are some
> other things that happened this week:
>
> AIFDR-funded development on automatic styling means that someday soon raster
> layers uploaded to GeoNode will have their NODATA values made transparent
> and the coloration based on the range of values present, rather than our
> current default which presents several rendering artifacts. For the
> adventurous, the experimental branch is available
> at https://github.com/dwins/geonode/tree/smart-rasters
> We've spent some time investigating the stability issues affecting
> GeoNetwork, and made some changes to GeoNode to mitigate the problem. This
> code has been deployed to the GeoNode demo site for testing and will
> hopefully be released as GeoNode 1.0.1 next week.
>
> Thanks for reading.
> --
> David Winslow
> OpenGeo - http://opengeo.org/
Re: [geonode] Week in review
- From:
- Jude Mwenda
- Date:
- 2011-04-16 @ 09:52
Updates on geonetwork.
2011/4/16 David Winslow <dwinslow@opengeo.org>
> Hey all,
>
> I just thought since more folks have been expressing interest in GeoNode
> development (especially the testing stuff) I'd try and start sending
> periodic status updates on the project (I will aim for weekly frequency but
> I make no promises since I am easily distracted :) Anyway, this week has
> seen a big push on automated testing, prompted largely by feedback from
> Ariel and the AIFDR crew. (AIFDR is developing a GeoNode-based tool called
> Risiko, and since GeoNode is their foundation its stability is quite
> important to them.)
>
> In that interest, we at OpenGeo have set up a continuous
integration<http://en.wikipedia.org/wiki/Continuous_integration>server at
> http://geonode-testing.dev.opengeo.org/ which will monitor the software
> repositories and re-run our test suite automatically after changes are made.
> (We still expect developers to test their own code, but having this service
> allows us to make some guarantees.)
>
> While we did have a basic test suite before this week, it missed some
> important pieces of functionality such as file upload and permissions, so
> Jeff has been working with Ariel on improving it. (You'll note this code is
> not yet in the master branch. So far, the tests are dependent on a patch
> Ariel submitted earlier this week which is still pending review; hopefully
> we'll be able to pull this in next week.) Jeff is also developing a more
> extensive test suite (using sample data provided by AIFDR) to verify cases
> which require more extensive setup than the unit tests included with each
> project.
>
> Jeff's unit test branch:
> http://github.com/jj0hns0n/geonode/tree/bulletproof/
> Jeff's extended unit testing suite:
> https://github.com/jj0hns0n/geonode-tests/
>
> Beyond improving the automated testing situation for GeoNode, here are some
> other things that happened this week:
>
> - AIFDR-funded development on automatic styling means that someday soon
> raster layers uploaded to GeoNode will have their NODATA values made
> transparent and the coloration based on the range of values present, rather
> than our current default which presents several rendering artifacts. For
> the adventurous, the experimental branch is available at
> https://github.com/dwins/geonode/tree/smart-rasters
> - We've spent some time investigating the stability issues affecting
> GeoNetwork, and made some changes to GeoNode to mitigate the problem. This
> code has been deployed to the GeoNode demo site for testing and will
> hopefully be released as GeoNode 1.0.1 next week.
>
> Thanks for reading.
>
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>
Re: [geonode] Week in review
- From:
- David Winslow
- Date:
- 2011-04-18 @ 11:54
I'm not sure if you are asking a question here - but if you want more
information on the investigation I've been doing into GeoNetwork see this
thread from the development list:
https://groups.google.com/a/opengeo.org/group/geonode-dev/browse_thread/thread/024afcae8472493b#
--
David Winslow
OpenGeo - http://opengeo.org/
On Sat, Apr 16, 2011 at 5:52 AM, Jude Mwenda <jude@upande.com> wrote:
> Updates on geonetwork.
>
>
> 2011/4/16 David Winslow <dwinslow@opengeo.org>
>
>> Hey all,
>>
>> I just thought since more folks have been expressing interest in GeoNode
>> development (especially the testing stuff) I'd try and start sending
>> periodic status updates on the project (I will aim for weekly frequency but
>> I make no promises since I am easily distracted :) Anyway, this week has
>> seen a big push on automated testing, prompted largely by feedback from
>> Ariel and the AIFDR crew. (AIFDR is developing a GeoNode-based tool called
>> Risiko, and since GeoNode is their foundation its stability is quite
>> important to them.)
>>
>> In that interest, we at OpenGeo have set up a continuous
integration<http://en.wikipedia.org/wiki/Continuous_integration>server at
>> http://geonode-testing.dev.opengeo.org/ which will monitor the software
>> repositories and re-run our test suite automatically after changes are made.
>> (We still expect developers to test their own code, but having this service
>> allows us to make some guarantees.)
>>
>> While we did have a basic test suite before this week, it missed some
>> important pieces of functionality such as file upload and permissions, so
>> Jeff has been working with Ariel on improving it. (You'll note this code is
>> not yet in the master branch. So far, the tests are dependent on a patch
>> Ariel submitted earlier this week which is still pending review; hopefully
>> we'll be able to pull this in next week.) Jeff is also developing a more
>> extensive test suite (using sample data provided by AIFDR) to verify cases
>> which require more extensive setup than the unit tests included with each
>> project.
>>
>> Jeff's unit test branch:
>> http://github.com/jj0hns0n/geonode/tree/bulletproof/
>> Jeff's extended unit testing suite:
>> https://github.com/jj0hns0n/geonode-tests/
>>
>> Beyond improving the automated testing situation for GeoNode, here are
>> some other things that happened this week:
>>
>> - AIFDR-funded development on automatic styling means that someday
>> soon raster layers uploaded to GeoNode will have their NODATA values made
>> transparent and the coloration based on the range of values present, rather
>> than our current default which presents several rendering artifacts. For
>> the adventurous, the experimental branch is available at
>> https://github.com/dwins/geonode/tree/smart-rasters
>> - We've spent some time investigating the stability issues affecting
>> GeoNetwork, and made some changes to GeoNode to mitigate the problem. This
>> code has been deployed to the GeoNode demo site for testing and will
>> hopefully be released as GeoNode 1.0.1 next week.
>>
>> Thanks for reading.
>>
>> --
>> David Winslow
>> OpenGeo - http://opengeo.org/
>>
>
>