I performed an "experiment" today merging the wcs branch into a 1.4.x comunity module. The actual copying over was pretty mechanical as its just ripping out hte WCS specific classes, as was done with WFS and WMS some time ago.
The only problem is of course, the UI. Even with our modules on 1.4.x the web app is still a single module which depends on all other modules. What this means that it will be hard to have wcs on 1.4.x without affecting the rest of the app.
Unfortunatley waiting for wcs to come home is somewhat of a problem. There are a couple of projects (SENS,OWS-4) which need 1.4.x on trunk.
We can talk this over with the WCS team at IRC meeting tommorow but the best solution may be to wait on wcs merge until after 1.4.x becomes trunk. The down side is that it will be more work than merging to trunk as it stands today. However, not a huge amount, I can explain more of the specifics at the meeting. And I will personally volunteer my time up to help with the merge and the transition to 1.4.x. Which I would have to do anyways if wcs merged onto trunk first.
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Yes, I think WCS will have to wait for 1.4.x. WCS will be 1.5. This is what I'd been thinking for awhile, was kinda surprised to see you guys contemplating getting it on before. I think the thing to do is just get everyone helping out when we sync up WCS with 1.4.x.
Chris
Justin Deoliveira wrote:
Hi all,
I performed an "experiment" today merging the wcs branch into a 1.4.x comunity module. The actual copying over was pretty mechanical as its just ripping out hte WCS specific classes, as was done with WFS and WMS some time ago.
The only problem is of course, the UI. Even with our modules on 1.4.x the web app is still a single module which depends on all other modules. What this means that it will be hard to have wcs on 1.4.x without affecting the rest of the app.
Unfortunatley waiting for wcs to come home is somewhat of a problem. There are a couple of projects (SENS,OWS-4) which need 1.4.x on trunk.
We can talk this over with the WCS team at IRC meeting tommorow but the best solution may be to wait on wcs merge until after 1.4.x becomes trunk. The down side is that it will be more work than merging to trunk as it stands today. However, not a huge amount, I can explain more of the specifics at the meeting. And I will personally volunteer my time up to help with the merge and the transition to 1.4.x. Which I would have to do anyways if wcs merged onto trunk first.
Well I wanted to see if we could make the wcs standalone enough to just turn it off in the regular build, but i dont think that is going to happen. So yeah, I agree that we just pull double duty when the time comes.
-Justin
Chris Holmes wrote:
Yes, I think WCS will have to wait for 1.4.x. WCS will be 1.5. This is what I'd been thinking for awhile, was kinda surprised to see you guys contemplating getting it on before. I think the thing to do is just get everyone helping out when we sync up WCS with 1.4.x.
Chris
Justin Deoliveira wrote:
Hi all,
I performed an "experiment" today merging the wcs branch into a 1.4.x comunity module. The actual copying over was pretty mechanical as its just ripping out hte WCS specific classes, as was done with WFS and WMS some time ago.
The only problem is of course, the UI. Even with our modules on 1.4.x the web app is still a single module which depends on all other modules. What this means that it will be hard to have wcs on 1.4.x without affecting the rest of the app.
Unfortunatley waiting for wcs to come home is somewhat of a problem. There are a couple of projects (SENS,OWS-4) which need 1.4.x on trunk.
We can talk this over with the WCS team at IRC meeting tommorow but the best solution may be to wait on wcs merge until after 1.4.x becomes trunk. The down side is that it will be more work than merging to trunk as it stands today. However, not a huge amount, I can explain more of the specifics at the meeting. And I will personally volunteer my time up to help with the merge and the transition to 1.4.x. Which I would have to do anyways if wcs merged onto trunk first.
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
I performed an "experiment" today merging the wcs branch into a 1.4.x comunity module. The actual copying over was pretty mechanical as its just ripping out hte WCS specific classes, as was done with WFS and WMS some time ago.
Nicely done.
The only problem is of course, the UI. Even with our modules on 1.4.x the web app is still a single module which depends on all other modules. What this means that it will be hard to have wcs on 1.4.x without affecting the rest of the app.
Can we look into splitting the config app up? It is something that struts supports ... I know it is more
work then we would like to do but having WCS in the game would be a bug plus.
Unfortunatley waiting for wcs to come home is somewhat of a problem. There are a couple of projects (SENS,OWS-4) which need 1.4.x on trunk.
SENS and OWS-4 may be able to work off a stable branch? Of the two I imagine only OWS-4 plans
to stir things up.
We can talk this over with the WCS team at IRC meeting tommorow but the best solution may be to wait on wcs merge until after 1.4.x becomes trunk. The down side is that it will be more work than merging to trunk as it stands today. However, not a huge amount, I can explain more of the specifics at the meeting. And I will personally volunteer my time up to help with the merge and the transition to 1.4.x. Which I would have to do anyways if wcs merged onto trunk first.
I performed an "experiment" today merging the wcs branch into a 1.4.x comunity module. The actual copying over was pretty mechanical as its just ripping out hte WCS specific classes, as was done with WFS and WMS some time ago.
Nicely done.
The only problem is of course, the UI. Even with our modules on 1.4.x the web app is still a single module which depends on all other modules. What this means that it will be hard to have wcs on 1.4.x without affecting the rest of the app.
Can we look into splitting the config app up? It is something that struts supports ... I know it is more
work then we would like to do but having WCS in the game would be a bug plus.
No. If we're doing major struts work we should probably just invest that in a new system, since no one likes the current system. WCS can come in to the game for 1.5. If 1.4 gets stable quick then WCS should be able to go to beta releases pretty soon.
Chris
Unfortunatley waiting for wcs to come home is somewhat of a problem. There are a couple of projects (SENS,OWS-4) which need 1.4.x on trunk.
SENS and OWS-4 may be able to work off a stable branch? Of the two I imagine only OWS-4 plans
to stir things up.
We can talk this over with the WCS team at IRC meeting tommorow but the best solution may be to wait on wcs merge until after 1.4.x becomes trunk. The down side is that it will be more work than merging to trunk as it stands today. However, not a huge amount, I can explain more of the specifics at the meeting. And I will personally volunteer my time up to help with the merge and the transition to 1.4.x. Which I would have to do anyways if wcs merged onto trunk first.