Re: [hibernate-dev] ORM release process
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, you just need to create the X.Y.Z.yml file as usual.
BTW, with the work Yoann did, you don't really need to mark the previous
micros as displayed: false anymore.
--
Guillaume
On Thu, Sep 28, 2017 at 6:30 PM, andrea boriero <dreborier(a)gmail.com> wrote:
Thanks Guillame
the *orm/releases/<version>/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 <crancran(a)gmail.com> wrote:
> Thanks Guillaume.
>
> On 09/28/2017 10:25 AM, Guillaume Smet wrote:
> > 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 and a
> *orm*
> > */releases/<version>/index.adoc* file.
> >
> > Basically, you have to do the same thing for the release page than what
> you
> > already do with your custom documentation page.
> >
> > We already created them for the existing releases so you already have
> > templates you just have to adjust when publishing a new major release.
> >
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>