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 :)
Related
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.
Here is maven-gpg-plugin version 3.0.0 official page: http://maven.apache.org/components/plugins-archives/maven-gpg-plugin-LATEST/download.cgi
However:
the download links not working
Maven central shows that the latest version of plugin is 1.6
Is it some fake page or what am I missing?
This was stage release, which doesn't passed testing and voting on Maven Developers List, so was canceled.
https://lists.apache.org/thread.html/r0286ef73b56cb484952489e6b5757e3b17023e73f8fa0dde7aa80bc4%40%3Cdev.maven.apache.org%3E
After testing two new issues was found:
https://issues.apache.org/jira/browse/MGPG-78
https://issues.apache.org/jira/browse/MGPG-79
There is new plugin https://www.simplify4u.org/sign-maven-plugin/ probably it will be successor of maven-gpg-plugin
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.
Alright, so I injected Ng-token-auth to my app and now an error shows up into my console:
'$http.get(...).success is not a function.
Doing some reading, Angular deprecated .success method after 1.6 version.
What can I do to make it work? Unfourtanetly I'm using Angular-Material which use 1.6 and cannot go back to a previuos version. What should I do?
After doing some research this was fix on they last commit but is not available in Bower yet. So I had to download myself from their official git site
For my yeoman+angular app, I'm trying to add angular 1.1.5 to my bower dependency list. Unfortunately, angular's github page has only provided a bower repository for 1.0.7.
One answer I've seen on another stackoverflow question is to fork angular 1.1.5 into my github account and reference it there. Is there any other way to maintain a reference to an official angular release of 1.1.5?
There is a angular-unstable bower package. https://github.com/johannestroeger/bower-angular-unstable
1.1.5 is an unstable release, so it's not likely you'll be able to use it in a scenario like this in any official capacity. You'll probably have to wait till some of the changes in this branch make it to the stable release for any kind of official repo.
However, forking GitHub is probably a good idea to temporarily allow you to use the 1.1.5 build.