Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] WTP Development Status - please read

Nick,

I am not sure what you mean by "biweekly smoketest calls". We will have a WTP Development Status call, as well as request smoketest for both WTP 3.9.3 and WTP 3.10, on January 25. (The smoketest schedules are already listed in the agenda.) When we have the WTP Development Status call, we discuss the smoketest request that was issued (if one was issued).
Also, I have seen you mention the time wrong a couple of times, so to be clear, the WTP Development Status call is at 2 pm Eastern time (EDT when daylight savings is on, and EST when daylight savings is off).

FWIW,

- Carl Anderson
WTP PMC lead

Inactive hide details for Nick Boldt ---01/18/2018 01:31:40 PM---Won't those conflict with the biweekly smoketest calls? Or wilNick Boldt ---01/18/2018 01:31:40 PM---Won't those conflict with the biweekly smoketest calls? Or will you move them a week later too, to c

From: Nick Boldt <nboldt@xxxxxxxxxx>
To: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Date: 01/18/2018 01:31 PM
Subject: Re: [wtp-dev] WTP Development Status - please read
Sent by: wtp-dev-bounces@xxxxxxxxxxx




Won't those conflict with the biweekly smoketest calls? Or will you move them a week later too, to continue the every-other-week flow?

Also, will the PMC calls be resuming soon? Just curious!

Nick

On Thu, Jan 18, 2018 at 10:40 AM, Carl Anderson <ccc@xxxxxxxxxx> wrote:
    Folks,

    My apologies for not doing this earlier- I worked out the calendar for the year, and it would work best if we had WTP Development Status meetings every other week starting with Jan. 25. That aligns us with both the Oxygen.3 and Photon M5 smoke test dates. So, there will not be a meeting today, but there will be a meeting (and both a WTP 3.9.3 and WTP 3.10 smoke test) next Thursday. I have already posted an agenda at     https://wiki.eclipse.org/WTP_2018-01-25 - feel free to update it.

    Sincerely,

    - Carl Anderson
    WTP PMC lead

    Inactive hide details for Carl Anderson---01/04/2018 11:05:30 AM---Folks, There should be a WTP Development Status meeting todCarl Anderson---01/04/2018 11:05:30 AM---Folks, There should be a WTP Development Status meeting today, but due to circumstances that arose

    From:     Carl Anderson/Raleigh/IBM
    To:     "Web Tools Platform Development" <wtp-dev@xxxxxxxxxxx>
    Date:     01/04/2018 11:05 AM
    Subject:     WTP Development Status - please read


    Folks,

    There should be a WTP Development Status meeting today, but due to circumstances that arose this morning, I will not be able to attend or run it. I have not found anyone to run it in my absence, so... unless someone steps up, there will not be a meeting today. To add to the fun, the WTP 3.10 build is broken today, so there is not yet a smoke test request.
    So, unless things change, I plan to hold a WTP Development Status meeting on Jan. 18. If the WTP 3.10 build gets fixed soon, we should have a smoke test, otherwise we will hold off until Jan. 18 for that as well.

    Happy New Year!

    - Carl Anderson
    WTP PMC lead


    _______________________________________________
    wtp-dev mailing list
    wtp-dev@xxxxxxxxxxx
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/wtp-dev



--
Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED.
@ @redhatnews      Red Hat_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_wtp-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=6JCYBixIS0G6Rj43h5xZSA&m=TGLugYSWgeyOJA4inNNk2srGNmbcqT0e9f-6NUYUIHw&s=NrnXcA_hEKtHSfoYOfOWI_-7aGLwE6iz06VlMS-XfBo&e=

Back to the top