|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 - 3 | Next > |
|
|
MGOS 2.0.1 statusHere's a status update on MGOS 2.0.1. I was waiting to get merge modules for the missing providers, but it doesn't look like that is going to happen for the already released FDO binaries (we will have them in future builds though). So now we're trying to figure out which version of FDO to install and once we have that I should be able to post a MGOS 2.0.1. This should all be resolved within a few days I hope.
Tom _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusThat sounds great.
Is there an updated Fusion for this build compared to 2.0? I believe that some significant bugs have been fixed since the 2.0 release, in selection and maybe in some of the canvas tools (select radius, distance measure, etc). Will we have an internal-only RC for this release, or are the changes small enough that you're comfortable with an untested point release? Jason -----Original Message----- From: Tom Fukushima Subject: [mapguide-internals] MGOS 2.0.1 status Here's a status update on MGOS 2.0.1. I was waiting to get merge modules for the missing providers, but it doesn't look like that is going to happen for the already released FDO binaries (we will have them in future builds though). So now we're trying to figure out which version of FDO to install and once we have that I should be able to post a MGOS 2.0.1. This should all be resolved within a few days I hope. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
Re: MGOS 2.0.1 statusOn Fri, May 2, 2008 at 9:25 AM, Jason Birch <Jason.Birch@...> wrote:
> That sounds great. > > Is there an updated Fusion for this build compared to 2.0? I believe > that some significant bugs have been fixed since the 2.0 release, in > selection and maybe in some of the canvas tools (select radius, distance > measure, etc). this fusion bug is rather critical http://trac.osgeo.org/fusion/ticket/2 it relates to tiled maps not being correctly positioned, ie fusion tiled maps are always incorrectly displayed with the wrong co-ordinates. It 'looks' ok, but it's in error I have also uploaded a tiny patch in trac for the linux apache conf issue http://trac.osgeo.org/mapguide/ticket/477 z > > Will we have an internal-only RC for this release, or are the changes > small enough that you're comfortable with an untested point release? > > Jason > > > -----Original Message----- > From: Tom Fukushima > Subject: [mapguide-internals] MGOS 2.0.1 status > > Here's a status update on MGOS 2.0.1. I was waiting to get merge > modules for the missing providers, but it doesn't look like that is > going to happen for the already released FDO binaries (we will have them > in future builds though). So now we're trying to figure out which > version of FDO to install and once we have that I should be able to post > a MGOS 2.0.1. This should all be resolved within a few days I hope. > > > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals > -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusTo follow up to myself....
As long as we take the Fusion that is in trunk, I think we're good for all the fixes up to 1.0.4, which is the most current release. There were some revisions between the revision used for MapGuide trunk and the 1.0.4 release, but I think that was all SVN migration stuff. There are certainly some other outstanding bugs in Fusion, but 1.0.5 appears to be a ways out. Fortunately, fusion is relatively easy to upgrade (at least between point releases). Jason ________________________________ From: mapguide-internals-bounces@... on behalf of Jason Birch Sent: Thu 2008-05-01 4:25 PM To: MapGuide Internals Mail List Subject: RE: [mapguide-internals] MGOS 2.0.1 status That sounds great. Is there an updated Fusion for this build compared to 2.0? I believe that some significant bugs have been fixed since the 2.0 release, in selection and maybe in some of the canvas tools (select radius, distance measure, etc). Will we have an internal-only RC for this release, or are the changes small enough that you're comfortable with an untested point release? Jason -----Original Message----- From: Tom Fukushima Subject: [mapguide-internals] MGOS 2.0.1 status Here's a status update on MGOS 2.0.1. I was waiting to get merge modules for the missing providers, but it doesn't look like that is going to happen for the already released FDO binaries (we will have them in future builds though). So now we're trying to figure out which version of FDO to install and once we have that I should be able to post a MGOS 2.0.1. This should all be resolved within a few days I hope. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
Re: MGOS 2.0.1 statusI think some of the new changes in Fusion recently are destined for a
1.1 release rather than a 1.0.5 release because they are new features rather than bug fixes. I will talk to Mike early next week about the state of the 1.0 branch vs trunk and try to bring over any important bug fixes. As Zac mentioned, the misalignment of the tiles seems like an important fix to get in, I'm not sure of the status of that. For a potential 1.1, I think we have a few more things to go in including some Jx work to factor out Prototype/Scriptaculous in favour of mootools. Cheers Paul On 1-May-08, at 11:01 PM, Jason Birch wrote: > To follow up to myself.... > > As long as we take the Fusion that is in trunk, I think we're good > for all the fixes up to 1.0.4, which is the most current release. > There were some revisions between the revision used for MapGuide > trunk and the 1.0.4 release, but I think that was all SVN migration > stuff. > > There are certainly some other outstanding bugs in Fusion, but 1.0.5 > appears to be a ways out. Fortunately, fusion is relatively easy to > upgrade (at least between point releases). > > Jason > > ________________________________ > > From: mapguide-internals-bounces@... on behalf of Jason > Birch > Sent: Thu 2008-05-01 4:25 PM > To: MapGuide Internals Mail List > Subject: RE: [mapguide-internals] MGOS 2.0.1 status > > > > That sounds great. > > Is there an updated Fusion for this build compared to 2.0? I believe > that some significant bugs have been fixed since the 2.0 release, in > selection and maybe in some of the canvas tools (select radius, > distance > measure, etc). > > Will we have an internal-only RC for this release, or are the changes > small enough that you're comfortable with an untested point release? > > Jason > > -----Original Message----- > From: Tom Fukushima > Subject: [mapguide-internals] MGOS 2.0.1 status > > Here's a status update on MGOS 2.0.1. I was waiting to get merge > modules for the missing providers, but it doesn't look like that is > going to happen for the already released FDO binaries (we will have > them > in future builds though). So now we're trying to figure out which > version of FDO to install and once we have that I should be able to > post > a MGOS 2.0.1. This should all be resolved within a few days I hope. > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals > > > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals __________________________________________ Paul Spencer Chief Technology Officer DM Solutions Group Inc http://www.dmsolutions.ca/ _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
Re: MGOS 2.0.1 statusI was sort of planning to fix the misalignment bug as part of some
refactoring work I'm doing to allow more than one map in a MapGroup (and allow other types of layers to be used). That work should definitely be targeted to a 1.1 release but it sounds like I should do a patch for the mis-alignment issue before that. I know what the problem is and don't think it would involve too much time. Mike Paul Spencer wrote: > I think some of the new changes in Fusion recently are destined for a > 1.1 release rather than a 1.0.5 release because they are new features > rather than bug fixes. I will talk to Mike early next week about the > state of the 1.0 branch vs trunk and try to bring over any important > bug fixes. As Zac mentioned, the misalignment of the tiles seems like > an important fix to get in, I'm not sure of the status of that. > > For a potential 1.1, I think we have a few more things to go in > including some Jx work to factor out Prototype/Scriptaculous in favour > of mootools. > > Cheers > > Paul > > On 1-May-08, at 11:01 PM, Jason Birch wrote: > >> To follow up to myself.... >> >> As long as we take the Fusion that is in trunk, I think we're good >> for all the fixes up to 1.0.4, which is the most current release. >> There were some revisions between the revision used for MapGuide >> trunk and the 1.0.4 release, but I think that was all SVN migration >> stuff. >> >> There are certainly some other outstanding bugs in Fusion, but 1.0.5 >> appears to be a ways out. Fortunately, fusion is relatively easy to >> upgrade (at least between point releases). >> >> Jason >> >> ________________________________ >> >> From: mapguide-internals-bounces@... on behalf of Jason >> Birch >> Sent: Thu 2008-05-01 4:25 PM >> To: MapGuide Internals Mail List >> Subject: RE: [mapguide-internals] MGOS 2.0.1 status >> >> >> >> That sounds great. >> >> Is there an updated Fusion for this build compared to 2.0? I believe >> that some significant bugs have been fixed since the 2.0 release, in >> selection and maybe in some of the canvas tools (select radius, distance >> measure, etc). >> >> Will we have an internal-only RC for this release, or are the changes >> small enough that you're comfortable with an untested point release? >> >> Jason >> >> -----Original Message----- >> From: Tom Fukushima >> Subject: [mapguide-internals] MGOS 2.0.1 status >> >> Here's a status update on MGOS 2.0.1. I was waiting to get merge >> modules for the missing providers, but it doesn't look like that is >> going to happen for the already released FDO binaries (we will have them >> in future builds though). So now we're trying to figure out which >> version of FDO to install and once we have that I should be able to post >> a MGOS 2.0.1. This should all be resolved within a few days I hope. >> _______________________________________________ >> mapguide-internals mailing list >> mapguide-internals@... >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals >> >> >> _______________________________________________ >> mapguide-internals mailing list >> mapguide-internals@... >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals > > > __________________________________________ > > Paul Spencer > Chief Technology Officer > DM Solutions Group Inc > http://www.dmsolutions.ca/ > > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals > mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
Re: MGOS 2.0.1 statusHi,
Great news that there will be a quick turnaround on getting a release out. Can I add the following points for discussion: * To enable us with projects and dependancies on MapGuide to have better visibility of schedules. The trac roadmap page says there will be a 2.1 release in "two months" but not a minor release. * It would be really good to see all the un-version-tagged issues reviewed so there is visibility of issues. I suspect many have been closed but there are over 100 sitting in http://trac.osgeo.org/mapguide/query?status=new&status=assigned&status=reopened&milestone=&order=id Many thanks for your consideration, Crispin
|
|
|
RE: MGOS 2.0.1 statusOK, it sounds like there are some Fusion fixes that we would like to get into 2.0.1. Do you have an ETA on when they will be in?
As for the other 2.0.1 changes, unless someone sees otherwise, I don't see anything that will require an RC. Tom -----Original Message----- From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@...] On Behalf Of Mike Adair Sent: Friday, May 02, 2008 7:37 AM To: MapGuide Internals Mail List Subject: Re: [mapguide-internals] MGOS 2.0.1 status I was sort of planning to fix the misalignment bug as part of some refactoring work I'm doing to allow more than one map in a MapGroup (and allow other types of layers to be used). That work should definitely be targeted to a 1.1 release but it sounds like I should do a patch for the mis-alignment issue before that. I know what the problem is and don't think it would involve too much time. Mike Paul Spencer wrote: > I think some of the new changes in Fusion recently are destined for a > 1.1 release rather than a 1.0.5 release because they are new features > rather than bug fixes. I will talk to Mike early next week about the > state of the 1.0 branch vs trunk and try to bring over any important > bug fixes. As Zac mentioned, the misalignment of the tiles seems like > an important fix to get in, I'm not sure of the status of that. > > For a potential 1.1, I think we have a few more things to go in > including some Jx work to factor out Prototype/Scriptaculous in favour > of mootools. > > Cheers > > Paul > > On 1-May-08, at 11:01 PM, Jason Birch wrote: > >> To follow up to myself.... >> >> As long as we take the Fusion that is in trunk, I think we're good >> for all the fixes up to 1.0.4, which is the most current release. >> There were some revisions between the revision used for MapGuide >> trunk and the 1.0.4 release, but I think that was all SVN migration >> stuff. >> >> There are certainly some other outstanding bugs in Fusion, but 1.0.5 >> appears to be a ways out. Fortunately, fusion is relatively easy to >> upgrade (at least between point releases). >> >> Jason >> >> ________________________________ >> >> From: mapguide-internals-bounces@... on behalf of Jason >> Birch >> Sent: Thu 2008-05-01 4:25 PM >> To: MapGuide Internals Mail List >> Subject: RE: [mapguide-internals] MGOS 2.0.1 status >> >> >> >> That sounds great. >> >> Is there an updated Fusion for this build compared to 2.0? I believe >> that some significant bugs have been fixed since the 2.0 release, in >> selection and maybe in some of the canvas tools (select radius, distance >> measure, etc). >> >> Will we have an internal-only RC for this release, or are the changes >> small enough that you're comfortable with an untested point release? >> >> Jason >> >> -----Original Message----- >> From: Tom Fukushima >> Subject: [mapguide-internals] MGOS 2.0.1 status >> >> Here's a status update on MGOS 2.0.1. I was waiting to get merge >> modules for the missing providers, but it doesn't look like that is >> going to happen for the already released FDO binaries (we will have them >> in future builds though). So now we're trying to figure out which >> version of FDO to install and once we have that I should be able to post >> a MGOS 2.0.1. This should all be resolved within a few days I hope. >> _______________________________________________ >> mapguide-internals mailing list >> mapguide-internals@... >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals >> >> >> _______________________________________________ >> mapguide-internals mailing list >> mapguide-internals@... >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals > > > __________________________________________ > > Paul Spencer > Chief Technology Officer > DM Solutions Group Inc > http://www.dmsolutions.ca/ > > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals > mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusLooks like a fix for this just got submitted to the Fusion trunk. Are
we going to wait for a new Fusion release, or can we pull the current revision of trunk? (can you tell I'd really like a 2.0.1?) :) Jason -----Original Message----- From: Tom Fukushima Subject: RE: [mapguide-internals] MGOS 2.0.1 status OK, it sounds like there are some Fusion fixes that we would like to get into 2.0.1. Do you have an ETA on when they will be in? As for the other 2.0.1 changes, unless someone sees otherwise, I don't see anything that will require an RC. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusNote that the latest addition to MapGuide trunk (r3154) about slow
deselection and maptips is something that I'd really like to see in 2.0.1 also. This is something that came up for the PostGIS provider as well, but I can't find the ticket. Jason -----Original Message----- From: Tom Fukushima Subject: RE: [mapguide-internals] MGOS 2.0.1 status OK, it sounds like there are some Fusion fixes that we would like to get into 2.0.1. Do you have an ETA on when they will be in? As for the other 2.0.1 changes, unless someone sees otherwise, I don't see anything that will require an RC. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusHi Jason,
It has been submitted to 2.0.x as well. Thanks, Trevor -----Original Message----- From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@...] On Behalf Of Jason Birch Sent: Tuesday, May 06, 2008 10:22 AM To: MapGuide Internals Mail List Subject: RE: [mapguide-internals] MGOS 2.0.1 status Note that the latest addition to MapGuide trunk (r3154) about slow deselection and maptips is something that I'd really like to see in 2.0.1 also. This is something that came up for the PostGIS provider as well, but I can't find the ticket. Jason -----Original Message----- From: Tom Fukushima Subject: RE: [mapguide-internals] MGOS 2.0.1 status OK, it sounds like there are some Fusion fixes that we would like to get into 2.0.1. Do you have an ETA on when they will be in? As for the other 2.0.1 changes, unless someone sees otherwise, I don't see anything that will require an RC. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
Re: MGOS 2.0.1 statusJason,
Mike is working to get Fusion bug fixes into the 1.0 branch to be rolled into the MGOS 2.0.1 update. This should be done by end of day Wednesday and then MGOS can be cut with a new Fusion that includes the bug fixes. Cheers Paul On 6-May-08, at 12:19 PM, Jason Birch wrote: > Looks like a fix for this just got submitted to the Fusion trunk. Are > we going to wait for a new Fusion release, or can we pull the current > revision of trunk? (can you tell I'd really like a 2.0.1?) :) > > Jason > > -----Original Message----- > From: Tom Fukushima > Subject: RE: [mapguide-internals] MGOS 2.0.1 status > > OK, it sounds like there are some Fusion fixes that we would like to > get > into 2.0.1. Do you have an ETA on when they will be in? > > As for the other 2.0.1 changes, unless someone sees otherwise, I don't > see anything that will require an RC. > > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals __________________________________________ Paul Spencer Chief Technology Officer DM Solutions Group Inc http://www.dmsolutions.ca/ _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusNever mind; Paul posted on the Fusion list that 1.0.5 should be released
within the next couple days, so we should obviously wait for that. Jason -----Original Message----- From: Jason Birch Subject: RE: [mapguide-internals] MGOS 2.0.1 status Looks like a fix for this just got submitted to the Fusion trunk. Are we going to wait for a new Fusion release, or can we pull the current revision of trunk? (can you tell I'd really like a 2.0.1?) :) _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusThanks Trevor...
Understood; I was just worried that Tom might be sitting with a specific revision pre-built and waiting for a Fusion update :) Jason -----Original Message----- From: Trevor Wekel Subject: RE: [mapguide-internals] MGOS 2.0.1 status It has been submitted to 2.0.x as well. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusHi,
We tried to integrate Fusion 1.0.5 but ran into some problems. Instead of waiting for those remaining Fusion fixes, which we won't be able to start integrating until next week at the earliest, I would like to put out 2.0.1. For those who really want to use Fusion 1.0.5 and 1.0.6, I believe these can be overlaid on top of the existing files (well, that or something like that is what Chris does when he tests it). If someone could smoke test the posting at http://download.osgeo.org/mapguide/releases/2.0.1/ before I announce, that would be good. I plan to announce tomorrow or Wednesday. Also, I decided on not doing an RC because there have only been bug fixes put into this version. Thanks Tom -----Original Message----- From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@...] On Behalf Of Jason Birch Sent: Tuesday, May 06, 2008 10:56 AM To: MapGuide Internals Mail List Subject: RE: [mapguide-internals] MGOS 2.0.1 status Thanks Trevor... Understood; I was just worried that Tom might be sitting with a specific revision pre-built and waiting for a Fusion update :) Jason -----Original Message----- From: Trevor Wekel Subject: RE: [mapguide-internals] MGOS 2.0.1 status It has been submitted to 2.0.x as well. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 statusTom, does 2.0.1 include the current MapGuide trunk version of Fusion
(analogous to 1.0.4)? Jason -----Original Message----- From: Tom Fukushima Subject: RE: [mapguide-internals] MGOS 2.0.1 status If someone could smoke test the posting at http://download.osgeo.org/mapguide/releases/2.0.1/ before I announce, that would be good. I plan to announce tomorrow or Wednesday. Also, I decided on not doing an RC because there have only been bug fixes put into this version. _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: MGOS 2.0.1 status |