Re: [hibernate-dev] Wrapping up 5.4.0
With regard to entity graphs, the only new piece is the "parse a string representation" feature. I'll write up a release notes blurb with a simple code sample, but the new documentation sections cover this feature very in-depth. On Mon, Nov 5, 2018 at 12:07 PM Guillaume Smet wrote: > Hi, > > If everybody is OK with it, I would like to wrap 5.4.0.CR1 on Wednesday > 14th (this is next Wednesday). > > That means that everything we want in 5.4.0 should be in by then. > > The big remaining subject IMHO is this one: > https://github.com/hibernate/hibernate-orm/pull/2611 . I think we really > need that in. > > Chris, Gail, do you think you can drive this puppy home before then? > > If you have issues affected to you that you know won't be fixed before next > Wednesday, can you please move them to 5.4.1 so that we have a clear vision > of the remaining work? > > Steve, could you please prepare a paragraph about the entity graph work for > the announcement? As it's the big new feature of this release, some code > showing the improvements made would be welcome, I think. > > Thanks! > > -- > Guillaume > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Boolean with null values and SAP SQL Anywhere
+1 to fix + note in the migration guide. On Fri, Nov 2, 2018 at 8:29 AM Guillaume Smet wrote: > Yeah, personally, I think it's a bug, e.g. this type shouldn't have been > used in the first place. > > But as it works when not storing nulls in the column, YMMV depending if you > use null or not. > > My vote goes to fix + note in the migration guide. > > Gail, what's your take on this one? > > Thanks! > > > On Fri, Nov 2, 2018 at 4:14 PM Steve Ebersole wrote: > > > In the general sense, it ultimately comes down to how one views the > > situation. Is it a bug? Then I think it is reasonable to just change it > > and mention it in the migration guide. If it is an enhancement, then I > > think a setting makes sense to control this. > > > > Honestly though, not sure this has a big compatibility impact. > > > > On Fri, Nov 2, 2018 at 10:00 AM Guillaume Smet > > > wrote: > > > >> Hi, > >> > >> Quite some time ago, someone opened > >> https://hibernate.atlassian.net/browse/HHH-12850 stating that null > values > >> were not supported for Booleans with SAP SQL Anywhere. > >> > >> This is due to the fact that null values are not supported for bits and > we > >> should use a tinyint. Interestingly enough, it was fixed for Sybase > here: > >> https://hibernate.atlassian.net/browse/HHH-5413 . > >> > >> Changing this will probably lead to compatibility issues but I think a > >> note > >> in the migration guide requiring a migration from bit to tinyint would > be > >> sufficient and 5.4.0 would be a good opportunity to do it. > >> > >> Thoughts? > >> > >> -- > >> Guillaume > >> ___ > >> hibernate-dev mailing list > >> hibernate-dev@lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > >> > > > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Releasing a new "major" HCANN version for ORM 5.4
Personally I would not use 6 as the version following the "goal" of trying to align major versions across projects where feasible (and here I think it is feasible). But +1 to releasing 5.1.0 On Mon, Nov 5, 2018 at 10:43 AM Guillaume Smet wrote: > Hi, > > Sanne merged > https://github.com/hibernate/hibernate-commons-annotations/pull/11 into > HCANN master a while ago, master that is currently labelled as 6. > > Wondering if we should release a HCANN 5.1.0 containing this fix (not sure > a 6 is needed for that but I don't really mind if some of you prefer 6) to > be consumed by ORM 5.4.0. > > That would allow to merge > https://github.com/hibernate/hibernate-orm/pull/2050 and remove the > java.util restriction on collections which seems like a good thing. > > What do you all think? > > -- > Guillaume > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] [ORM] Releasing 5.2.18?
Hi, So, I was thinking (again) about releasing a 5.2.18. https://hibernate.atlassian.net/projects/HHH/versions/31663/tab/release-report-todo says: - we have 4 issues about adding stuff to the migration notes. Gail, do you still think it's useful? Maybe for people going from 5.1 to 5.3? How much work would it be? E.g. if it's a 2 hours effort, it sounds like a good investment but if it's a 2 days effort, not so much. - This issue is bugging me a bit https://hibernate.atlassian.net/browse/HHH-12251 as it's a regression introduced in 5.2.13. Would somebody have time to take a look at it (once the 5.4.0 related tasks are done)? AFAIK, Vlad already put a test case together. If not, I suppose we would just move it to 5.4-backlog and consider it for 5.4. (Or release another 5.2.x later if the fix is backportable). - https://hibernate.atlassian.net/browse/HHH-12276 - This one was already present in 5.0 so it's low priority for me. I would vote for keeping it for later. Thanks for the feedback. -- Guillaume ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Wrapping up 5.4.0
Hi, If everybody is OK with it, I would like to wrap 5.4.0.CR1 on Wednesday 14th (this is next Wednesday). That means that everything we want in 5.4.0 should be in by then. The big remaining subject IMHO is this one: https://github.com/hibernate/hibernate-orm/pull/2611 . I think we really need that in. Chris, Gail, do you think you can drive this puppy home before then? If you have issues affected to you that you know won't be fixed before next Wednesday, can you please move them to 5.4.1 so that we have a clear vision of the remaining work? Steve, could you please prepare a paragraph about the entity graph work for the announcement? As it's the big new feature of this release, some code showing the improvements made would be welcome, I think. Thanks! -- Guillaume ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Releasing a new "major" HCANN version for ORM 5.4
Hi, Sanne merged https://github.com/hibernate/hibernate-commons-annotations/pull/11 into HCANN master a while ago, master that is currently labelled as 6. Wondering if we should release a HCANN 5.1.0 containing this fix (not sure a 6 is needed for that but I don't really mind if some of you prefer 6) to be consumed by ORM 5.4.0. That would allow to merge https://github.com/hibernate/hibernate-orm/pull/2050 and remove the java.util restriction on collections which seems like a good thing. What do you all think? -- Guillaume ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Chat migration - D minus 115 until the death of HipChat
Not everyone voted, far from it; we're missing votes from Gail, Guillaume, Fabio, Chris, Davide, Emmanuel, Koen. So no, no consensus yet. I sent an email to them off-list, perhaps they didn't see this thread. Provisional results are as follows: IRC: 2 Yes, 3 "if need be", 3 no Slack: 2 Yes, 2 "if need be", 4 no Zulip: 2 Yes, 3 "if need be", 3 no Gitter: 6 Yes, 0 "if need be", 2 no So Gitter seems on the verge of winning, but apparently some people are categorically against it, so I'd say we'll have to give them a chance to explain why. I'll wait for everyone to answer, though, since they could completely change the results. Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On Sat, 3 Nov 2018 at 13:35, Steve Ebersole wrote: > Any consensus on this yet? > > On Tue, Oct 23, 2018 at 5:21 AM Sanne Grinovero > wrote: > >> Thanks for starting this! >> >> The choice of IRC is a bit special on the list as we never intended it >> to be killed: it has been historically important and we should >> maintain some level of reachability on it. So voting for the "IRC" >> choice just means a preference to not use anything else on top of it, >> while alternatively we'' be using X on top of IRC, albeit with a >> preference to use X for team conversations. >> >> Also good to remind: please try to be on IRC as well occasionally as >> many in the OSS community we integrate with will reach out there. >> >> Thanks, >> Sanne >> >> On Tue, 23 Oct 2018 at 09:46, Yoann Rodiere wrote: >> > >> > Hi, >> > >> > TL;DR: please vote here if you don't want to end up having to use a chat >> > tool you don't like: https://doodle.com/poll/h6scc9bsh6a4ymre >> > >> > HipChat Cloud will stop working on February 15th, 2019 [1]. We need to >> > choose an alternative before we have our back against the wall, so I'll >> try >> > to resurrect the conversation. >> > >> > As a reminder, Stride is no longer an option: Atlassian cancelled the >> > project, and encourages users to migrate to Slack. >> > >> > The discussed options so far were: >> > >> >- *Moving back to IRC*. Aye: ?; nay: ? >> >Pros: simple as hell. >> >Cons: basic as hell; we won't keep the chat history. >> >- *Migrating to Slack* [6], as suggested by Atlassian [2]. Aye: >> >Christian B; Nay: ? >> >Pros: we will keep the chat history (I think). >> >Cons: not open-source; desktop client consumes a lot of resources. >> >- *Migrating to Zulip* [3]. Aye: Emmanuel, Yoann. Nay: Guillaume >> (kind >> >of). >> >Pros: Advanced conversation management thanks to the "topics" >> feature. >> >Cons: Complex to use because of the "topics" feature; we won't keep >> the >> >chat history (1). >> >- *Migrating to Gitter* [5] (we'll create different rooms, probably). >> >Aye: ?, Nay: ? >> >Pros: Users seem to actually go there, so we could have our "live >> >support" rooms next to our "internal discussion" rooms. >> >Cons: not open-source; we won't keep the chat history (1). >> > >> > I created a poll based on the discussion we had on the thread >> > "[hibernate-dev] Stride". I think everyone had the time to suggest >> another >> > option. >> > >> > Please vote here and now, or remain silent forever ;): >> > https://doodle.com/poll/h6scc9bsh6a4ymre >> > >> > I'd suggest the following rules: if there's a single clear winner (a >> > platform that everyone would be happy with), we'll pick that one. If >> there >> > are multiple clear winners, whoever does the migration work will pick >> > what's easier to set up (taking into account the various integrations). >> > Otherwise, back to discussing it on this thread... >> > >> > (1) There seems to be some work in progress on a migration tool from >> > HipChat to Zulip, but it doesn't seem to be ready yet [4] >> > >> > [1] >> > >> https://www.atlassian.com/partnerships/slack/faq#faq-da2b66a1-53d3-4c4e-a405-467d961336f7 >> > [2] https://www.atlassian.com/partnerships/slack/migration >> > [3] https://hibernate.zulipchat.com/ >> > [4] https://github.com/zulip/zulip/issues/10647 >> > [5] https://gitter.im/hibernate/hibernate-orm >> > [6] https://slackdemo.com/ >> > >> > Yoann Rodière >> > Hibernate NoORM Team >> > yo...@hibernate.org >> > ___ >> > hibernate-dev mailing list >> > hibernate-dev@lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >> >> ___ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
