Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-dev] Eclipse4 testing

Hi,

I've create a google hangout for Monday 13th of October at 19:00 CEST is
this Ok for you?

Others are naturally free to join
https://plus.google.com/u/0/events/c8vdan4315df4q5mppacvj4rfng

Tom

On 06.10.14 19:43, Jody Garnett wrote:
> Morning Tom,
> 
> Would you like to invite me (and any other interested parties) to a
> google hangout (using world clock meeting planner
> <http://www.timeanddate.com/worldclock/meetingtime.html?month=10&day=7&year=2014&p1=87&p2=1091&iv=0>
> is a good way to establish a time).
> 
> The issues (and test plan) are the same as reported earlier - going
> through walkthrough 1 and walkthrough 2 resulted in two primary issues:
> 
> 1) map editor navigational controls (zoom to extent and similar) were
> not displayed in the toolbar. They show up in the menubar, so we are
> probably looking a straightforward migration issues?
> 
> 2) user interface getting out of sync with EMF model used for projects /
> maps / layers.
> 
> If we can arrange a hangout I would be happy to share a screen and step
> through walkthrough 1 and walkthrough 2 showing where the above two
> issues occur.
> 
> Notes:
> - I am using uDig 1.4.0 as a baseline to ensure any regressions are a
> result of migration to Eclipse 4.
> - uDig master has migrated to GeoTools 11.2 - this is an orthogonal
> change with surprisingly few lines of code changed (so chances are
> rebasing your branch against master will be seamless).
> 
> --
> Jody
> 
> Jody Garnett
> 
> On Mon, Oct 6, 2014 at 3:04 AM, Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx
> <mailto:tom.schindl@xxxxxxxxxxxxxxx>> wrote:
> 
>     Hi,
> 
>     Having returned from JavaOne I'm now available for a testing session
>     with Jody so that he can show me areas not yet working and I can finally
>     fix them.
> 
>     Tom
> 
>     On 06.10.14 10:44, Moser-Spitzenstaetter Ludwig wrote:
>     > Hello,
>     >
>     >
>     >
>     > I’m waiting for a result to get uDig started up within our product, but
>     > for this i wait for a confimration that it is working correctly (o rat
>     > least most of it)
>     >
>     >
>     >
>     > So whats the current status?
>     >
>     >
>     >
>     > Thanks in advance
>     >
>     >
>     >
>     > *Bakk. Techn. Ludwig M. Spitzenstätter*
>     >
>     > Naturwissenschaftliche Sammlungen
>     >
>     >
>     >
>     > *Tiroler Landesmuseen-Betriebsgesellschaft m.b.H.
>     > *Feldstrasse 11a, 6020 Innsbruck
>     > Tel +43 512 594 89-425 <tel:%2B43%20512%20594%2089-425>   Fax DW
>     -440__
>     >
>     > _l.spitzenstaetter@tiroler-landesmuseen.at_
>     >
>     > www.tiroler-landesmuseen.at <http://www.tiroler-landesmuseen.at>
>     <http://www.tiroler-landesmuseen.at> |
>     > www.biooffice.at <http://www.biooffice.at> <http://www.biooffice.at/>
>     >
>     >
>     >
>     > *Von:*udig-dev-bounces@xxxxxxxxxxxxxxxx
>     <mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx>
>     > [mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx
>     <mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx>] *Im Auftrag von *Jody
>     Garnett
>     > *Gesendet:* Donnerstag, 28. August 2014 21:13
>     > *An:* Tom Schindl
>     > *Cc:* uDig project developer discussion
>     > *Betreff:* Re: [udig-dev] Eclipse4 testing
>     >
>     >
>     >
>     > Note I want to ensure you (like any developer) gets paid - so we can use
>     > this test plan against 1.4.0 to ensure we have not misidentified any
>     > bugs as regressions brought on by Luna.
>     >
>     > --
>     >
>     > Jody
>     >
>     >
>     > Jody Garnett
>     >
>     >
>     >
>     > On Thu, Aug 28, 2014 at 12:11 PM, Jody Garnett <jody.garnett@xxxxxxxxx <mailto:jody.garnett@xxxxxxxxx>
>     > <mailto:jody.garnett@xxxxxxxxx <mailto:jody.garnett@xxxxxxxxx>>> wrote:
>     >
>     > Given that we are working across different weeks / availability /
>     > timezones we should make a test plan that both you and your customer can
>     > sign off on.
>     >
>     >
>     >
>     > Normally we use the getting started tutorials as our test plan for each
>     > release (these tutorials are specific about what button to push when).
>     > It is aimed as an intro but I understand if it requires background
>     > knowledge on mapping that makes it difficult to follow.
>     >
>     >
>     >
>     > I will find a wiki page and write up my previous email/results in the
>     > form of a test plan so we can refer to specific problem steps (sigh).
>     >
>     >
>     >
>     > Is there any wiki that you have access to for this purpose? Or should we
>     > set up a shared google doc?
>     >
>     >
>     >
>     >
>     > Jody Garnett
>     >
>     >
>     >
>     > On Thu, Aug 28, 2014 at 11:56 AM, Tom Schindl
>     > <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>     <mailto:tom.schindl@xxxxxxxxxxxxxxx
>     <mailto:tom.schindl@xxxxxxxxxxxxxxx>>> wrote:
>     >
>     > Fine with me! If you have steps for reproduction just sent them over and
>     > I'll try to reproduce myself ;-)
>     >
>     > Tom
>     >
>     >
>     > On 28.08.14 19:33, Jody Garnett wrote:
>     >> That is the week of foss4g so it will need to be after that.
>     >>
>     >>
>     >>
>     >>> On Aug 28, 2014, at 4:00 AM, Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>     > <mailto:tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>>>
>     wrote:
>     >>>
>     >>> Hi,
>     >>>
>     >>> I'm going to be on holiday next week and have to finish of some other
>     >>> work items so I guess we need to postpone this to after the my holiday.
>     >>> Would Thursday 11th Sep work for you?
>     >>>
>     >>> Tom
>     >>>
>     >>>> On 26.08.14 08:37, Jody Garnett wrote:
>     >>>> Hello Tom:
>     >>>>
>     >>>> I would be happy to screen share (Skype or google hangout) and
>     >>>> demonstrate the issues I encountered. Please let me know when you are
>     >>>> available.
>     >>>>
>     >>>> I did try and take notes with my initial reports on the data sets and
>     >>>> steps used, hopefuly we can retrace these steps together.
>     >>>>
>     >>>> Jody
>     >>>>
>     >>>> Jody Garnett
>     >>>>
>     >>>>
>     >>>> On Wed, Aug 20, 2014 at 3:56 AM, Tom Schindl
>     >>>> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>     <mailto:tom.schindl@xxxxxxxxxxxxxxx
>     <mailto:tom.schindl@xxxxxxxxxxxxxxx>>
>     > <mailto:tom.schindl@xxxxxxxxxxxxxxx
>     <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>     > <mailto:tom.schindl@xxxxxxxxxxxxxxx
>     <mailto:tom.schindl@xxxxxxxxxxxxxxx>>>> wrote:
>     >>>>
>     >>>>    Hi,
>     >>>>
>     >>>>    I think I'll have time this Friday afternoon to look at some
>     of the
>     >>>>    problems but for that I need a description how I can
>     reproduce the
>     >>>>    problem.
>     >>>>
>     >>>>    It's naturally also possible that we setup a screensharing
>     session so
>     >>>>    that you can demostrate me the problem.
>     >>>>
>     >>>>    Tom
>     >>>>
>     >>>>>    On 16.08.14 01:24, Jody Garnett wrote:
>     >>>>> Just double checking we are sorting out E4 issues with Tom before
>     >>>>> upgrading GeoTools. This allows us to be assured the issues are
>     >>>>    entirely
>     >>>>> due to change RCP, EMF, etc... and not due to change of underlying
>     >>>>> geotools library.
>     >>>>>
>     >>>>>    Now we are in position to test udig on E4 platform and
>     collaborate
>     >>>>>    on branch
>     >>>>>    https://github.com/uDig/udig-platform/tree/luna-support to
>     upgrade
>     >>>>>    geotools.
>     >>>>>
>     >>>>>
>     >>>>> Tom are you able to track that branch? (and possibly issue pull
>     >>>>    requests
>     >>>>> against it?)
>     >>>>>
>     >>>>> I tried to report several issues with the branch that did not make
>     >>>>    your
>     >>>>> list Frank, adding them below with a (+)
>     >>>>>
>     >>>>> Next steps (for luna-support):
>     >>>>> * testing phase with the current alpha2
>     >>>>> (+) ensure "action tools" show up in toolbar
>     >>>>> (+) restart issues around map save/load
>     >>>>> * fix #E4 upgrade bugs together with Tom
>     >>>>> * merge this branch back to master
>     >>>>>
>     >>>>> Upgrade GeoTools:
>     >>>>> (+) Table View fix
>     >>>>> * afterwards we can
>     >>>>> merge
>     >>>>   
>     https://github.com/uDig/udig-platform/tree/udig-gt-11-snapshot into
>     >>>>    master
>     >>>>> as well
>     >>>>> * creating an other Alpha release to test with
>     >>>>> * finalize uDig 2.0.0 (with installer that contain JRE and so
>     on) -
>     >>>>> which will not really be a LocationTech release because of
>     IP/CQ stuff
>     >>>>>
>     >>>>> LocationTech Release:
>     >>>>> (+) Change to GeoTools 11.2 (this is the one I am getting
>     reviewed for
>     >>>>> geogig)
>     >>>>>
>     >>>>>    * next goal to make a LocationTech Release
>     >>>>>       * bundles and features hosted at LoactionTech (maven/p2
>     update
>     >>>>>    sites)
>     >>>>>       * installers builds we can still provide from
>     Refractions based
>     >>>>>    on Release from LocationTech (sources at github, hosting of
>     final
>     >>>>>    package installers and JRE's at Refractions research)
>     >>>>>
>     >>>>>    Does this makes sense to you? If so, I would like to create
>     >>>>    tasks -
>     >>>>>    bugzilla or still in JIRA? What would yoe prefer
>     >>>>>
>     >>>>>
>     >>>>> Bugzilla, GitHub or Jira.  I am personally terrible at using
>     Bugzilla
>     >>>>> but perhaps that is just me? I do not mind much either way.
>     >>>>>
>     >>>>> Jody
>     >>>
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > udig-dev mailing list
>     > udig-dev@xxxxxxxxxxxxxxxx <mailto:udig-dev@xxxxxxxxxxxxxxxx>
>     > To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     > https://locationtech.org/mailman/listinfo/udig-dev
>     >
> 
>     _______________________________________________
>     udig-dev mailing list
>     udig-dev@xxxxxxxxxxxxxxxx <mailto:udig-dev@xxxxxxxxxxxxxxxx>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://locationtech.org/mailman/listinfo/udig-dev
> 
> 
> 
> 
> _______________________________________________
> udig-dev mailing list
> udig-dev@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://locationtech.org/mailman/listinfo/udig-dev
> 



Back to the top