9:25 a.m.
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.
--
Guillaume
10:58 a.m.
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.
11:30 a.m.
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
11:47 a.m.
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
>
11:41 a.m.
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
series.yml.
Thanks again for all your work on these changes. It really does look a lot
better I think.
On Thu, Sep 28, 2017 at 11:16 AM 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
11:48 a.m.
On Thu, Sep 28, 2017 at 6:41 PM, Steve Ebersole <steve(a)hibernate.org> 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 drive
the release announcements (blog, emails, twitter, etc) from the content of
a series.yml.
Thanks again for all your work on these changes. It really does look a
lot better I think.
The release work is Yoann's. I just worked on the new layout. So kudos go
to him for the Releases page improvement!
--
Guillaume
12:08 p.m.
Thanks a lot Guillaume and Yoann, great work.
On 28 September 2017 at 17:41, Steve Ebersole <steve(a)hibernate.org> 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 drive the
release announcements (blog, emails, twitter, etc) from the content of a
series.yml.
Thanks again for all your work on these changes. It really does look a lot
better I think.
On Thu, Sep 28, 2017 at 11:16 AM 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
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:22 a.m.
Hi,
Thanks Guillaume for stepping up to explain this. I should have done it but
I guess I forgot :)
You just need to create it for a major.
It's this page: http://hibernate.org/orm/releases/5.2/ presenting the
whole
major.
I think there's a confusion between major, minor an micro here.
Our version numbers are: major.minor.micro. As far as I understood, 5 is a
major version, 5.2 is a minor version, 5.2.1 is a micro.
To sum up:
- New micro/alpha/beta/CR/whatever: just add a new
_data/orm/releases/<major.minor>/<major.minor.micro.FinalOrAlphaOrBetaOrWhatever>.yml
file like you used to. No need to change/remove the previous ones, and in
fact you shouldn't remove them: removing files will break stuff.
- New major or minor:
- add a new _data/orm/releases/<major.minor>/series.yml file
- add a new
_data/orm/releases/<major.minor>/<major.minor.0.FinalOrAlphaOrBetaOrWhatever>.yml
file.
- add a new orm/releases/<major.minor>/index.adoc file. It can be
empty except for the AsciiDoc metadata, but ideally you would
put in there
a description of the minor. The content will appear in the "What's
new"
section on the series page. For example:
http://hibernate.org/search/releases/5.8/#whats-new. Obviously you'll
want to keep yours shorter, I'm just not good at summarizing ;)
Thanks,
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
On 28 September 2017 at 19:08, andrea boriero <andrea(a)hibernate.org> wrote:
Thanks a lot Guillaume and Yoann, great work.
On 28 September 2017 at 17:41, Steve Ebersole <steve(a)hibernate.org> 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 drive the
> release announcements (blog, emails, twitter, etc) from the content of a
> series.yml.
>
> Thanks again for all your work on these changes. It really does look a
lot
> better I think.
>
> On Thu, Sep 28, 2017 at 11:16 AM 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
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:38 a.m.
Yoann your understood of major, minor and micro seems correct to me at
least it is what I understood too and Thanks for the sum up, really clear.
On 29 September 2017 at 09:22, Yoann Rodiere <yoann(a)hibernate.org> wrote:
Hi,
Thanks Guillaume for stepping up to explain this. I should have done it
but I guess I forgot :)
> You just need to create it for a major.
> It's this page: http://hibernate.org/orm/releases/5.2/ presenting the
> whole
> major.
I think there's a confusion between major, minor an micro here.
Our version numbers are: major.minor.micro. As far as I understood, 5 is a
major version, 5.2 is a minor version, 5.2.1 is a micro.
To sum up:
- New micro/alpha/beta/CR/whatever: just add a new
_data/orm/releases/<major.minor>/<major.minor.micro.
FinalOrAlphaOrBetaOrWhatever>.yml file like you used to. No need to
change/remove the previous ones, and in fact you shouldn't remove them:
removing files will break stuff.
- New major or minor:
- add a new _data/orm/releases/<major.minor>/series.yml file
- add a new _data/orm/releases/<major.minor>/<major.minor.0.
FinalOrAlphaOrBetaOrWhatever>.yml file.
- add a new orm/releases/<major.minor>/index.adoc file. It can be
empty except for the AsciiDoc metadata, but ideally you would put in there
a description of the minor. The content will appear in the "What's
new"
section on the series page. For example: http://hibernate.org/
search/releases/5.8/#whats-new. Obviously you'll want to keep yours
shorter, I'm just not good at summarizing ;)
Thanks,
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
On 28 September 2017 at 19:08, andrea boriero <andrea(a)hibernate.org>
wrote:
> Thanks a lot Guillaume and Yoann, great work.
>
> On 28 September 2017 at 17:41, Steve Ebersole <steve(a)hibernate.org>
> 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 drive the
> > release announcements (blog, emails, twitter, etc) from the content of a
> > series.yml.
> >
> > Thanks again for all your work on these changes. It really does look a
> lot
> > better I think.
> >
> > On Thu, Sep 28, 2017 at 11:16 AM 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
> > >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
2657
days inactive
2658
days old
8 comments
6 participants
participants (6)
-
andrea boriero -
andrea boriero -
Chris Cranford -
Guillaume Smet -
Steve Ebersole -
Yoann Rodiere