I'm working on a Django project and I'm being asked the following question.
For exemple :
I'm creating version 1.1.0 for a new feature.
After, I create version 1.2.0 for a second new feature.
If I must created a new version for a fix about the 1.1.0 version.
What will be the number of this version ? 1.2.1 ?
1.1.1 makes more sense. But the version order will not be correct !
What is good practice ?
There are no good or bad practices, only "common sense" and logic.
In your case, if you have
fix about the 1.1.0 version
without changes incorporated in 1.2.0 when it will be 1.1.x in release
and when you forward-port from 1.1.* into 1.2.0, you'll get 1.2.x
Dates of releases are irrelevant (while you follow semver), because more than 1 supported version post-releases for full line of product is natural practice.
Related
I have encountered a (now known) bug with #testing-library/user-event version 12.8.3 and need to upgrade to a newer version. I'm wondering how high a version can I go?
We're using react-dom 16.8.5, and rather than just plugging in the latest version of testing library I was hoping to see a compatibility list somewhere. Is there such a thing? I can't seem to glean anything from npmjs.com.
We are using 0.10.3 version of react-big-calendar and facing the Timezone issue discussed here.
Unfortunately we made some custom changes to the 0.10.3 version, so we can't apply that fix(provided in that library for the latest versions) to the version we are using. How to apply the fix in the older version 0.10.3 without upgrading it to a new version?
The (0.36.0) latest version of RBC has full timezone support now, when using either the momentLocalizer or the new luxonLocalizer. Doc site isn't up to date yet, but if you run the 'examples' locally you'll find all the info.
we want to build a project A with the latest version of clarity and project needs to be used in platform B build with angular 7 and clarity version 1.3 as a library inside B. can these be achieved
In generally, this is not likely to work well. This is more due to the way that the TypeScript and Angular compiler works than Clarity, because the Angular versions used are different enough that they do not work together. You can try, but I would recommend updating your old project as it is out of support for Angular at this point.
Is there any way to use the angular 2 final version with meteor right now?, or should we wait for any updated version from meteor?
Im now using meteor 1.4.1 and I think it consist on rc4
As I see Angular2-meteor is already up to date with the release version.
Angular2-meteor repository
https://github.com/Urigo/angular2-meteor/commit/f7af9b2ae0734e2ce1b313f39c238582cc6392e2
The last commit targets release 2.0.0.
So I would say it's release-ready :)
Just learning atk4. (4.2.4, I believe. Installed through curl -sS http://agiletoolkit.org/install | sh)
How do I modify and load shared.html in atk4? I can only edit atk4/templates/shared/shared.html?
I tried copying shared.html to the following locations and edit them:
/templates/default/shared.html
/templates/default/shared/shared.html
/templates/shared/shared.html
and none seems to be loaded at all.
It should work at least from /templates/shared/shared.html.
Please try to use latest ATK4 version from master branch from GitHub https://github.com/atk4/atk4. Current fully working version is 4.2.5.
If you start to learn ATK4 or start completely new project based on ATK4 framework, then you better look into 4.3 branch in GitHub and learn and use it. There are quite a lot of things changed in 4.3 (not yet released) version so you better use them now and you'll not need to "convert" your project from 4.2.x to 4.3 later on when 4.3 will be officially released.