Starting release
On Thu, Feb 1, 2018 at 7:42 AM Vlad Mihalcea
wrote:
> Thanks,
>
> I was having some Pull Requests which I pushed to 5.2.13 and wanted to
> have them in 5.3 as well.
>
> I will add them now.
>
> Vlad
>
> On Thu, Feb 1, 2018 at 3:34 PM, Steve Ebersole
> wrote:
>
>> If it's stuff
If it's stuff that's ready to go, go for it. I'll send out an email when
I'm ready to start.
On Thu, Feb 1, 2018, 7:28 AM Vlad Mihalcea wrote:
> Hi Steve,
>
> Is it ok to commit on the master branch today or should we wait for 5.3 to
> be released?
>
> Vlad
> On Thu, Feb 1, 2018 at 4:03 AM, Ste
Thanks,
I was having some Pull Requests which I pushed to 5.2.13 and wanted to have
them in 5.3 as well.
I will add them now.
Vlad
On Thu, Feb 1, 2018 at 3:34 PM, Steve Ebersole wrote:
> If it's stuff that's ready to go, go for it. I'll send out an email when
> I'm ready to start.
>
> On Thu
Hi Steve,
Is it ok to commit on the master branch today or should we wait for 5.3 to
be released?
Vlad
On Thu, Feb 1, 2018 at 4:03 AM, Steve Ebersole wrote:
> I am waiting until I hear back from Joel from Sonatype regarding disabling
> the JBoss Nexus -> OSSRH sync for ORM artifacts before I c
On 1 February 2018 at 02:03, Steve Ebersole wrote:
> I am waiting until I hear back from Joel from Sonatype regarding disabling
> the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.
Just curious: is that a requirement to start releasing on OSSRH?
I was assuming that simply not
I am waiting until I hear back from Joel from Sonatype regarding disabling
the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.
On Wed, Jan 31, 2018 at 10:06 AM Guillaume Smet
wrote:
> On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole
> wrote:
>
>> Yes, I agree. As it is, it is
On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole wrote:
> Yes, I agree. As it is, it is very likely that in 2 weeks we will have
> ORM 5.3.0.CR1. So even if you did do a OGM release at that time we are
> going to be limited in what exactly we can change if we find changes are
> needed.
>
> Inter
Yes, I agree. As it is, it is very likely that in 2 weeks we will have ORM
5.3.0.CR1. So even if you did do a OGM release at that time we are going
to be limited in what exactly we can change if we find changes are needed.
Interestingly this goes back to earlier discussions about "release
early/
On Wed, Jan 31, 2018 at 4:42 PM, Steve Ebersole wrote:
> The next time-box is in fact 2 weeks... :)
>
> But yes, OGM makes me a little nervous as as far as I know we have no idea
> about that integration yet
>
We discussed it on Tuesday at our meeting.
I think we can commit to getting your feed
The next time-box is in fact 2 weeks... :)
Hopefully we have these JPA TCK challenges resolved by then and can do CR
then. So yes, please have feedback by then. Yoann and I have been working
on Search and ORM 5.3 (at least parts) so I think that will work out fine.
But yes, OGM makes me a little
I would say let's go for Beta2. We are not in a hurry considering the
challenges still pending so no need to rush in the CR phase.
On the NoORM side:
- Search - Yoann has prepared a PR with the 5.3 support so we should be OK
on this side. 5.9 will be tagged early next week and we'll release an alp
I have no strong preference either way.
On 01/30/2018 05:00 PM, Steve Ebersole wrote:
> Wanted to remind everyone that tomorrow is the next time-boxed release for
> 5.3.
>
> I wanted to get everyone's opinions about the version number, whether this
> should be Beta2 or CR1. IMO It depends how you
having a Beta2 release is fine also to me
On 31 January 2018 at 10:26, Sanne Grinovero wrote:
> I would suggest a Beta2, as we were hoping to still do some work on
> it. No strong take though, as far as I know our pending work is
> optional / low impact:
> A. produce the feature packs in ORM
>
I would suggest a Beta2, as we were hoping to still do some work on
it. No strong take though, as far as I know our pending work is
optional / low impact:
A. produce the feature packs in ORM
B. test OGM integration
Status of these:
A#
The feature packs have low impact on ORM's risk and quality,
On Tue, Jan 30, 2018 at 11:00 PM, Steve Ebersole
wrote:
> Wanted to remind everyone that tomorrow is the next time-boxed release for
> 5.3.
>
> I wanted to get everyone's opinions about the version number, whether this
> should be Beta2 or CR1. IMO It depends how you view the remaining
> challen
Wanted to remind everyone that tomorrow is the next time-boxed release for
5.3.
I wanted to get everyone's opinions about the version number, whether this
should be Beta2 or CR1. IMO It depends how you view the remaining
challenges with the JPA TCK, with CR1 being the optimistic view.
___
16 matches
Mail list logo
