Add draft blog post for 1.4.0 release #54

thehowl · 2018-01-12T16:00:25Z

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.

strk · 2018-01-12T16:34:49Z

I love it !
Ideally also the CHANGELOG.md would only contain notable changes, will you also help with that ?

LGTM

Owners: make this guy a release manager!

appleboy

Awesome.

lafriks

Do not merge before actual release ;)

thehowl · 2018-01-12T16:50:50Z

@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 · 2018-01-12T16:53:29Z

Are merge styles not in?

lafriks · 2018-01-12T16:57:41Z

These also would be nice to mention:
go-gitea/gitea#3225 (deploy keys with write support)
go-gitea/gitea#3188 (PR squash&merge, rebase&merge support)
go-gitea/gitea#2938 (LFS locking support)

ShalokShalom · 2018-01-12T17:04:19Z

If I commit today/very soon updates on the translations, would they get included?

Thanks a lot

lafriks · 2018-01-12T17:06:06Z

@ShalokShalom if you mean gitea web UI translations than yes, there is still time for that

ShalokShalom · 2018-01-12T17:11:41Z

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.
This 'one part in English and one part in another language' thing confuses me and it undermines the sense of a translation.

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 · 2018-01-12T17:14:29Z

@ShalokShalom what language are you talking about? :)

ShalokShalom · 2018-01-12T17:15:18Z

German

ShalokShalom · 2018-01-12T17:15:41Z

And in general - this counts for every language, so we might find a conclusion here for all of them. :)

lafriks · 2018-01-12T17:17:33Z

@ShalokShalom this is not the place to discuss that. Please use #translations channel

bkcsoft · 2018-01-12T17:37:23Z

Def. love it! 😍 I vote that @thehowl writes all our future release posts

thehowl · 2018-01-12T18:13:00Z

@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 · 2018-01-12T18:39:15Z

That squash and merge support is awesome: Will there be a short screencast to demonstrate its usage?

lafriks · 2018-01-12T19:12:00Z

@ShalokShalom there are screenshots in PR, otherwise it's quite close to how it looks and works in github

tboerger · 2018-01-12T19:13:49Z

Nice post, but the thanks list is not really correct :)

lafriks · 2018-01-12T19:21:15Z

@ShalokShalom something must be wrong with your script, even as two my PR are featured, I'm not in contributors list :)

ShalokShalom · 2018-01-12T20:00:51Z

Its not my script ;)

thehowl · 2018-01-12T20:06:06Z

@lafriks There was an issue with the script; it only really fetched from the GitHub API open pull requests (because apparently, creating status=merged and putting the milestone parameter also for the pull request API was too hard for them 🙄). It's fixed now :)

ShalokShalom

Awesome ^-^

bkcsoft

Just a few suggestions. If you don't have time just 👍 and I'll make them myself :)

bkcsoft · 2018-01-24T22:25:05Z

content/post/release-of-1.4.0.md

+
+![Responsive UI screenshot](/demos/2750/3.png)
+
+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.


"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? 🤔

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?

You might prefer property testing.

@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? 🤔

With some examples?

@ShalokShalom examples would be great but not necessarily

bkcsoft · 2018-01-24T22:26:28Z

content/post/release-of-1.4.0.md

+
+![Screenshot of Reactions](/demos/2856/2.png)
+
+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 😎.


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 😉

bkcsoft · 2018-01-24T22:29:02Z

content/post/release-of-1.4.0.md

+
+![Progress bar demo](/demos/3171/1.png)
+
+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.


"does this" => "what does this" 🙂

bkcsoft · 2018-01-24T22:31:08Z

content/post/release-of-1.4.0.md

+
+![Commit body expansion demo](/demos/2980/1.gif)
+
+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.


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? 😄

bkcsoft · 2018-01-24T22:33:27Z

content/post/release-of-1.4.0.md

+
+# 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))


I very much think we should have all breaking changes at the top. Otherwise people will miss them (who reads changelogs anyway? )

wdym by at the top? at the top of the article? or is there some sarcasm I didn't catch? :P

At the top of the article.

bkcsoft · 2018-01-24T22:35:46Z

content/post/release-of-1.4.0.md

+- 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))


"now also in [French]" ?

thehowl · 2018-01-30T18:05:24Z

@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 · 2018-02-16T21:31:27Z

@bkcsoft sorry for the absence - addressed the issue

bugreport0 · 2018-03-03T12:45:10Z

@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 · 2018-03-03T19:54:58Z

The over excited bits and pieces were the most exciting parts on this release announcement to me and others ;)

ShalokShalom · 2018-03-03T19:55:00Z

The over excited bits and pieces were the most exciting parts on this release announcement to me and others ;)

bugreport0 · 2018-03-04T12:27:29Z

@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 · 2018-03-25T10:08:41Z

Make LG-TM work

thehowl added 3 commits January 12, 2018 16:57

Add draft blog post for 1.4.0 release

be5fae8

woops, forgot to commit the actual post...

0787f67

Forgot one new important feature

44b817f

tboerger added the lgtm/need 1 label Jan 12, 2018

appleboy approved these changes Jan 12, 2018

View reviewed changes

tboerger added lgtm/done and removed lgtm/need 1 labels Jan 12, 2018

lafriks added the status/wip label Jan 12, 2018

lafriks suggested changes Jan 12, 2018

View reviewed changes

MORE highlights, add list of contributors, reorder changes

04c63a9

Update thanklist

bfc96f9

thehowl added 3 commits January 12, 2018 21:08

theme PR has been merged; hack no longer needed

1e0373a

add help out section

31af552

add screenshot for 3097

a9d3c5f

appleboy changed the title ~~Add draft blog post for 1.4.0 release~~ [WIP] Add draft blog post for 1.4.0 release Jan 13, 2018

ShalokShalom reviewed Jan 13, 2018

View reviewed changes

thehowl mentioned this pull request Jan 19, 2018

Add 1.4 release section on CHANGELOG.md go-gitea/gitea#3400

Closed

bkcsoft reviewed Jan 24, 2018

View reviewed changes

thehowl added 3 commits January 25, 2018 12:58

Apply suggested edits by @bkcsoft

951b0b3

Finish the Customize Gitea section

3cbdcb7

move expected release date to 05/02

3275467

thehowl changed the title ~~[WIP] Add draft blog post for 1.4.0 release~~ Add draft blog post for 1.4.0 release Jan 30, 2018

sapk approved these changes Feb 5, 2018

View reviewed changes

reworked interface instead of finally responsive

dde043f

thehowl mentioned this pull request Mar 2, 2018

Modal dialogs and consistency go-gitea/gitea#3605

Closed

bugreport0 added 2 commits March 3, 2018 19:56

Reword a bit.

daafc2f

Applying suggestions.

1ab26c1

Some more tweaking

0f35655

lafriks approved these changes Mar 25, 2018

View reviewed changes

Fix release date and add download link

92eb141

lafriks removed the status/wip label Mar 25, 2018

lafriks merged commit 68830a8 into go-gitea:master Mar 25, 2018


		![Responsive UI screenshot](/demos/2750/3.png)

		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.


		![Screenshot of Reactions](/demos/2856/2.png)

		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 😎.


		![Progress bar demo](/demos/3171/1.png)

		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.


		![Commit body expansion demo](/demos/2980/1.gif)

		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.


		# 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))

Add draft blog post for 1.4.0 release #54

Add draft blog post for 1.4.0 release #54

Conversation

thehowl commented Jan 12, 2018 • edited Loading

strk commented Jan 12, 2018

appleboy left a comment

Choose a reason for hiding this comment

lafriks left a comment

Choose a reason for hiding this comment

thehowl commented Jan 12, 2018

strk commented Jan 12, 2018

lafriks commented Jan 12, 2018

ShalokShalom commented Jan 12, 2018

lafriks commented Jan 12, 2018

ShalokShalom commented Jan 12, 2018 • edited Loading

lafriks commented Jan 12, 2018

ShalokShalom commented Jan 12, 2018

ShalokShalom commented Jan 12, 2018

lafriks commented Jan 12, 2018

bkcsoft commented Jan 12, 2018

thehowl commented Jan 12, 2018

ShalokShalom commented Jan 12, 2018

lafriks commented Jan 12, 2018

tboerger commented Jan 12, 2018

lafriks commented Jan 12, 2018

ShalokShalom commented Jan 12, 2018

thehowl commented Jan 12, 2018

ShalokShalom left a comment

Choose a reason for hiding this comment

bkcsoft left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ShalokShalom Jan 25, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

thehowl commented Jan 30, 2018 • edited Loading

thehowl commented Feb 16, 2018

bugreport0 commented Mar 3, 2018 • edited Loading

ShalokShalom commented Mar 3, 2018

ShalokShalom commented Mar 3, 2018

bugreport0 commented Mar 4, 2018

lafriks commented Mar 25, 2018

thehowl commented Jan 12, 2018 •

edited

Loading

ShalokShalom commented Jan 12, 2018 •

edited

Loading

ShalokShalom Jan 25, 2018 •

edited

Loading

thehowl commented Jan 30, 2018 •

edited

Loading

bugreport0 commented Mar 3, 2018 •

edited

Loading