[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-dev] initial code check-in
|
Am 14.10.2014 22:16 schrieb "Jody Garnett" <jody.garnett@xxxxxxxxx>:
>
> On Tue, Oct 14, 2014 at 12:54 PM, Frank Gasdorf <
fgdrf@xxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> Jody, I'm not sure whether I got your point. Althought we can work in
github you like to move to LocationTech hosted git repository (and mirror
this back to LocationTech group repository at github)?
>
> I am in the process of asking for https://github.com/locationtech/udig to
be created.
I guess it exists already
>
> When it is available I would like to move from
https://github.com/uDig/udig-platform to
https://github.com/locationtech/udig
>>
>> Is this neccessary to be in Position to use build and hosting
infrastructure and relang functionality from eclipse common build
infrastructure as well?
>
> This is not my initial goal, however when we have moved to
https://github.com/locationtech/udig we can use eclipse build
infrastructure, you will have to explain build/hosting/relang to me.
Hudson build infrastructure, p2 hostingand release engineering and
depolyment and so on
>>
>> Or is it about adding eclipse git as remote repository to our working
copy and push master to upstream master, rebase luna branch and push it to
upstream as well?
>>>>> not displayed in the toolbar. They show up in the menubar, so we are
>>>>> probably looking a straightforward migration issues?
>>>>>=20
>>>>> 2) user interface getting out of sync with EMF model used for
>>>> projects /
>>>>> maps / layers.
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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).
>>>>>=20
>>>>> --
>>>>> Jody
>>>>>=20
>>>>> Jody Garnett
>>>>>=20
>>>>> On Mon, Oct 6, 2014 at 3:04 AM, Tom Schindl
>>>> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>> wrote:
>>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> Tom
>>>>>=20
>>>>>> On 06.10.14 10:44, Moser-Spitzenstaetter Ludwig wrote:
>>>>>> Hello,
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> I=E2=80=99m 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)
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> So whats the current status?
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Thanks in advance
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> *Bakk. Techn. Ludwig M. Spitzenst=C3=A4tter*
>>>>>>=20
>>>>>> Naturwissenschaftliche Sammlungen
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> *Tiroler Landesmuseen-Betriebsgesellschaft m.b.H.
>>>>>> *Feldstrasse 11a, 6020 Innsbruck
>>>>>> Tel +43 512 594 89-425 <tel:%2B43%20512%20594%2089-425>
>>>> <tel:%2B43%20512%20594%2089-425> Fax DW
>>>>> -440__
>>>>>>=20
>>>>>> _l.spitzenstaetter@xxxxxxxxxxxxxxxxxxxxxxx
>>>> <mailto:l.spitzenstaetter@xxxxxxxxxxxxxxxxxxxxxxx>_
>>>>>>=20
>>>>>> www.tiroler-landesmuseen.at
>>>> <http://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> <http://www.biooffice.at/>
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> *Von:*udig-dev-bounces@xxxxxxxxxxxxxxxx
>>>> <mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx>
>>>>> <mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx
>>>> <mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx>>
>>>>>> [mailto: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
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>> --
>>>>>>=20
>>>>>> Jody
>>>>>>=20
>>>>>>=20
>>>>>> Jody Garnett
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 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>>
>>>>>> <mailto:jody.garnett@xxxxxxxxx
>>>> <mailto:jody.garnett@xxxxxxxxx> <mailto:jody.garnett@xxxxxxxxx
>>>> <mailto:jody.garnett@xxxxxxxxx>>>> wrote:
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 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).
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Is there any wiki that you have access to for this purpose?
>>>> Or should we
>>>>>> set up a shared google doc?
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Jody Garnett
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 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>>
>>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>>> wrote:
>>>>>>=20
>>>>>> Fine with me! If you have steps for reproduction just sent
>>>> them over and
>>>>>> I'll try to reproduce myself ;-)
>>>>>>=20
>>>>>> Tom
>>>>>>=20
>>>>>>=20
>>>>>>> On 28.08.14 19:33, Jody Garnett wrote:
>>>>>>> That is the week of foss4g so it will need to be after that.
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>> 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>>
>>>>=20
>>>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>>>
>>>>> wrote:
>>>>>>>>=20
>>>>>>>> Hi,
>>>>>>>>=20
>>>>>>>> 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?
>>>>>>>>=20
>>>>>>>> Tom
>>>>>>>>=20
>>>>>>>>> On 26.08.14 08:37, Jody Garnett wrote:
>>>>>>>>> Hello Tom:
>>>>>>>>>=20
>>>>>>>>> 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.
>>>>>>>>>=20
>>>>>>>>> I did try and take notes with my initial reports on the
>>>> data sets and
>>>>>>>>> steps used, hopefuly we can retrace these steps together.
>>>>>>>>>=20
>>>>>>>>> Jody
>>>>>>>>>=20
>>>>>>>>> Jody Garnett
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> 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>>>
>>>>>> <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
>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>>>> wrote:
>>>>>>>>>=20
>>>>>>>>> Hi,
>>>>>>>>>=20
>>>>>>>>> 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.
>>>>>>>>>=20
>>>>>>>>> It's naturally also possible that we setup a screensharing
>>>>> session so
>>>>>>>>> that you can demostrate me the problem.
>>>>>>>>>=20
>>>>>>>>> Tom
>>>>>>>>>=20
>>>>>>>>>> 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.
>>>>>>>>>>=20
>>>>>>>>>> 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.
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> Tom are you able to track that branch? (and possibly
>>>> issue pull
>>>>>>>>> requests
>>>>>>>>>> against it?)
>>>>>>>>>>=20
>>>>>>>>>> I tried to report several issues with the branch that
>>>> did not make
>>>>>>>>> your
>>>>>>>>>> list Frank, adding them below with a (+)
>>>>>>>>>>=20
>>>>>>>>>> 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
>>>>>>>>>>=20
>>>>>>>>>> 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
>>>>>>>>>>=20
>>>>>>>>>> LocationTech Release:
>>>>>>>>>> (+) Change to GeoTools 11.2 (this is the one I am getting
>>>>> reviewed for
>>>>>>>>>> geogig)
>>>>>>>>>>=20
>>>>>>>>>> * 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)
>>>>>>>>>>=20
>>>>>>>>>> Does this makes sense to you? If so, I would like to
>>>> create
>>>>>>>>> tasks -
>>>>>>>>>> bugzilla or still in JIRA? What would yoe prefer
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> Bugzilla, GitHub or Jira. I am personally terrible at using
>>>>> Bugzilla
>>>>>>>>>> but perhaps that is just me? I do not mind much either way.
>>>>>>>>>>=20
>>>>>>>>>> Jody
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> udig-dev mailing list
>>>>=20
>>>>>> udig-dev@xxxxxxxxxxxxxxxx <mailto:udig-dev@xxxxxxxxxxxxxxxx>
>>>> <mailto: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
>>>>>=20
>>>>> _______________________________________________
>>>>> udig-dev mailing list
>>>>> udig-dev@xxxxxxxxxxxxxxxx <mailto:udig-dev@xxxxxxxxxxxxxxxx>
>>>> <mailto:udig-dev@xxxxxxxxxxxxxxxx <mailto:udig-dev@xxxxxxxxxxxxxxxx>=
>
>>>>=20
>>>>> To change your delivery options, retrieve your password, or
>>>>> unsubscribe from this list, visit
>>>>> https://locationtech.org/mailman/listinfo/udig-dev
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> 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
>>>>=20
>>>> _______________________________________________
>>>> 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
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> 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
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> 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
>>>=20
>>> _______________________________________________
>>> udig-dev mailing list
>>> udig-dev@xxxxxxxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe f=
rom this list, visit
>>> https://locationtech.org/mailman/listinfo/udig-dev
>>=20
>> _______________________________________________
>> udig-dev mailing list
>> udig-dev@xxxxxxxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe f=
rom this list, visit
>> https://locationtech.org/mailman/listinfo/udig-dev
>=20
> _______________________________________________
> udig-dev mailing list
> udig-dev@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe fr=
om this list, visit
> https://locationtech.org/mailman/listinfo/udig-dev
