- Notifications
You must be signed in to change notification settings - Fork 20
Add draft blog post for 1.4.0 release#54
Uh oh!
There was an error while loading. Please reload this page.
Conversation
thehowl commented Jan 12, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
strk commented Jan 12, 2018
I love it ! LGTM Owners: make this guy a release manager! |
appleboy left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome.
lafriks left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not merge before actual release ;)
thehowl commented Jan 12, 2018
@strk Possibly. I won't do that retroactively (hell no I'm not working through another 1500 merged PRs), but I think I could probably just copy the "Other changes" section, remove any jokes, and add the release highlights in a compacted form, while on top linking to the blog post. |
strk commented Jan 12, 2018
Are merge styles not in? |
lafriks commented Jan 12, 2018
These also would be nice to mention: |
ShalokShalom commented Jan 12, 2018
If I commit today/very soon updates on the translations, would they get included? Thanks a lot |
lafriks commented Jan 12, 2018
@ShalokShalom if you mean gitea web UI translations than yes, there is still time for that |
ShalokShalom commented Jan 12, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Fine, thanks a lot. The current translation is officially finished, while important parts of the GUI are still in English. I guess the maintainer thinks its fine to leave them untranslated since some persons are used to English terms. I for myself think that these translations could be done. People who want to have an English UI can use the English UI. I like to ask for approval before I so this job. |
lafriks commented Jan 12, 2018
@ShalokShalom what language are you talking about? :) |
ShalokShalom commented Jan 12, 2018
German |
ShalokShalom commented Jan 12, 2018
And in general - this counts for every language, so we might find a conclusion here for all of them. :) |
lafriks commented Jan 12, 2018
@ShalokShalom this is not the place to discuss that. Please use #translations channel |
bkcsoft commented Jan 12, 2018
Def. love it! 😍 I vote that @thehowl writes all our future release posts |
thehowl commented Jan 12, 2018
@lafriks Thanks, mentioned them all. Also added a list of all the contributors to the release, which reminded me of how bad I am at writing python. |
ShalokShalom commented Jan 12, 2018
That squash and merge support is awesome: Will there be a short screencast to demonstrate its usage? |
lafriks commented Jan 12, 2018
@ShalokShalom there are screenshots in PR, otherwise it's quite close to how it looks and works in github |
tboerger commented Jan 12, 2018
Nice post, but the thanks list is not really correct :) |
lafriks commented Jan 12, 2018
@ShalokShalom something must be wrong with your script, even as two my PR are featured, I'm not in contributors list :) |
ShalokShalom commented Jan 12, 2018
Its not my script ;) |
thehowl commented Jan 12, 2018
@lafriks There was an issue with the script; it only really fetched from the GitHub API open pull requests (because apparently, creating |
ShalokShalom left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome ^-^
bkcsoft left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few suggestions. If you don't have time just 👍 and I'll make them myself :)
content/post/release-of-1.4.0.md Outdated
|  | ||
| Starting from version 1.4.0, Gitea's web interface is finally responsive; this means it can be properly used from your phone without having to pinch everywhere to see what is on the screen! There may be some places where the interface is still not completely responsive, in which case we ask you kindly to [file an issue](https://github.com/go-gitea/gitea/issues) if there isn't one already, posting screenshots of what does not work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"finally responsive" suggests that we'll keep it a priority to make sure it stays taht way. AFAIK we don't have any tests that checks the frontend right? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we don't really have those. (If someone is willing to do them, I'll be glad. I can bear writing unit tests for Go, definitely not writing tests for the frontend). So what do you suggest?
ShalokShalomJan 25, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might prefer property testing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thehowl I'd suggest something like "Starting from version 1.4.0, we've reworked some of the interface to allow for a more responsive design" maybe? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With some examples?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ShalokShalom examples would be great but not necessarily
content/post/release-of-1.4.0.md Outdated
|  | ||
| Yes. Yes! YES!!! Gitea now has reactions on pull requests and issues. Now hopefully your collaborators will shut up with their "+1" comments on the issue and will instead just press the 👍 button. Oh yeah 😎. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe not telling collaborators to "shut up" 😂 How about Maybe now your inbox will not be filled with "+1" emails instead. Still tounge-in-cheek, while not offending your collaborators 😉
content/post/release-of-1.4.0.md Outdated
|  | ||
| Did you know that Gitea has, like GitHub, support for checkboxes in markdown? If you write a bulletpoint in the following format: `- [ ]` you will get a nice HTML textbox. And does this have to do with checkboxes? Everything, of course! The issue list will now show the percentage of checked items in the top issue post. So you always know how far you've gotten on the roadmap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"does this" => "what does this" 🙂
content/post/release-of-1.4.0.md Outdated
|  | ||
| Making a long commit? Now you can view the entire contents of it without changing the page; you will only need to press on the ellipsis button, similar to what you can see on GitHub and GitLab. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making a long commit sounds like you put a lot of changes in it. Maybe Did someone write an entire essay in the commit message? 😄
| # Other changes | ||
| - **BREAKING:** if you used `GOGS_WORK_DIR` to change the working directory of Gitea, that won't work anymore - you'll need to use `GITEA_WORK_DIR`. ([#2946](https://github.com/go-gitea/gitea/pull/2946)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I very much think we should have all breaking changes at the top. Otherwise people will miss them (who reads changelogs anyway?
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wdym by at the top? at the top of the article? or is there some sarcasm I didn't catch? :P
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the top of the article.
content/post/release-of-1.4.0.md Outdated
| - If you're a [Dingtalk](https://www.dingtalk.com/en) user, you'll be happy to know webhooks now support it starting from 1.4.0. Hooray! ([#2777](https://github.com/go-gitea/gitea/pull/2777)) | ||
| - As a reminder, we currently support webhooks for Slack, Discord and Gitea's own format, as well as a version for Gogs, to keep backwards compatibility. Also, Gitea and Gogs are mostly compatible with GitHub's webhooks! | ||
| - Git LFS aficionados: we added support for the [File Locking API](https://github.com/git-lfs/git-lfs/blob/master/docs/api/locking.md). ([#2938](https://github.com/go-gitea/gitea/pull/2938)) | ||
| - Parlez-vous français? The Gitea docs now features [French](https://docs.gitea.io/fr-fr/). Keep in mind that the only language that is guaranteed to be kept up-to-date on the documentation is English; all other languages may have information that is inaccurate, so please stick to english if you want to make sure everything works in the latest gitea version. ([#3030](https://github.com/go-gitea/gitea/pull/3030)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"now also in [French]" ?
thehowl commented Jan 30, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
@bkcsoft can you address my questions? I've finished it up - it's now ready for the final reviews. I'd say we wait this to be merged after the release candidates. |
thehowl commented Feb 16, 2018
@bkcsoft sorry for the absence - addressed the issue |
bugreport0 commented Mar 3, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
@thehowl asked me if I could take a look. It's great work. The tone was a bit over-excited so I tried to focus more on the features, which are impressive as is! Here's my PR: https://github.com/thehowl/blog-1/pull/1 |
ShalokShalom commented Mar 3, 2018
The over excited bits and pieces were the most exciting parts on this release announcement to me and others ;) |
1 similar comment
ShalokShalom commented Mar 3, 2018
The over excited bits and pieces were the most exciting parts on this release announcement to me and others ;) |
bugreport0 commented Mar 4, 2018
@ShalokShalom I tried to keep the tone professional and consistent with the style I use for the English translation. I think it's perfect and awesome for you and all others to be over-excited and proud about these features as developers and contributors to Gitea. As I wrote earlier, it's an amazing development tool! But I think (just my opinion) that projecting a clean, professional image outwards lowers the barrier of entry to people who don't know Gitea or its internals. Don't show people where we've been, show them where we're at right now. Also, I just randomly dropped into Gitea and started editing and writing stuff. Everyone is free to ignore me and my suggestions. I don't have any claim to power or authority! |
lafriks commented Mar 25, 2018
Make LG-TM work |
Still a draft, and with many parts left to do still. What do you think?
Rendered markdown can be seen here: https://github.com/thehowl/blog-1/blob/release-1.4.0/content/post/release-of-1.4.0.md (without images, though)
cc/ @lafriks, as we were discussing this yesterday.