Re: [hibernate-dev] New layout for in.relation.to

[Steve Ebersole]

+1  Great job (again)

On Fri, Sep 29, 2017 at 3:36 PM Chris Cranford  wrote:

> Was curious if we would carry the new style to in.relation.to.
> It looks superb.
>
> Chris
>
> On 09/29/2017 01:57 PM, Guillaume Smet wrote:
> > Hi!
> >
> > I converted in.relation.to to the new layout and pushed it to
> > http://staging.in.relation.to/ .
> >
> > Please take a look at it so that we can make progress quickly.
> >
> > Note that I still have some work to do on the mobile side. Will do once
> the
> > dust has settled and we agree on the layout.
> >
> > The home page:
> > http://staging.in.relation.to/
> >
> > The blog post page: the idea here is to just present the content in a
> very
> > minimal way:
> >
> http://staging.in.relation.to/2017/09/25/hibernate-community-newsletter-2017-18/
> >
> > While it's not validated, please be careful when cherry-picking your new
> > blog post to production, don't merge my commits by mistake!
> >
> > Note that it doesn't change anything to the blog posts so business can
> > continue as usual and you can safely cherry-pick your blog post from
> > staging to production.
> >
> > Looking forward to your feedback.
> >
>
> ___
> 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

Re: [hibernate-dev] New layout for in.relation.to

[Chris Cranford]

Was curious if we would carry the new style to in.relation.to. 
It looks superb.

Chris

On 09/29/2017 01:57 PM, Guillaume Smet wrote:
> Hi!
>
> I converted in.relation.to to the new layout and pushed it to
> http://staging.in.relation.to/ .
>
> Please take a look at it so that we can make progress quickly.
>
> Note that I still have some work to do on the mobile side. Will do once the
> dust has settled and we agree on the layout.
>
> The home page:
> http://staging.in.relation.to/
>
> The blog post page: the idea here is to just present the content in a very
> minimal way:
> http://staging.in.relation.to/2017/09/25/hibernate-community-newsletter-2017-18/
>
> While it's not validated, please be careful when cherry-picking your new
> blog post to production, don't merge my commits by mistake!
>
> Note that it doesn't change anything to the blog posts so business can
> continue as usual and you can safely cherry-pick your blog post from
> staging to production.
>
> Looking forward to your feedback.
>

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] New layout for in.relation.to

[Guillaume Smet]

Hi!

I converted in.relation.to to the new layout and pushed it to
http://staging.in.relation.to/ .

Please take a look at it so that we can make progress quickly.

Note that I still have some work to do on the mobile side. Will do once the
dust has settled and we agree on the layout.

The home page:
http://staging.in.relation.to/

The blog post page: the idea here is to just present the content in a very
minimal way:
http://staging.in.relation.to/2017/09/25/hibernate-community-newsletter-2017-18/

While it's not validated, please be careful when cherry-picking your new
blog post to production, don't merge my commits by mistake!

Note that it doesn't change anything to the blog posts so business can
continue as usual and you can safely cherry-pick your blog post from
staging to production.

Looking forward to your feedback.

-- 
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] ORM release process

[andrea boriero]

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  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//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//series.yml file
>   - add a new _data/orm/releases//   FinalOrAlphaOrBetaOrWhatever>.yml file.
>   - add a new orm/releases//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
> yo...@hibernate.org
>
> On 28 September 2017 at 19:08, andrea boriero 
> wrote:
>
>> 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 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 
>> > 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//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@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 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

Re: [hibernate-dev] ORM release process

[Yoann Rodiere]

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//.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//series.yml file
  - add a new
  
_data/orm/releases//.yml
  file.
  - add a new orm/releases//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
yo...@hibernate.org

On 28 September 2017 at 19:08, andrea boriero  wrote:

> 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 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 
> > 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//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@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 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