On Thu, May 28, 2015 at 8:07 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>
The banner is indeed driven by RSS
I have not seen any RSS capability from the GitHub Release "system".
so we would lose that. Also push driven news persons would not go
regularly to GitHub to see if anything is new.
That depends. What we do today is to write the announcement in one place
and then announce in multiple places pointing to that one announcement.
That is still an option. Just I am advocating writing the announcement in
GitHub rather than in Seam-wiki-text-whatnot. We could very well write a
"Weblog Entry" (lol) on in.relation.to that links to the GitHub release.
The "next gen blog" has been "coming" for years. That's not a dig
anyone, just a simple point that I'd rather plan based on options I have
today rather than options that I will have at some indeterminate date.
Unless you can tell me definitively when the new blog system is going to be
I forgot with who I was discussing that but we do miss a list of the
releases and their announcements.
Yes, and no. It depends on consistent tagging which I personally use for
ORM releases, but we have never really all agreed to across all projects.
But even then, the list is fugly :)
If the GitHub thing can be automated, that would be a nice complement
regular blog announcement. It would complement nicely the new blog infra as
you could reuse the same text and script that process.
I am actually contemplating *not* automating it. It actually happens
automatically already. By default it simply grabs the message you applied
t the tag as the description. Essentially what happens is that a release
is automatically created for each tag. You can edit that afterwards. In
fact this is exactly what I did. Compare that to a default release.
You could technically leverage the fact that it picks up the tag message to
provide the markdown. But given that for ORM we manually tag anyway, it
really just makes sense to do that step through the GitHub release UI whcih
will also create the tag if you want.
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.
I am not tied to it. We have other options for that anyway. But having
one complete "picture" of the release is a very very very nice-to-have.
The release ymls in hibernate.org
strive to be that, but just arent.