Time to cut a new 2.7?

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Time to cut a new 2.7?

Jody Grassel
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?

_______________________________________________
eclipselink-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Haller, Patrick

I’d be more than happy if the provided fixes for https://bugs.eclipse.org/bugs/show_bug.cgi?id=463042 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=382308 could get into an official release! Would that still be possible to go into a 2.7.x?

 

Thanks,

Patrick

 

 

From: [hidden email] <[hidden email]> On Behalf Of Jody Grassel
Sent: Dienstag, 24. September 2019 17:27
To: Dev mailing list for Eclipse Persistence Services <[hidden email]>
Subject: [eclipselink-dev] Time to cut a new 2.7?

 

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?


_______________________________________________
eclipselink-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Lukas Jungmann
In reply to this post by Jody Grassel
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
> [hidden email]
> 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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Jody Grassel
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?  If there are blockers, which exact bugtracker #s/Github PRs are needed?

On Tue, Sep 24, 2019 at 11:08 AM Lukas Jungmann <[hidden email]> 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
> [hidden email]
> 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
[hidden email]
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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Lukas Jungmann
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
> <[hidden email] <mailto:[hidden email]>> 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
>      > [hidden email] <mailto:[hidden email]>
>      > 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
>     [hidden email] <mailto:[hidden email]>
>     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
> [hidden email]
> 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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Jody Grassel
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?

On Fri, Sep 27, 2019 at 8:56 AM Lukas Jungmann <[hidden email]> 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
> <[hidden email] <mailto:[hidden email]>> 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
>      > [hidden email] <mailto:[hidden email]>
>      > 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
>     [hidden email] <mailto:[hidden email]>
>     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
> [hidden email]
> 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
[hidden email]
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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Lukas Jungmann
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
> <[hidden email] <mailto:[hidden email]>> 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
>      > <[hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>> 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
>      >      > [hidden email]
>     <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >      > 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
>      > [hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >     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
>      > [hidden email] <mailto:[hidden email]>
>      > 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
>     [hidden email] <mailto:[hidden email]>
>     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
> [hidden email]
> 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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Lukas Jungmann
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
>> <[hidden email] <mailto:[hidden email]>> 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
>>      > <[hidden email] <mailto:[hidden email]>
>>     <mailto:[hidden email]
>>     <mailto:[hidden email]>>> 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
>>      >      > [hidden email]
>>     <mailto:[hidden email]>
>>     <mailto:[hidden email]
>>     <mailto:[hidden email]>>
>>      >      > 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
>>      > [hidden email] <mailto:[hidden email]>
>>     <mailto:[hidden email]
>>     <mailto:[hidden email]>>
>>      >     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
>>      > [hidden email] <mailto:[hidden email]>
>>      > 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
>>     [hidden email] <mailto:[hidden email]>
>>     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
>> [hidden email]
>> 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
> [hidden email]
> 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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Jody Grassel
Awesome!  Thank you!

On Mon, Sep 30, 2019 at 11:40 AM Lukas Jungmann <[hidden email]> wrote:
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
>> <[hidden email] <mailto:[hidden email]>> 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
>>      > <[hidden email] <mailto:[hidden email]>
>>     <mailto:[hidden email]
>>     <mailto:[hidden email]>>> 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
>>      >      > [hidden email]
>>     <mailto:[hidden email]>
>>     <mailto:[hidden email]
>>     <mailto:[hidden email]>>
>>      >      > 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
>>      > [hidden email] <mailto:[hidden email]>
>>     <mailto:[hidden email]
>>     <mailto:[hidden email]>>
>>      >     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
>>      > [hidden email] <mailto:[hidden email]>
>>      > 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
>>     [hidden email] <mailto:[hidden email]>
>>     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
>> [hidden email]
>> 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
> [hidden email]
> 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
[hidden email]
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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Phillip Ross-4
why ALFA instead of alpha?  😒

On Tue, Oct 1, 2019 at 2:05 PM Jody Grassel <[hidden email]> wrote:

>
> Awesome!  Thank you!
>
> On Mon, Sep 30, 2019 at 11:40 AM Lukas Jungmann <[hidden email]> wrote:
>>
>> 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
>> >> <[hidden email] <mailto:[hidden email]>> 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
>> >>      > <[hidden email] <mailto:[hidden email]>
>> >>     <mailto:[hidden email]
>> >>     <mailto:[hidden email]>>> 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
>> >>      >      > [hidden email]
>> >>     <mailto:[hidden email]>
>> >>     <mailto:[hidden email]
>> >>     <mailto:[hidden email]>>
>> >>      >      > 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
>> >>      > [hidden email] <mailto:[hidden email]>
>> >>     <mailto:[hidden email]
>> >>     <mailto:[hidden email]>>
>> >>      >     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
>> >>      > [hidden email] <mailto:[hidden email]>
>> >>      > 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
>> >>     [hidden email] <mailto:[hidden email]>
>> >>     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
>> >> [hidden email]
>> >> 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
>> > [hidden email]
>> > 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
>> [hidden email]
>> 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
> [hidden email]
> 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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Radek Felcman
Hello,

        if You mean releases ALFA, ALFA1 there (this is just staging)
        https://oss.sonatype.org/content/groups/staging/org/eclipse/persistence/eclipselink/
        please ignore them. They are testing releases from new Eclipse.org build infrastructure.
        ALFA/alpha....sorry it was my mistake.

                                                        Radek
       

On 10/1/19 10:51 PM, Phillip Ross wrote:

> why ALFA instead of alpha?  😒
>
> On Tue, Oct 1, 2019 at 2:05 PM Jody Grassel <[hidden email]> wrote:
>>
>> Awesome!  Thank you!
>>
>> On Mon, Sep 30, 2019 at 11:40 AM Lukas Jungmann <[hidden email]> wrote:
>>>
>>> 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_eclipselink_downloads_nightly.php&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=hybwjP6ClUhGUhvhE-SPhdqTTDqGl-GPE6axefL268Y&e=  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
>>>>> <[hidden email] <mailto:[hidden email]>> 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
>>>>>       > <[hidden email] <mailto:[hidden email]>
>>>>>      <mailto:[hidden email]
>>>>>      <mailto:[hidden email]>>> 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://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug.cgi-3Fid-3D546431&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=N4LDV8Jf-tx30GNzTZSIsM61z_qlUhxQuWNWgAAOCGA&e=
>>>>>       >
>>>>>       >      >
>>>>>       >      > _______________________________________________
>>>>>       >      > eclipselink-dev mailing list
>>>>>       >      > [hidden email]
>>>>>      <mailto:[hidden email]>
>>>>>      <mailto:[hidden email]
>>>>>      <mailto:[hidden email]>>
>>>>>       >      > To change your delivery options, retrieve your password, or
>>>>>       >     unsubscribe from this list, visit
>>>>>       >      > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>>>>       >      >
>>>>>       >     _______________________________________________
>>>>>       >     eclipselink-dev mailing list
>>>>>       > [hidden email] <mailto:[hidden email]>
>>>>>      <mailto:[hidden email]
>>>>>      <mailto:[hidden email]>>
>>>>>       >     To change your delivery options, retrieve your password, or
>>>>>       >     unsubscribe from this list, visit
>>>>>       > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>>>>       >
>>>>>       >
>>>>>       > _______________________________________________
>>>>>       > eclipselink-dev mailing list
>>>>>       > [hidden email] <mailto:[hidden email]>
>>>>>       > To change your delivery options, retrieve your password, or
>>>>>      unsubscribe from this list, visit
>>>>>       > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>>>>       >
>>>>>      _______________________________________________
>>>>>      eclipselink-dev mailing list
>>>>>      [hidden email] <mailto:[hidden email]>
>>>>>      To change your delivery options, retrieve your password, or
>>>>>      unsubscribe from this list, visit
>>>>>      https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> eclipselink-dev mailing list
>>>>> [hidden email]
>>>>> To change your delivery options, retrieve your password, or
>>>>> unsubscribe from this list, visit
>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>>>>
>>>> _______________________________________________
>>>> eclipselink-dev mailing list
>>>> [hidden email]
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>> _______________________________________________
>>> eclipselink-dev mailing list
>>> [hidden email]
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>>
>> _______________________________________________
>> eclipselink-dev mailing list
>> [hidden email]
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
> _______________________________________________
> eclipselink-dev mailing list
> [hidden email]
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=ffRH6FSHbQx7CUAlzSqCJr_km6HLDdZzP8USzAVjeq0&s=AamdCHUiRz8oWLoIdPrBjZP2x-K2xEbRtmOW5KXBC3M&e=
>
_______________________________________________
eclipselink-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

Lukas Jungmann
In reply to this post by Jody Grassel
just to give you some update wrt 2.7.5:

2.7.5-RC2 has been produced last week on the new infrastructure.

CWe're seeing some test failures in Oracle tests - but Will probably
just found the cause.... Once this gets fixed, RC3 will go out. This
particular fix is the last thing blocking 2.7.5 final release.

thanks,
--lukas

On 10/1/19 8:04 PM, Jody Grassel wrote:

> Awesome!  Thank you!
>
> On Mon, Sep 30, 2019 at 11:40 AM Lukas Jungmann
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     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
>      >> <[hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>> 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
>      >>      > <[hidden email]
>     <mailto:[hidden email]> <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>>> 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
>      >>      >      > [hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>>
>      >>      >      > 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
>      >>      > [hidden email]
>     <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>>
>      >>      >     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
>      >>      > [hidden email]
>     <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>      > 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
>      >> [hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     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
>      >> [hidden email] <mailto:[hidden email]>
>      >> 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
>      > [hidden email] <mailto:[hidden email]>
>      > 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
>     [hidden email] <mailto:[hidden email]>
>     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
> [hidden email]
> 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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: Time to cut a new 2.7?

William Dazey
Hello!
ya, I found the issue. It was a copy/paste mistake when I ported a fix from master -> 2.7 -> 2.6_WAS. I have PRs out now to fix the issues.

Thanks,
Will Dazey

On Tue, Oct 15, 2019 at 4:15 PM Lukas Jungmann <[hidden email]> wrote:
just to give you some update wrt 2.7.5:

2.7.5-RC2 has been produced last week on the new infrastructure.

CWe're seeing some test failures in Oracle tests - but Will probably
just found the cause.... Once this gets fixed, RC3 will go out. This
particular fix is the last thing blocking 2.7.5 final release.

thanks,
--lukas

On 10/1/19 8:04 PM, Jody Grassel wrote:
> Awesome!  Thank you!
>
> On Mon, Sep 30, 2019 at 11:40 AM Lukas Jungmann
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     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
>      >> <[hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>> 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
>      >>      > <[hidden email]
>     <mailto:[hidden email]> <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>>> 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
>      >>      >      > [hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>>
>      >>      >      > 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
>      >>      > [hidden email]
>     <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>
>      >>     <mailto:[hidden email]
>     <mailto:[hidden email]>>>
>      >>      >     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
>      >>      > [hidden email]
>     <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>      > 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
>      >> [hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>      >>     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
>      >> [hidden email] <mailto:[hidden email]>
>      >> 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
>      > [hidden email] <mailto:[hidden email]>
>      > 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
>     [hidden email] <mailto:[hidden email]>
>     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
> [hidden email]
> 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
[hidden email]
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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipselink-dev