[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Time to cut a new 2.7?

On 9/27/19 5:14 PM, Jody Grassel wrote:
Well, okay. I guess what I'm trying to ask is: Can we cut a new 2.7 release with what is present in 2.7 right now?

I don't want to do any decisions while being on vacation.

Anyway https://www.eclipse.org/eclipselink/downloads/nightly.php shows test failures for the last nightly. We can't release what we have if there are test failures.

thanks,
--lukas


On Fri, Sep 27, 2019 at 8:56 AM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx <mailto:lukas.jungmann@xxxxxxxxxx>> wrote:


    On 9/26/19 4:21 PM, Jody Grassel wrote:
     > It's been since January since the last 2.7 version cut, if our
    goal was
     > one release per quarter, then we've already missed 2 point
    releases in
     > the time since then.  Of the list you've cited, how many are
     > considered stop-ship, and how many could be deferred to the next
    point
     > release of 2.7?


Â>Â Â Â- go through open PRs and close (either merge or reject) ~50% of them Â>Â Â Â- evaluate open issues - I can see some of them can be closed as Â>Â Â Âalready Â>Â Â Âfixed

    where when first part of both sentences ("go through open PRs" and
    "evaluate open issues") is done, answer to your question can be given.
    Second part of both sentences goes a step beyond what is required right
    now but maybe there is some low hanging fruit we could add to the
    release. I don't have all existing issues and PRs in my head, sorry.

    thanks,
    --lukas

     ÂÂ If there are blockers, which exact bugtracker #s/Github
     > PRs are needed?
     >
     > On Tue, Sep 24, 2019 at 11:08 AM Lukas Jungmann
     > <lukas.jungmann@xxxxxxxxxx <mailto:lukas.jungmann@xxxxxxxxxx>
    <mailto:lukas.jungmann@xxxxxxxxxx
    <mailto:lukas.jungmann@xxxxxxxxxx>>> wrote:
     >
     >Â Â ÂOn 9/24/19 5:27 PM, Jody Grassel wrote:
     >Â Â Â > It's been a very long time since a version of Eclipselink
    2.7 was
     >Â Â Âcut
     >Â Â Â > (thought this was supposed to be done quarterly?)Â With the
     >Â Â Âupdate to
     >Â Â Â > ASM 7.1, perhaps now is a good time to cut a new one?
     >
     >Â Â Âthat is on the table. We should see if we managed to fix an
    issue we
     >Â Â Âhad
     >Â Â Âtomorrow, so far it seems to be on the good way but keep fingers
     >Â Â Âcrossed.
     >
     >Â Â ÂFew remaining TODOs, if you/anyone want(s) to help with them:
     >Â Â Â- compare PRs merged to master with those in 2.7 to see if
    something
     >Â Â Âworth to be in 2.7 is there, eventually prepare PR
    backporting what is
     >Â Â Âmissing (or what is in 2.7 and not in master)
     >Â Â Â- fix for bug 550542 (PR #530) is something we really want to
    have
     >Â Â Âin 2.7
     >Â Â Â- go through open PRs and close (either merge or reject) ~50%
    of them
     >Â Â Â- evaluate open issues - I can see some of them can be closed as
     >Â Â Âalready
     >Â Â Âfixed
     >Â Â Â- Radek is currently investigating some Oracle DB related
    failures he
     >Â Â Ânoticed (..and Will apparently as well)
     >
     >Â Â ÂI believe that with some help, all this can be done by
    Monday. If it
     >Â Â Âwill be, and I believe it will, we'll work towards releasing
    2.7.5
     >Â Â Âusing
     >Â Â Ânew build infrastructure, so the old one can be retired
    (actually old
     >Â Â Âone needs to be retired before new one can be enabled[1], so
    there will
     >Â Â Âbe some time during which travis will be the only thing
    running some
     >Â Â Âbuilds/tests)
     >
     >Â Â Âthanks,
     >Â Â Â--lukas
     >
     >Â Â Â[1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=546431
     >
     >Â Â Â >
     >Â Â Â > _______________________________________________
     >Â Â Â > eclipselink-dev mailing list
     >Â Â Â > eclipselink-dev@xxxxxxxxxxx
    <mailto:eclipselink-dev@xxxxxxxxxxx>
    <mailto:eclipselink-dev@xxxxxxxxxxx
    <mailto:eclipselink-dev@xxxxxxxxxxx>>
     >Â Â Â > To change your delivery options, retrieve your password, or
     >Â Â Âunsubscribe from this list, visit
     >Â Â Â > https://www.eclipse.org/mailman/listinfo/eclipselink-dev
     >Â Â Â >
     >Â Â Â_______________________________________________
     >Â Â Âeclipselink-dev mailing list
     > eclipselink-dev@xxxxxxxxxxx <mailto:eclipselink-dev@xxxxxxxxxxx>
    <mailto:eclipselink-dev@xxxxxxxxxxx
    <mailto:eclipselink-dev@xxxxxxxxxxx>>
     >Â Â ÂTo change your delivery options, retrieve your password, or
     >Â Â Âunsubscribe from this list, visit
     > https://www.eclipse.org/mailman/listinfo/eclipselink-dev
     >
     >
     > _______________________________________________
     > eclipselink-dev mailing list
     > eclipselink-dev@xxxxxxxxxxx <mailto:eclipselink-dev@xxxxxxxxxxx>
     > To change your delivery options, retrieve your password, or
    unsubscribe from this list, visit
     > https://www.eclipse.org/mailman/listinfo/eclipselink-dev
     >
    _______________________________________________
    eclipselink-dev mailing list
    eclipselink-dev@xxxxxxxxxxx <mailto:eclipselink-dev@xxxxxxxxxxx>
    To change your delivery options, retrieve your password, or
    unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/eclipselink-dev


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