-
Notifications
You must be signed in to change notification settings - Fork 29
Make a post of every release? #31
Comments
Sounds good! Should we include the changelog or not? |
I can offer to start creating a small blog post for every release, similar like we tweet about every release. It should not include too much text though, should it? |
Sounds good! |
I think we decided to have a small release announcement for every release now, we started with 0.6.8 (here: https://solidity.ethereum.org/2020/05/14/solidity-068-release-announcement/). I can be in charge of putting it together / reminding us that we want to write one each time. |
This issue was also suggesting that we could create a script pulling from github release page and pushing it to the blog. Should we keep it open for that for a tiny bit longer? |
I don't think it's a good idea to "automate" release announcements like that since we might want to outline things more in the blog post, e.g. in the last one we outlined the three bugs in more detail. Or what are you suggesting? |
The release page on github was always written like a blog post, highlighting the important parts. I know recently highlighting on the blog became even more emphasized, but still, the old release notes were trying to fill in the same gap. (They are not just a copy paste from the CHANGELOG file.) The suggestion here is to have a script which pulls the release page and creates a blog entry for each for the past releases. I wasn't suggesting to use it for any new release, but I guess it could be. Also didn't suggest to run it in the background, but rather someone had to run it once :) |
Here's the API to download release notes: https://developer.github.com/v3/repos/releases/ For example https://api.github.com/repos/ethereum/solidity/releases/tags/v0.6.7 contains the |
Here's my script:
|
Looks good from what I can tell, @chriseth can you also have a look so that we can move forward? :) |
looks good |
Minor comment, there are two spaces between |
That was fixed locally, just forgot to push here (also added some other things, iirc). |
I think if we were to do this, it should contain the short intro from the release page (and perhaps the changelog) and the link to the release. But I wouldn't copy paste the entire release page with all the different links.
Any opinions?
Also not suggesting we should do this retroactively for every release, but we may as well if it can be automated. Probably there is a github API to download the release text.
The text was updated successfully, but these errors were encountered: