Release 1.1

Jan 6, 2009 at 9:31 AM
I am currently working a couple fixes to the core.   So it occurs to me that we should probably push out a release prior to jumping into new functionality.  Also, this would give us a clean start for incorporating the new geometry stuff.   So if you all agree, let's pick a date, roll up our sleeves, and get to work fixing all the remaining bugs / issues.
Jan 6, 2009 at 11:52 AM
I agree!
Jan 6, 2009 at 1:00 PM
Sounds good to me, we should do our usual assigning of tasks to the version, set a date based on that and see how we go. I think the release we put out before Christmas was well timed but clearly there are things to clean up.
Jan 10, 2009 at 11:38 PM
Edited Jan 25, 2009 at 3:08 PM
So to get us started thinking about what needs to be done, here is a few ideas and suggestions I have for the release:

Timeframe:  Given the items listed below, I think we should target an end of month release.  This should give us time to complete, test, and package together a solid release.  Here are my suggested dates:

    * 23 Jan 09: Code Complete
    * 30 Jan 09: Release V1.1

Suggested Task Assignments:

RoadWarrior:  Layer Cleanup:

   1. Refactor BaseLayer class.
   2. Test ability to layer multiple MSI’s.
   3. Reconsider Map Boundary Implementation

        * Horizontal Continuous Panning (GM Approach)
        * Confine Earth to Screen (VE Approach)
        * Both with the ability to configure mode.

SoulSolutions:  VE Services Stability

   1. Anything that can be done to simplify or increase developers understanding would be great.
   2. Research issue of browser not being able to caching VE tile images.
   3. Research ability to detect "No Image Found".
   4. Map Rotation:  Oversize map canvas on rotation.

DotNetNoobie:  Prototype Enhancements:

   1. Consider what can be done to refactor SideBar for more vertical space.
   2. Implement a Vertical Scale ZoomBar.
   3. Routing Improvements

        * Update Routing Panel Layout to be able to view all commands
        * Add different colored pushpins to note route start and end (e.g. Green, Red)
        * Zoom-in on route extent when route is complete

AquaSeal:  Documentation.

   1. Review and identify specific areas which need better documentation
   2. Create a generated .CHM file from the DeepEarth core project.
   3. Review and update “How To” type documentation.

Skulavik:  Review and Update Projections.

   1. Do a performance review of CoordTransform & Projections.
   2. Add missing Projections that are needed for WMS.

Repasted from Notepad: as IE Users were gettng unreadable characters.
Jan 11, 2009 at 7:13 AM
Sounds fair to me - we will have to branch on the 23 Jan as we will be doing a bunch of work for Geometry that week.
Lets call this version 1.1 however to be more conventional (hate for people to be asking waht happened to 1.1,1.2,1.3 and 1.4)
Release is here:
We can start creating / assigning tasks straight away.
Jan 11, 2009 at 2:54 PM
DeepEarth 1.1 it is.  I'll change this topic header to eliminate further confusion.

Regarding branching.  I'd rather wait one week and avoid the headache of branching an dual maintenance. 
Jan 11, 2009 at 9:02 PM
Edited Jan 11, 2009 at 9:03 PM
Just updated the suggested task list after reviewing the "Issue Tracker".
Jan 12, 2009 at 4:41 AM
I love the assignments.  I'll be on it!  Thanks.