If the people whose names on the list could reply with a quick status update that would be great.
I won't go into the lower priority issues. But if there are any issues that need to promoted or demoted, or that you just wish to comment on, please reply accordingly.
Thanks,
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I just committed a means to keep the namespace synchronized with the workspace anytime the workspace changes.
It uses an ajax call to update the namespace drop down, and the namespace dropdown is disabled to void manual changes.
The odd thing is the "onchange" event for the workspace dropdown doesn't seem to be triggered if you select a different workspace with the up/down arrow keys instead of using the mouse...
any idea what event should I listen for to cover that case?
code is something like:
wsDropDown.add(new AjaxFormComponentUpdatingBehavior("onchange") {
private static final long serialVersionUID = 1L;
Working on wicket ui test coverage, will tackle this one tomorrow
Done pumping up the code coverage. Current levels:
- web-core: 61%
- demo: 52%
- wms: 60%
- wfs: 67%
- wcs: 69%
- app: 44%
So it seems to be good for graduation.
Downside: it now takes 2 minutes to build web2... I have
to look into it, my guess is that it still takes a lot of time
to look up the i18n strings but it's just a gut feeling
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
So as per recent discussion, discussing the road map is to be moved to email. So here goes the first update:
* 2.0-beta2 release date
The new date on the table for beta2 is next Monday, July 13
* Issue status update
It has been brought to my attention that there is no mention on the short term road map of app-schema. My apologies for this blunder.
(This was the missing bit, needed to get it formally into the short-term roadmap).
Monday should still be OK if we can get the default 512M for tests on Hudson. Otherwise, we will be blocked for perhaps weeks trying to reduce the memory footprint of the tests.
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
So as per recent discussion, discussing the road map is to be moved to email. So here goes the first update:
* 2.0-beta2 release date
The new date on the table for beta2 is next Monday, July 13
* Issue status update
It has been brought to my attention that there is no mention on the short term road map of app-schema. My apologies for this blunder.
No worries Ben, the process is not well documented, and I sort of just assumed that people were aware of it. So apologies. That said, as you have stated you have went through all the paces of the proposal etc, so its close.
I for one would be fine with pushing back the release a few days to ensure app-schema gets in, since it is so close and all that really needs to be done is voting. If others feel the same way we can move the proposal through the vote, fix all the issues with the build (upping memory seems to be the short term solution), and do the move to extension. Then release.
(This was the missing bit, needed to get it formally into the short-term roadmap).
Monday should still be OK if we can get the default 512M for tests on Hudson. Otherwise, we will be blocked for perhaps weeks trying to reduce the memory footprint of the tests.
Kind regards,
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I for one would be fine with pushing back the release a few days to
ensure app-schema gets in, since it is so close and all that really
needs to be done is voting. If others feel the same way we can move the
proposal through the vote, fix all the issues with the build (upping
memory seems to be the short term solution), and do the move to
extension. Then release.
Comments?
I would be fine with delaying the release (and have already voted on
the GSIP). In terms of scheduling I think it would be really important
to get this feature (and associated documentation) some community
exposure and testing earlier rather than later.
So as per recent discussion, discussing the road map is to be moved to email. So here goes the first update:
* 2.0-beta2 release date
The new date on the table for beta2 is next Monday, July 13
* Issue status update
It has been brought to my attention that there is no mention on the short term road map of app-schema. My apologies for this blunder.
No worries Ben, the process is not well documented, and I sort of just assumed that people were aware of it. So apologies. That said, as you have stated you have went through all the paces of the proposal etc, so its close.
I for one would be fine with pushing back the release a few days to ensure app-schema gets in, since it is so close and all that really needs to be done is voting. If others feel the same way we can move the proposal through the vote, fix all the issues with the build (upping memory seems to be the short term solution), and do the move to extension. Then release.
Comments?
Works for me
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
No worries Ben, the process is not well documented, and I sort of just assumed that people were aware of it. So apologies. That said, as you have stated you have went through all the paces of the proposal etc, so its close.
You made me aware of it ... I just didn't understand it.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia