Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
The major hurdle in doing the merge is that wcs branch is built against the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a position to merge for quite some time yet, on the order of weeks, and more then likley months. This conflicts with Jody's project which requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option #1 does not work for Jody's project timewise.
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
About tommorows IRC, its pretty important that everyone CC'd on this mail attend at the same time. Either 7:00 UTC, or 19:00 UTC.
As for me I can do either. What about everyone else.
-Justin
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
The major hurdle in doing the merge is that wcs branch is built against the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a position to merge for quite some time yet, on the order of weeks, and more then likley months. This conflicts with Jody's project which requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option #1 does not work for Jody's project timewise.
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
I am prepared to do either, but not both. So where the highest avg of people will attend, I will attend as well.
Kind Regards
Clint Lewis
Justin Deoliveira wrote:
About tommorows IRC, its pretty important that everyone CC'd on this mail attend at the same time. Either 7:00 UTC, or 19:00 UTC.
As for me I can do either. What about everyone else.
-Justin
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
The major hurdle in doing the merge is that wcs branch is built against the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a position to merge for quite some time yet, on the order of weeks, and more then likley months. This conflicts with Jody's project which requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option #1 does not work for Jody's project timewise.
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
For the 7:00 UTC would be better but I cannot use IRC at that time, only Skype.
If it’s not possible to have a Skype meeting in the morning then 19:00 UTM is the only chance for me.
I am prepared to do either, but not both. So where the highest avg of
people will attend, I will attend as well.
Kind Regards
Clint Lewis
Justin Deoliveira wrote:
About tommorows IRC, its pretty important that everyone CC’d on this
mail attend at the same time. Either 7:00 UTC, or 19:00 UTC.
As for me I can do either. What about everyone else.
-Justin
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve
some issues before the move to trunk. The major issue is the wcs branch.
If 1.4.x moves to trunk before wcs then it will significantly harder to
ever bring wcs home. And we cant really afford another complex-features
nightmare.
The major hurdle in doing the merge is that wcs branch is built against
the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x
is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a
position to merge for quite some time yet, on the order of weeks, and
more then likley months. This conflicts with Jody’s project which
requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
Merge wcs branch to trunk:
Wait for geotools gc merge to complete
move geoserver trunk to geotools trunk, or a stable 2.3.x branch
merge wcs onto geoserver trunk
merge trunk onto 1.4.x
1.4.x becomes new trunk
Merge wcs branch to 1.4.x
wcs becomes 1.4.x module
merge trunk to 1.4.x
1.4.x becomes new trunk
Option #1 does not work for Jody’s project timewise.
Option #2 is faster as we dont have to wait for the geotools branch
merge. However it relies on the fact that we must build geoserver
against two different versions of getools: 2.2.x, and gc-branch. With
the new maven 2 build system, this should be possible. However we would
not be able to release geoserver with wcs until they are both on
geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
-Justin
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
I suspect some of the minor issues show up with Brent's KML work.
- do you need another documentation release from GEOSDOC before things merge?
- when in the release cycle is KML being placed onto trunk?
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
Ack, please no fork. If geotools was making releases these days maybe.
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option 2 here missed out on the upgrade to GeoTools 2.3 step. Also for it to work for me we would need a matching uDig.
So let me try Option 3 (ie what I though was happening .... )
Option 3
1. merge trunk to 1.4.x
2. 1.4.x becomes the new trunk
3. trunk releases 1.4.0 is released with docs
4. wait for geotools gc merge to complete
5. trunk moves to geotools trunk
6. wcs becomes a geoserver module
7. trunk releases 1.4.1 with a WCS community module
8. user docs are completed for WCS ...
9. trunk releases 1.5.0
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
I think I see, so WCS would be "out of the build", but would have seperate build instructions ...
Those are the issues. Next GeoServer IRC meeting will be an important one.
I think tonights geotools IRC will be interesting as well.
Jody
Do you need to do a documentation export from GEOSDOC for your 1.3.2 release? Justin has us scheduled to hack it up this week.
Jody
KML is on trunk, and there shouldn't be many issues merging it in. It
works fine in the WCS branch. Only a couple changes in WMS.
- Brent
On 7/3/06, Jody Garnett <jgarnett@anonymised.com> wrote:
Justin Deoliveira wrote:
> Hi all,
>
> Before the release train gathers up too much steam, we need to resolve
> some issues before the move to trunk. The major issue is the wcs
> branch. If 1.4.x moves to trunk before wcs then it will significantly
> harder to ever bring wcs home. And we cant really afford another
> complex-features nightmare.
I suspect some of the minor issues show up with Brent's KML work.
- do you need another documentation release from GEOSDOC before things
merge?
- when in the release cycle is KML being placed onto trunk?
> So we have a couple of ways to proceed.
>
> 1. Merge wcs branch to trunk:
> 1. Wait for geotools gc merge to complete
> 2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
> 3. merge wcs onto geoserver trunk
> 4. merge trunk onto 1.4.x
> 5. 1.4.x becomes new trunk
Ack, please no fork. If geotools was making releases these days maybe.
> 2. Merge wcs branch to 1.4.x
> 1. wcs becomes 1.4.x module
> 2. merge trunk to 1.4.x
> 3. 1.4.x becomes new trunk
Option 2 here missed out on the upgrade to GeoTools 2.3 step. Also for
it to work for me we would need a matching uDig.
So let me try Option 3 (ie what I though was happening .... )
Option 3
1. merge trunk to 1.4.x
2. 1.4.x becomes the new trunk
3. trunk releases 1.4.0 is released with docs
4. wait for geotools gc merge to complete
5. trunk moves to geotools trunk
6. wcs becomes a geoserver module
7. trunk releases 1.4.1 with a WCS community module
8. user docs are completed for WCS ...
9. trunk releases 1.5.0
> Option #2 is faster as we dont have to wait for the geotools branch
> merge. However it relies on the fact that we must build geoserver
> against two different versions of getools: 2.2.x, and gc-branch. With
> the new maven 2 build system, this should be possible. However we
> would not be able to release geoserver with wcs until they are both on
> geotools trunk.
I think I see, so WCS would be "out of the build", but would have
seperate build instructions ...
> Those are the issues. Next GeoServer IRC meeting will be an important
> one.
I think tonights geotools IRC will be interesting as well.
Jody
Sorry, using gmail web mail while I fix my main machine. Not used to
it not auto replying-to-all.
- Brent
On 7/3/06, Jody Garnett <jgarnett@anonymised.com> wrote:
Hey brent can you hit reply to all next time
Do you need to do a documentation export from GEOSDOC for your 1.3.2
release? Justin has us scheduled to hack it up this week.
Jody
> KML is on trunk, and there shouldn't be many issues merging it in. It
> works fine in the WCS branch. Only a couple changes in WMS.
>
> - Brent
>
> On 7/3/06, Jody Garnett <jgarnett@anonymised.com> wrote:
>> Justin Deoliveira wrote:
>> > Hi all,
>> >
>> > Before the release train gathers up too much steam, we need to resolve
>> > some issues before the move to trunk. The major issue is the wcs
>> > branch. If 1.4.x moves to trunk before wcs then it will significantly
>> > harder to ever bring wcs home. And we cant really afford another
>> > complex-features nightmare.
>> I suspect some of the minor issues show up with Brent's KML work.
>> - do you need another documentation release from GEOSDOC before things
>> merge?
>> - when in the release cycle is KML being placed onto trunk?
>> > So we have a couple of ways to proceed.
>> >
>> > 1. Merge wcs branch to trunk:
>> > 1. Wait for geotools gc merge to complete
>> > 2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
>> > 3. merge wcs onto geoserver trunk
>> > 4. merge trunk onto 1.4.x
>> > 5. 1.4.x becomes new trunk
>> Ack, please no fork. If geotools was making releases these days maybe.
>> > 2. Merge wcs branch to 1.4.x
>> > 1. wcs becomes 1.4.x module
>> > 2. merge trunk to 1.4.x
>> > 3. 1.4.x becomes new trunk
>> Option 2 here missed out on the upgrade to GeoTools 2.3 step. Also for
>> it to work for me we would need a matching uDig.
>>
>> So let me try Option 3 (ie what I though was happening .... )
>>
>> Option 3
>> 1. merge trunk to 1.4.x
>> 2. 1.4.x becomes the new trunk
>> 3. trunk releases 1.4.0 is released with docs
>> 4. wait for geotools gc merge to complete
>> 5. trunk moves to geotools trunk
>> 6. wcs becomes a geoserver module
>> 7. trunk releases 1.4.1 with a WCS community module
>> 8. user docs are completed for WCS ...
>> 9. trunk releases 1.5.0
>> > Option #2 is faster as we dont have to wait for the geotools branch
>> > merge. However it relies on the fact that we must build geoserver
>> > against two different versions of getools: 2.2.x, and gc-branch. With
>> > the new maven 2 build system, this should be possible. However we
>> > would not be able to release geoserver with wcs until they are both on
>> > geotools trunk.
>> I think I see, so WCS would be "out of the build", but would have
>> seperate build instructions ...
>> > Those are the issues. Next GeoServer IRC meeting will be an important
>> > one.
>> I think tonights geotools IRC will be interesting as well.
>> Jody
>>
>> Using Tomcat but need to do more? Need to support web services,
>> security?
>> Get stuff done quickly with pre-integrated technology to make your
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
About tommorows IRC, its pretty important that everyone CC'd on this mail attend at the same time. Either 7:00 UTC, or 19:00 UTC.
As for me I can do either. What about everyone else.
-Justin
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
The major hurdle in doing the merge is that wcs branch is built against the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a position to merge for quite some time yet, on the order of weeks, and more then likley months. This conflicts with Jody's project which requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option #1 does not work for Jody's project timewise.
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
As for me. 7:00 UTC is pretty much impossible, I think it's like 3am here.
Brent Owens wrote:
19:00 UTC would work better for me.
Brent Owens
(The Open Planning Project)
Justin Deoliveira wrote:
About tommorows IRC, its pretty important that everyone CC'd on this mail attend at the same time. Either 7:00 UTC, or 19:00 UTC.
As for me I can do either. What about everyone else.
-Justin
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
The major hurdle in doing the merge is that wcs branch is built against the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a position to merge for quite some time yet, on the order of weeks, and more then likley months. This conflicts with Jody's project which requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option #1 does not work for Jody's project timewise.
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
KML is on trunk right now, and being released with 1.3.2.
Brent Owens
(The Open Planning Project)
Jody Garnett wrote:
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
I suspect some of the minor issues show up with Brent's KML work.
- do you need another documentation release from GEOSDOC before things merge?
- when in the release cycle is KML being placed onto trunk?
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
Ack, please no fork. If geotools was making releases these days maybe.
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option 2 here missed out on the upgrade to GeoTools 2.3 step. Also for it to work for me we would need a matching uDig.
So let me try Option 3 (ie what I though was happening .... )
Option 3
1. merge trunk to 1.4.x
2. 1.4.x becomes the new trunk
3. trunk releases 1.4.0 is released with docs
4. wait for geotools gc merge to complete
5. trunk moves to geotools trunk
6. wcs becomes a geoserver module
7. trunk releases 1.4.1 with a WCS community module
8. user docs are completed for WCS ...
9. trunk releases 1.5.0
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
I think I see, so WCS would be "out of the build", but would have seperate build instructions ...
Those are the issues. Next GeoServer IRC meeting will be an important one.
I think tonights geotools IRC will be interesting as well.
Jody
Lets call the meeting for 19:00 UTC with a meeting during the day with the WCS team. Simone, Allesio, what time works for you?
-Justin
Brent Owens wrote:
19:00 UTC would work better for me.
Brent Owens
(The Open Planning Project)
Justin Deoliveira wrote:
About tommorows IRC, its pretty important that everyone CC'd on this mail attend at the same time. Either 7:00 UTC, or 19:00 UTC.
As for me I can do either. What about everyone else.
-Justin
Justin Deoliveira wrote:
Hi all,
Before the release train gathers up too much steam, we need to resolve some issues before the move to trunk. The major issue is the wcs branch. If 1.4.x moves to trunk before wcs then it will significantly harder to ever bring wcs home. And we cant really afford another complex-features nightmare.
The major hurdle in doing the merge is that wcs branch is built against the gc-geotools branch, soon to be geotools trunk. And geoserver 1.4.x is built against 2.2.x. So we have a conflict.
After chatting with the wcs team I realize that they wont be in a position to merge for quite some time yet, on the order of weeks, and more then likley months. This conflicts with Jody's project which requires 1.4.x to be on trunk.
So we have a couple of ways to proceed.
1. Merge wcs branch to trunk:
1. Wait for geotools gc merge to complete
2. move geoserver trunk to geotools trunk, or a stable 2.3.x branch
3. merge wcs onto geoserver trunk
4. merge trunk onto 1.4.x
5. 1.4.x becomes new trunk
2. Merge wcs branch to 1.4.x
1. wcs becomes 1.4.x module
2. merge trunk to 1.4.x
3. 1.4.x becomes new trunk
Option #1 does not work for Jody's project timewise.
Option #2 is faster as we dont have to wait for the geotools branch merge. However it relies on the fact that we must build geoserver against two different versions of getools: 2.2.x, and gc-branch. With the new maven 2 build system, this should be possible. However we would not be able to release geoserver with wcs until they are both on geotools trunk.
Those are the issues. Next GeoServer IRC meeting will be an important one.
