New versioning scheme #284
kennethlove
started this conversation in
Ideas
Replies: 2 comments
-
just release django-braces 2.0 O:) |
Beta Was this translation helpful? Give feedback.
0 replies
-
There have been no breaking API changes. There's no reason for a 2.0.
…On Mon, Nov 15, 2021, 18:51 Asif Saif Uddin ***@***.***> wrote:
just release django-braces 2.0 O:)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#284 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAC5BC2JCZ7G3D3XMGJ63TUMHBJJANCNFSM5IC2NTZA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
django-braces
is extremely mature and stable. All of the issues it has are related to either explicit version support (Django's usually) or new features.What if, instead of
django-braces-1.15.0
, we haddjango-braces-2.2-3.2-1
to show it was the first release1
, and for Django versions2.2
and3.2
?I also wouldn't mind a date-based versioning, like I use with
django-shapeshifter
.django-braces-21.11.15
for example.Like it? Hate it? Have another versioning scheme that would work better?
Want me to shut up and leave it as it is?
Beta Was this translation helpful? Give feedback.
All reactions