Looks like gmail address are back, so we can return to the geoserver-devel list....
Let me state this a bit more clearly. Brent and I are both confused if either of you were planning on a 1.3.x release off of trunk with the ip fixes.
We were planning, I think you said the IP changes were ready?
If you had, we ask that you hold it off. Brent will do a 1.3.1 release today or tomorrow, that will be 1.3.1beta plus KML. This will make sense from a linear perspective, whereas a 1.3.1 with just ip fixes off of trunk wouldn't make sense, as it wouldn't have the updated 2.2.x jars.
I looked at your roadmap but did not see this plan? How should we communicate this in the future?
1.3.1 will be done off the 1.3.1beta branch. It will then be merged after to be 1.3.2.
So what are we releasing from trunk? 1.3.2beta?
Aside: 1.4.x includes the integrated taz demo, we we are going to target the uDig users at it.
Jody
Brent Owens wrote:
I need to clear some things up for the release.
Is the trunk release going out this week?
The 1.3.1 beta release was a test of geotools 2.2.x with geoserver. The 2.2.x branch hasn't been merged to trunk yet and if we leave it out and release, nothing will be consistent from the beta.
I can merge trunk in next week (thursday/friday the 15th, 16th).But we need to get a release out soon with the IP fixes. I have merged the fixes from trunk onto the 2.2.x branch and can kick out a release today from there.
Also, for the Where 2.0 conference (next week), we would like to have a release up that contains the KML code, currently not on trunk. Since it will be demoed. Either way a release with the KML code needs to happen within the next day or so, either as a "1.3.1kml" release, or just as "1.3.1".
Thoughts?