The banner is indeed driven by RSS so we would lose that. Also push driven news 
persons would not go regularly to GitHub to see if anything is new.

I forgot with who I was discussing that but we do miss a list of the releases 
and their announcements. If the GitHub thing can be automated, that would be a 
nice complement to a regular blog announcement. It would complement nicely the 
new blog infra as you could reuse the same text and script that process.

On hosting distributions on GitHub, I still have a bitter taste when GitHub 
pulled the plug on release hosting the last time around. I don’t think we 
should trust them on this one.

Emmanuel

> On 28 May 2015, at 04:47, Steve Ebersole <st...@hibernate.org> wrote:
> 
> At the moment we write release announcements using in.relation.to and then
> announce in other mediums by posting that link.  We all agree (more or
> less) that the wiki editor and rendering on there leaves much to be desired.
> 
> Brett had mentioned a long time ago about GitHub and its release
> capabilities and tonight I went back and looked at them again.  I created a
> more descriptive release announcement in GitHub then its default of just
> using the tag message for this 5.0.0.CR1 release just to see how it worked
> out.  Here are the 2 links for comparison:
> 
> * http://in.relation.to/Bloggers/HibernateORM500CR1Release
> * https://github.com/hibernate/hibernate-orm/releases/tag/5.0.0.CR1
> 
> There are a few things to notice here.  First, I think we can all agree
> that the second looks considerably better.  Also, there is a lot to be said
> for these being closely available from the source repo.
> 
> Another thing to note is that the GitHub release has the ability to attach
> random zips and tgz.  I have not taken advantage of that as I felt bad
> uploading our 62 and 97 Mb release bundles here just for a PoC.  I do have
> a task for myself post 5.0 to re-think how we build these release
> bundles[1].  But ultimately whether it makes sens to attach them here comes
> down to whether we think SF and its FRS has any advantage.  I think
> download statistics will be the only discussion point there.
> 
> Anyway, moving forward I plan to move to this approach for release
> announcements.
> 
> The only sticky point is the sourcing for the banners on hibernate.org.
> What drives that?  RSS?
> 
> Thoughts?
> 
> [1] https://hibernate.atlassian.net/browse/HHH-9828
> _______________________________________________
> 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

Reply via email to