Hi, On Wed, May 27, 2015 at 09:47:29PM -0500, Steve Ebersole 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.
+100, the editor and rendering sucks. > 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. I like this approach in general and I agree there is a certain merit in having the announcements in the source repo, BUT :-) We are very close now with the migration of in.relation.to to awestruct. In fact I was hoping we could do the migration within a couple of weeks. Using the awestruct based blog, we get markdown/ascidoc for writing the blog entries and also a blog which matches it its style the current hibernate.org website. It also means we can continue our practice of announcing on the blog. The release announcements make up a considerable part of the blog content, I fear moving them to GitHub will make our blog to appear stagnant. My vote is to push this blog migration through - now! --Hardy
pgpFxipJFY3CM.pgp
Description: PGP signature
_______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
