Btw, it's not à one line array, you also have he Java version.
So maybe what's missing is a header to make it clearer?
> Le 28 sept. 2017 à 16:33, Guillaume Smet a écrit :
>
>> On Thu, Sep 28, 2017 at 4:26 PM, Sanne Grinovero wrote:
>> But I see
To be honest, I think that is perfect process Guillaume. I can now define
all that content and information in one place, which is a huge win. Which
make me think of a future nice-to-have we could consider... to drive the
release announcements (blog, emails, twitter, etc) from the content of a
That was a rich joke Sanne...
On Thu, Sep 28, 2017 at 9:27 AM Sanne Grinovero wrote:
> On 28 September 2017 at 15:10, Steve Ebersole wrote:
> > If you really like the gold, why not try making that whole banner gold?
>
> It's expensive!
>
> >
> >
> >
Thanks Guillame
the *orm/releases//index.adoc* file should be changed only in case
of a major or minor not for a micro, am I right?
On 28 September 2017 at 16:58, Chris Cranford wrote:
> Thanks Guillaume.
>
> On 09/28/2017 10:25 AM, Guillaume Smet wrote:
> > Hi ORM guys,
On Thu, Sep 28, 2017 at 4:26 PM, Sanne Grinovero
wrote:
> But I see how this can be far fetched, while there are objectinve
> benefits from having a cleaner table, so feel free to remove it.
>
Well not really.
I personally don't want to maintain specific templates for each
You just need to create it for a major.
It's this page: http://hibernate.org/orm/releases/5.2/ presenting the whole
major.
You can keep it simple or add content to it presenting the major as done
here in the What's new section: http://hibernate.org/search/releases/5.8/.
For a minor or a micro,
On Thu, Sep 28, 2017 at 6:41 PM, Steve Ebersole wrote:
> To be honest, I think that is perfect process Guillaume. I can now
> define all that content and information in one place, which is a huge win.
> Which make me think of a future nice-to-have we could consider... to
Thanks a lot Guillaume and Yoann, great work.
On 28 September 2017 at 17:41, Steve Ebersole wrote:
> To be honest, I think that is perfect process Guillaume. I can now define
> all that content and information in one place, which is a huge win. Which
> make me think of a
Hey Vlad,
I recently learned about your "Hibernate Types" project [1]. It's great to
see support for JSON, arrays, etc!
Out of curiosity, though, why did you decide to make it a separate project
instead of adding these very useful types to Hibernate itself? Seems it'd
be easier for people to us
I'm not so sure a single "extras" artifact/module makes the most sense
though. Since some involve pulling in driver jars - I think (if we do
this) we ought to have `hibernate-extras-base` as well as db-specific
extensions (`hibernate-extras-pgsql`, ...).
We had a similar discussion recently on
Looks OK to me!
On Thu, Sep 28, 2017 at 9:43 AM, Yoann Rodiere wrote:
> So the order would be:
>
> * Compatibility
> * Documentation
> * How to get it
> * What's new
> * Migrate
> * Releases in this series (we just renamed it, I think it pretty much
> solves the issue we
2017-09-28 11:28 GMT+02:00 Vlad Mihalcea :
> Hi,
>
> It's because not all database support ARRAY or JSON.
>
> We've been discussing this on the mailing list (around one year ago) and I
> remember we concluded that we can only add these types to ORM core
> if the vast
Overall the new design looks amazing. I do agree with Andrea about the
gold backgrounds - that looks anything but modern and does not match the
rest of the site design imo.
For another iteration... "Getting started" is another group of information
that is version specific.
A minor thing that I
Do y'all really think it makes sense to have JPA versions in this ORM
"compatibility matrix"?
My concern is that it is more involved (as we then try to convey in the
section below that matrix) than a cell in a matrix/table with just a
version number.
If we end up treating JPA compatibility
Hi,
It's because not all database support ARRAY or JSON.
We've been discussing this on the mailing list (around one year ago) and I
remember we concluded that we can only add these types to ORM core
if the vast majority of the Hibernate-supported database offer JSON or
ARRAY.
Also, even if we
+1. Either we properly mirror our tweets/blog posts to G+, or we stop
advertising that account.
Yoann Rodière
Hibernate NoORM Team
yo...@hibernate.org
On 28 September 2017 at 11:51, Guillaume Smet
wrote:
> Hi,
>
> We have a couple of Google+ links here and there on
On 28 September 2017 at 10:51, Guillaume Smet wrote:
> Hi,
>
> We have a couple of Google+ links here and there on the website.
>
> I was thinking we should probably remove them as they sound a bit 2010 and
> I don't think we are actively maintaining it.
>
> WDYT?
On 28 September 2017 at 11:11, Yoann Rodiere wrote:
> +1. Either we properly mirror our tweets/blog posts to G+, or we stop
> advertising that account.
Let's try using G+ a bit more?
>
>
> Yoann Rodière
> Hibernate NoORM Team
> yo...@hibernate.org
>
> On 28 September 2017
On Thu, Sep 28, 2017 at 12:39 PM, Gunnar Morling
wrote:
> I see. A separate project/repo under the Hibernate umbrella could be an
> alternative, too ("Hibernate Extras" or so). I.e. some middle ground
> between part of ORM proper and fully being 3rd party.
>
+1 to make it
Done.
On Thu, Sep 28, 2017 at 11:13 AM, Guillaume Smet
wrote:
> Looks OK to me!
>
> On Thu, Sep 28, 2017 at 9:43 AM, Yoann Rodiere
> wrote:
>
>> So the order would be:
>>
>> * Compatibility
>> * Documentation
>> * How to get it
>> * What's new
>>
On Thu, Sep 28, 2017 at 9:21 AM, Guillaume Smet
wrote:
> I was talking about the ability to access the old series when they are not
> displayed in the overview.
>
> AFAICS, this is definitely missing and we would need either a page with
> all the series linked from the
On 28 September 2017 at 11:39, Gunnar Morling wrote:
> 2017-09-28 11:28 GMT+02:00 Vlad Mihalcea :
>
>> Hi,
>>
>> It's because not all database support ARRAY or JSON.
>>
>> We've been discussing this on the mailing list (around one year ago) and I
>>
On 28 September 2017 at 08:21, Guillaume Smet wrote:
> On Thu, Sep 28, 2017 at 9:00 AM, Yoann Rodiere wrote:
>>
>> >
>> > > As a user, I still need to be able to go to a given series page to
>>
>> > understand what was done (see my initial use
Hi,
We have a couple of Google+ links here and there on the website.
I was thinking we should probably remove them as they sound a bit 2010 and
I don't think we are actively maintaining it.
WDYT?
--
Guillaume
___
hibernate-dev mailing list
On Thu, Sep 28, 2017 at 12:10 PM, Sanne Grinovero
wrote:
> Personally I'm more of a Twitter user but some other people actually
> used to advertise our stuff on G+
>
> I think Steve manages that? Make sure to check with him before removing
> these.
>
Ah yes, I should have
I think it would be a good idea to post on Google+ whenever we add a new
blog article
On 28 September 2017 at 12:26, Sanne Grinovero wrote:
> On 28 September 2017 at 11:11, Yoann Rodiere wrote:
> > +1. Either we properly mirror our tweets/blog posts to
I think the new layout is fine except for the gold background colour of the
project names, I really do not like it.
What about an opinion from the jboss.org design team?
On 26 September 2017 at 17:08, Guillaume Smet
wrote:
> On Tue, Sep 26, 2017 at 3:47 PM, Davide
On Thu, Sep 28, 2017 at 2:11 PM, Steve Ebersole wrote:
> Overall the new design looks amazing. I do agree with Andrea about the
> gold backgrounds - that looks anything but modern and does not match the
> rest of the site design imo.
>
Frankly, it feels weird without. So
On Thu, Sep 28, 2017 at 3:23 PM, Guillaume Smet
wrote:
> On Thu, Sep 28, 2017 at 2:11 PM, Steve Ebersole
> wrote:
>
>> Overall the new design looks amazing. I do agree with Andrea about the
>> gold backgrounds - that looks anything but modern and
On 28 September 2017 at 14:09, Sanne Grinovero wrote:
> On 28 September 2017 at 13:11, Steve Ebersole wrote:
>> Overall the new design looks amazing. I do agree with Andrea about the
>> gold backgrounds - that looks anything but modern and does not
On 28 September 2017 at 13:11, Steve Ebersole wrote:
> Overall the new design looks amazing. I do agree with Andrea about the
> gold backgrounds - that looks anything but modern and does not match the
> rest of the site design imo.
>
> For another iteration... "Getting
What's in the matrix is up to each project. You can remove content by
editing the .yml file for each series, and removing elements from site.yml
under projects.orm.integrations.
I'd argue that moving away from the matrix for ORM just because Java
compatibility is "not enough" will force us to add
On 28 September 2017 at 13:30, Steve Ebersole wrote:
> Do y'all really think it makes sense to have JPA versions in this ORM
> "compatibility matrix"?
I think it's useful. Try booting a recent ORM version with an out of
date JPA api jar: you'll get really weird exceptions
The question is not about whether to have that information. The question
is whether a one row table spanning horizontally across the screen is the
best presentation for that info.
On Thu, Sep 28, 2017 at 8:01 AM Sanne Grinovero wrote:
> On 28 September 2017 at 13:30, Steve
Ah, so its retro-modern ;)
So what happens if you remove the gold/light-gray completely and just use
the dark-gray as background for the white-lettered words? Seems like that
would JustWork.
On Thu, Sep 28, 2017 at 8:33 AM Guillaume Smet
wrote:
> On Thu, Sep 28,
Guillaume -
If we must keep a background color, I think the new color you've changed
on staging
feels like it flows much more than the gold and is far more appealing to
the eye, imo.
Chris
On 09/28/2017 09:32 AM, Guillaume Smet wrote:
> On Thu, Sep 28, 2017 at 3:23 PM, Guillaume Smet
P.S. Sorry, I would TIAS but my CSS skills are slight better than those of
an ocelot.
On Thu, Sep 28, 2017 at 8:55 AM Steve Ebersole wrote:
> Ah, so its retro-modern ;)
>
> So what happens if you remove the gold/light-gray completely and just use
> the dark-gray as
OK, let's settle on the grey one then.
Sigh. :)
On Thu, Sep 28, 2017 at 3:56 PM, Chris Cranford wrote:
> Guillaume -
>
> If we must keep a background color, I think the new color you've changed
> on staging
> feels like it flows much more than the gold and is far more
If you really like the gold, why not try making that whole banner gold?
On Thu, Sep 28, 2017 at 9:09 AM Guillaume Smet
wrote:
> OK, let's settle on the grey one then.
>
> Sigh. :)
>
> On Thu, Sep 28, 2017 at 3:56 PM, Chris Cranford
> wrote:
>
>>
On Thu, Sep 28, 2017 at 3:53 PM, Steve Ebersole wrote:
> The question is not about whether to have that information. The question
> is whether a one row table spanning horizontally across the screen is the
> best presentation for that info.
>
Yeah, the example of ORM is
On 28 September 2017 at 14:53, Steve Ebersole wrote:
> The question is not about whether to have that information. The question is
> whether a one row table spanning horizontally across the screen is the best
> presentation for that info.
TBH I don't remember myself which
Hi ORM guys,
So with a new website comes new responsabilities.
I updated the NoORM release process but I don't know where you put these
information for ORM.
So basically, when you release a new MAJOR version, you will have to take
care of adding a *data/projects/orm/releases/series.yml *file
On 28 September 2017 at 15:10, Steve Ebersole wrote:
> If you really like the gold, why not try making that whole banner gold?
It's expensive!
>
>
> On Thu, Sep 28, 2017 at 9:09 AM Guillaume Smet
> wrote:
>
>> OK, let's settle on the grey one
>
> > As a user, I still need to be able to go to a given series page to
> understand what was done (see my initial use case). But they can be in a
> > older series section in small vs big boxes.
> This is currently missing.
NO, it is not missing. At least, the concept is there. The "What's
> On 28 Sep 2017, at 09:00, Yoann Rodiere wrote:
>
> And yes, there's too much content in this section for Search 5.8, but that's
> mainly because there's too much content in 5.8 to begin with.
Ah, finally an objective measurement to force Sanne to release smaller but
On Thu, Sep 28, 2017 at 9:00 AM, Yoann Rodiere wrote:
> >
> > > As a user, I still need to be able to go to a given series page to
>
> > understand what was done (see my initial use case). But they can be in a
> > > older series section in small vs big boxes.
> > This is
Hello
Watching new.hibernate.org (2017-09-28 9:00 CET), I have two minor proposals.
In frequency, I think people go read the docs online much more than they want
to know how to get it. So I would put the Documentation section at the top (or
below the compatibility matrix if you won’t budge).
And I am +1 to push the new style today. These discussions are not linked.
> On 28 Sep 2017, at 09:17, Emmanuel Bernard wrote:
>
> Hello
>
> Watching new.hibernate.org (2017-09-28 9:00 CET), I have two minor proposals.
>
> In frequency, I think people go read the docs
So the order would be:
* Compatibility
* Documentation
* How to get it
* What's new
* Migrate
* Releases in this series (we just renamed it, I think it pretty much
solves the issue we were having)
Right?
Seems ok to me, no strong opinion about that. As long as compatibility info
stays at the
Hi all,
Better late that never, here are the minutes of this week's IRC meeting:
16:04 < jbott> Ending meeting. Generating minutes. Be patient :)
16:04 < jbott> Meeting ended Tue Sep 26 14:04:37 2017 UTC. Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:04 < jbott>
50 matches
Mail list logo