-
Notifications
You must be signed in to change notification settings - Fork 2
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
Backwards compatability #31
Comments
V2.01 is a very stable release and is still available for use ehich does not require all the modifications to upgrade. Many users stay with V2.01. It is still offered at nPose HQ inworld and on Github.Upgrading to V3.10 is possibly something to consider for new builds or if any of the new features would be useful. In defense of the upgrades, they were needed to allow nPose to grow. The features that V3.10 offer could not happen without making these changes. V3.10 has been released for over 2 years and is also a very stable version.Pick what works for you.Howard
-------- Original message --------From: WhiteFire <[email protected]> Date: 6/18/19 4:31 PM (GMT-08:00) To: nPoseTeam/nPose-V3 <[email protected]> Cc: Subscribed <[email protected]> Subject: [nPoseTeam/nPose-V3] Backwards compatability (#31) Can we have a long term stable version, or should I just ignore nPose 3 and fork myself my own nPose 2? Removing core functionality (DEFAULT for example) is not something I want to deal with running my store.
I went through this with Wendy's Open Collar where the API changed constantly, not interested in doing it again.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#31?email_source=notifications\u0026email_token=AA3SNIWK77HNU75HMXBTQJTP3FV6PA5CNFSM4HZEUTSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2ISB7Q",
"url": "#31?email_source=notifications\u0026email_token=AA3SNIWK77HNU75HMXBTQJTP3FV6PA5CNFSM4HZEUTSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2ISB7Q",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Hi,
I hope that are good reasons ... My point of view: V3.10: will be likely the the last version in the V3 era and I don't know of any major issues. If you start a new project I would be using this. API changes because of 1+2+3+4+5 in the above list V4: The next release (hopefully this year) will be V4 and it implements some new features. There will also some (very?) minor "API" changes (considerably less as between V2 and V3). API changes because of 2+3+5 in the above list.
Well it isn't removed it just changed ... (I currently don't know of anythig that can be made in V2 but not in V3) PS: If I speak of bad design descission ... I don't want to say that anyone did a bad job ... I mean we all (this includes me) are making descissions and some of them are good and some of them are not as good and we are not able to see a bad descission in the moment we make the descission but we see them later. |
Can we have a long term stable version, or should I just ignore nPose 3 and fork myself my own nPose 2? Removing core functionality (DEFAULT for example) is not something I want to deal with running my store.
I went through this with Wendy's Open Collar where the API changed constantly, not interested in doing it again.
The text was updated successfully, but these errors were encountered: