Proposal: Use ISO-8601 in CHANGELOG #80

New Issue

Closed

opened 2021-06-12 23:34:05 +02:00 by deejoe · 12 comments

deejoe commented

2021-06-12 23:34:05 +02:00

As of #11 a full 10 characters are being used to represent the date, so in the next and subsequent entries why not just use ISO-8601 format: YYYY-MM-DD?

As of #11 a full 10 characters are being used to represent the date, so in the next and subsequent entries why not just use ISO-8601 format: YYYY-MM-DD?

deejoe commented

2021-06-12 23:34:38 +02:00

Author

Sorry, that's not the Gitea # 11 but CHANGELOG entry # 11.

Sorry, that's not the Gitea # 11 but CHANGELOG entry # 11.

muppeth commented

2021-07-02 00:47:19 +02:00

Owner

Not sure to which issue are you trying to link. you mean that we use DD-MM-YYYY in our changelog repo?

Personally I don't why why we should use the reverse one. dd-mm-yyyy is more clear imo.

Not sure to which issue are you trying to link. you mean that we use DD-MM-YYYY in our changelog repo? Personally I don't why why we should use the reverse one. dd-mm-yyyy is more clear imo.

deejoe commented

2021-07-23 02:57:21 +02:00

Author

because it's a standard, and because it sorts?

because it's a standard, and because it sorts?

muppeth commented

2021-07-30 09:39:39 +02:00

Owner

@meaz @antilopa @fede @avg_joe ^^? I personally, although used to DD-MM-YYYY format, I don't care much as long as its not MM-DD-YYYY

@meaz @antilopa @fede @avg_joe ^^? I personally, although used to DD-MM-YYYY format, I don't care much as long as its not MM-DD-YYYY

meaz commented

2021-07-30 10:03:04 +02:00

Owner

Both are fine with me...

Both are fine with me...

antilopa commented

2021-08-01 11:44:38 +02:00

Owner

I don't mind the change. I understand the convenience in sorting items better.

I don't mind the change. I understand the convenience in sorting items better.

fede commented

2021-08-01 21:46:52 +02:00

Owner

Although I do understand the use of YYYY-MM-DD in a changelog, I personally use the DD-MM-YYYY format (in South America we don't use other date format). And as Muppeth, I don't mind changing the order of the year but not to MM-DD-YY.

Although I do understand the use of YYYY-MM-DD in a changelog, I personally use the DD-MM-YYYY format (in South America we don't use other date format). And as Muppeth, I don't mind changing the order of the year but not to MM-DD-YY.

meaz commented

2022-03-04 16:49:31 +01:00

Owner

So what is our final decision on this? Do we go for YYYY-MM-DD or do we stay with DD-MM-YYYY in the changelog repo?

So what is our final decision on this? Do we go for YYYY-MM-DD or do we stay with DD-MM-YYYY in the changelog repo?

meaz self-assigned this 2022-03-04 16:49:45 +01:00

fede commented

2022-03-04 16:55:20 +01:00

Owner

I go for YYYY-MM-DD

I go for YYYY-MM-DD

muppeth commented

2022-03-04 23:50:20 +01:00

Owner

ok. who's gonna fix it then?

ok. who's gonna fix it then?

meaz commented

2022-03-05 08:06:15 +01:00

Owner

I've assigned it to me so will do it.

I've assigned it to me so will do it.

meaz referenced this issue from Disroot/CHANGELOG

2022-03-12 19:29:32 +01:00

Use ISO-8601 in CHANGELOG fixing #80 #220

meaz commented

2022-03-12 19:29:44 +01:00

Owner

Fixed by Disroot/CHANGELOG#220

Fixed by https://git.disroot.org/Disroot/CHANGELOG/pulls/220

meaz closed this issue

2022-03-12 19:29:44 +01:00

meaz referenced this issue from a commit

2022-03-15 15:48:00 +01:00

Use ISO-8601 in CHANGELOG fixing #80 (#220)

Sign in to join this conversation.

No Label

Feature request

🤔️ Investigate

spam-protection

No Milestone

No project

No Assignees

5 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: Disroot/Disroot-Project#80

No description provided.