-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Locale supported as timezone #54
Conversation
I will test this branch in https://github.com/PuneetGopinath/activity-test now. |
@abhijoshi2k See those results in https://github.com/PuneetGopinath/activity-test/actions/runs/866856864 |
@abhijoshi2k Is there something you want to still commit in the timezone-fix branch? |
Changelog is still left |
@PuneetGopinath let us stop all the work on #53 till this pr is merged and all conflicts are resolved. |
@abhijoshi2k Why do we have to release minor version can't we release a new major version, v1.3.0 of our release has not followed semantic version already, can I update the Changelog and the draft release? |
Yes, we can go for v2.0.0 in next release |
How? |
Semver says to use a new major version when there is a breaking change. |
No, we should reset it when a new major version is released, that's why in the old format, I added the older changelogs section but you removed it!! |
@PuneetGopinath @Andre601 can we keep changelogs of old version in separate folder then? |
Yes, we can keep them, anyway they are available in the v1.3.0 tag |
This comment has been minimized.
This comment has been minimized.
The Pull request of @abhijoshi2k has been marked as Ready! It can now be reviewed and/or merged by Maintainers.
|
This comment has been minimized.
This comment has been minimized.
There's no need to get angry @Andre601 . |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Just make a backup of the old (v1) changelog now... Maybe in a |
I shall merge it after we clear everything with @Andre601 . I don't want to hurt a team member here. I shall also resolve all the conflicts. You can sleep. |
@abhijoshi2k You can get the old change log from the old changelogs section, then copy the raw content and create a new file and paste the content. |
@PuneetGopinath let's make sure this doesn't happen anymore. |
@abhijoshi2k We have breaking changes and that should release a new major version |
Make a proper archive of old changelog
I merged a |
Hello @Andre601, @PuneetGopinath and all, I just wanted to provide my two cents since my original ticket spurred this discussion and I don't want to see people upset on great working being done already. Debating can be a good thing and even healthy as long as no one takes it personal, and with versioning, there are always a lot of opinions. With that said, I will just share this, https://semver.org/. These are very clear guidelines, and with regards to Minor version, it says Keeping in mind the above, I think, at least in part, that some of the confusion is coming from releasing maybe too few breaking changes as a new version. For example, 1 breaking change causing the major version to update each time, which feels wrong as opposed to maybe 10. The discussion above seems to hover around both of these concepts. I won't say what I think is best, but I did just want to share some info in the hopes it helps work things out easier. Thanks again everyone for your time and involvement in this. |
Hello @StevenJDH , Thank you. |
@abhijoshi2k yes, things look good. And yes, I've decided to switch from main to a version number after reconsidering my approach here. Thanks again 🙏🏽 |
@StevenJDH The feature you requested is now released with v2.0.0 |
@abhijoshi2k perfect, I will upgrade today, thanks! |
Checks
I have...
Type of Pull request
This Pull request doesn't break existing configuration.
This Pull request will break existing configuration.
This Pull request will fix a (critical) bug.
This Pull request only changes documentation (README.md, CHANGELOG.md, etc.)
Description
Timezone support extended. It can now accept locale string as "continent/city"
f.e. GMT+0530 or Asia/Kolkata
Formats for all timezones can be viewed here : https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
🔴🔴 Breaking Change 🔴🔴
TIMEZONE_OFFSET
input has now changed toTIMEZONE
Closes #49