gitea/blog
44
20
Fork 31
Code Issues 10 Pull Requests 1 Actions Activity

Add blog post for 1.5.0 #64

Closed
techknowlogick wants to merge 3 commits from unknown repository into main
pull from: unknown repository
merge into: gitea:main
Conversation 12 Commits 3 Files Changed 1 +81
techknowlogick commented 2018-07-04 02:30:50 +00:00
Owner
Copy Link

Date will need to be changed to the correct release date.

Date will need to be changed to the correct release date.
sondr3 commented 2018-07-04 11:30:50 +00:00 (Migrated from github.com)
Copy Link

Are you gonna expand on the features in this release akin to the blog post for 1.4? It was a big plus in my book to delve a bit deeper into the new and big features that came with that release instead of just listing the changelog and a small paragraph about this release.

Are you gonna expand on the features in this release akin to the blog post for 1.4? It was a big plus in my book to delve a bit deeper into the new and big features that came with that release instead of just listing the changelog and a small paragraph about this release.
lunny commented 2018-07-04 11:46:54 +00:00
Copy Link

I would like you include a public gpg key here for verify the downloads. I have uploaded that on #maintainers channel.

I would like you include a public gpg key here for verify the downloads. I have uploaded that on #maintainers channel.
techknowlogick commented 2018-07-04 14:41:58 +00:00
Author
Owner
Copy Link

@lunny Good Idea. I think we should put that on gitea.io website and link to it from this blog post. I've added a line about GPG updates.

@sondr3 good idea. I've just added some text to the blog post which expands on changes.

@lunny Good Idea. I think we should put that on gitea.io website and link to it from this blog post. I've added a line about GPG updates. @sondr3 good idea. I've just added some text to the blog post which expands on changes.
lafriks commented 2018-07-04 21:41:12 +00:00 (Migrated from github.com)
Copy Link

It would be nice to add notice that we will be dropping integrated TiDB support in next release

It would be nice to add notice that we will be dropping integrated TiDB support in next release
techknowlogick commented 2018-07-04 21:42:10 +00:00
Author
Owner
Copy Link

@lafriks that is in the blog post

@lafriks that is in the blog post
lafriks commented 2018-07-04 21:45:50 +00:00 (Migrated from github.com)
Copy Link

Oh, sorry you are right, missed that :)

Oh, sorry you are right, missed that :)
lafriks commented 2018-07-05 08:00:19 +00:00 (Migrated from github.com)
Copy Link

@thehowl could you add more detailed info with screenshots etc about new features?

@thehowl could you add more detailed info with screenshots etc about new features?
thehowl commented 2018-07-06 07:54:12 +00:00 (Migrated from github.com)
Copy Link

Hey - I'm quite overwhelmed with work as of lately and I kind of lost interest in Gitea (I should get around to ask to be moved to advisors :P) but I guess I can try to make time to sum up the changes and make a changelog like the previous one. I'll try to do it over the weekend.

Hey - I'm quite overwhelmed with work as of lately and I kind of lost interest in Gitea (I should get around to ask to be moved to advisors :P) but I guess I can try to make time to sum up the changes and make a changelog like the previous one. I'll try to do it over the weekend.
lunny commented 2018-07-15 06:59:47 +00:00
Copy Link

@thehowl do you have time to do that?

@thehowl do you have time to do that?
thehowl commented 2018-07-15 17:56:10 +00:00 (Migrated from github.com)
Copy Link

I'll get to it now

I'll get to it now
techknowlogick commented 2018-07-15 20:00:24 +00:00
Author
Owner
Copy Link

@thehowl I gave you push access to my repo. Feel free to make changes directly to this PR.

@thehowl I gave you push access to my repo. Feel free to make changes directly to this PR.
techknowlogick commented 2018-07-15 23:08:56 +00:00
Author
Owner
Copy Link

Closing as #72 exists now.

Closing as #72 exists now.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
in progress

   
kind/bug

   
kind/deployment

   
kind/docs

   
kind/enhancement

   
kind/feature

   
kind/lint

   
kind/proposal

   
kind/question

   
kind/security

   
kind/testing

   
kind/translation

   
kind/ui

   
lgtm/done

   
lgtm/need 1

   
lgtm/need 2

   
priority/critical

   
priority/low

   
priority/maybe

   
priority/medium

   
reviewed/duplicate

   
reviewed/invalid

   
reviewed/wontfix

   
status/blocked

   
status/needs-feedback

   
status/wip
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/blog#64
No description provided.
Delete Branch "unknown repository"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?