Gitea 1.8.0 #4

New Issue

Closed

opened 2019-04-21 01:39:52 +00:00 by luna · 4 comments

luna commented

2019-04-21 01:39:52 +00:00

Owner

beep! released 5 minutes ago at the time of writing.

I counted some 20 commits between -rc3 and proper 1.8.0, so that might be important even though our upstream update was some days ago.

https://github.com/go-gitea/gitea/releases/tag/v1.8.0

I'd also like an answer on "can I keep writing those upstream updates as issues here or not?"

beep! released 5 minutes ago at the time of writing. I counted some 20 commits between -rc3 and proper 1.8.0, so that might be important even though our upstream update was some days ago. https://github.com/go-gitea/gitea/releases/tag/v1.8.0 I'd also like an answer on "can I keep writing those upstream updates as issues here or not?"

a commented

2019-04-25 17:31:27 +00:00

Owner

I’d also like an answer on “can I keep writing those upstream updates as issues here or not?”

I also get emailed about them, but sure.

> I’d also like an answer on “can I keep writing those upstream updates as issues here or not?” I also get emailed about them, but sure.

a commented

2019-04-25 17:34:12 +00:00

Owner

Updated.

Updated.

a closed this issue

2019-04-25 17:34:14 +00:00

luna commented

2019-04-25 17:35:32 +00:00

Author

Owner

I also get emailed about them, but sure.

Yeah but we were on 1.6 while 1.7 was already there as well, so I didn't know, anyways.

> I also get emailed about them, but sure. Yeah but we were on 1.6 while 1.7 was already there as well, so I didn't know, anyways.

a commented

2019-04-25 17:37:24 +00:00

Owner

Yeah I only subscribed after #3

Yeah I only subscribed after #3

Sign in to join this conversation.

No Label

No Milestone

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: gitdab/gitdab#4

No description provided.