Hey,
I pushed an update to staging. I only converted the "Search" part for now.
What changes:
- The _data folder structured changed a bit, so that we can introduces a
YAML file for each series (5.5, 5.6, 5.6, 5.8, ...), containing a summary
of this series and a list of integration constr
Thanks Yoann!
Looks great.
Two minor suggestions:
- could the two links we have for each release on search/releases/ on
two separate lines? Or something else to make it clear that there are
two linkes.
- Regarding the "Compatibility matrix", the header line (the one in
black) .. I think we need
Sanne, I addressed both your comments. Is it better?
I also addressed Guillaume's comment on HipChat, and made the compatibility
matrix a bit... fuzzier, so that we won't have to update it as often. We
can still make it very specific if we want to, but we won't be limited by
the layout anymore.
Yo
For me the real problem is that its not just Downloads/Releases that should
be (need to be really) treated in this manner - our documentation is also
family specific.
So for ORM I had envisioned a "versions" (although "releases" works just as
well) component to the url scheme. Vlad did this for d
Steve,
If I understood correctly, the main difference between what I did and what
you want is you don't want a "hub" pointing to different versions, you want
to redirect to the page for the latest version, and from there allow to
move to another version using drop-down.
While I can understand you'
Following Steve's comments, I made another few changes for the sake of
usability:
- Moved the series-specific pages so that the path is more consistent
with ORM documentation; the series-specific page for Search 5.8, for
instance, is now http://staging.hibernate.org/search/releases/5.8/
On Fri, Sep 8, 2017 at 9:45 AM Yoann Rodiere wrote:
> Steve,
>
> If I understood correctly, the main difference between what I did and what
> you want is you don't want a "hub" pointing to different versions, you want
> to redirect to the page for the latest version, and from there allow to
> mov
On 8 September 2017 at 14:46, Yoann Rodiere wrote:
> Sanne, I addressed both your comments. Is it better?
I love it, definitely a step forward!
But we'll need to find some compromise with the requirements of the
other projects - e.g. Steve's feedback - : it should be consistent
across them for p
Hi,
Note to Gail: this is potentially a blocking issue for 5.2.11 for the OGM
upgrade (I thought it was a bug in OGM but apparently, it's an issue with
ORM).
In 5.2 SessionImpl, we now use getInterceptor() instead of accessing the
interceptor field directly because the field has been moved to
Abs
Are the tests in the documentation module expected to run on MySQL /
MariaDB only? Or are they expected to run on all databases?
The test org.hibernate.userguide.mapping.basic.SubselectTest is failing
on Firebird, because it has the following subselect:
@Subselect(
"select " +
" a.id
I test Hibernate with the following DBs mostly:
- H2
- Oracle
- SQL Server
- PostgreSQL
- MySQL and MariaDb
For other databases, it's not guaranteed that all tests will run.
Related to that function, we could other add a change, but it must work on
the DBs above too.
Or, you could just mark the
On 2017-09-08 20:23, Vlad Mihalcea wrote:
> I test Hibernate with the following DBs mostly:
>
> - H2
> - Oracle
> - SQL Server
> - PostgreSQL
> - MySQL and MariaDb
>
> For other databases, it's not guaranteed that all tests will run.
>
> Related to that function, we could other add a change, but
12 matches
Mail list logo
