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

I kicked off new build on Saturday for which the nightly passed; so 2.7.5-RC1 is in the queue.

Anyway it does not contain fix for bug 550542 yet. Once that fix is ready, RC2 will be produced.

thanks,
--lukas

On 9/27/19 5:23 PM, Lukas Jungmann wrote:
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


_______________________________________________
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