Re: [hibernate-dev] HBX-1193 (oracle) reverse engineering of UniqueConstraint annotation for function-based indexes
Apologies for the empty email last time https://hibernate.atlassian.net/browse/HBX-1193 Hi, I've submitted a pull request for this issue. Is there anything more I need to do or could help with to close this one off? Thanks, Graham ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] NoORM IRC meeting minutes
Hi, Here are the minutes of our IRC meeting: 15:20 < jbott> Meeting ended Tue Oct 23 13:20:49 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 15:20 < jbott> Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/hibernate-dev.2018-10-23-13.00.html 15:20 < jbott> Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/hibernate-dev.2018-10-23-13.00.txt 15:20 < jbott> Log: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/hibernate-dev.2018-10-23-13.00.log.html Cheers, -- 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
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] Chat migration - D minus 115 until the death of HipChat
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
