Switch to ArdorForum

@tosh
Im not seeing much the overall goal of your post, in the end, the devs agree to review their release managment practice.
Can you be more specific?
I'm just trying to understand really.

Yes, I am not ok with the decision not to roll back the API. And I see two parties loosing if they do.

The developers loose a lot of work (either with implementing changes instead of continuing to work on future products. Or with old scripts/libraries not working anymore).
The Nxt API looses a lot of developers.

Quote from: https://drive.google.com/file/d/0B4OEA-peIYHXd3JOTUY4VndQLW8/view?usp=sharing

Jean-Luc: the time spent discussing the "incompatible" changes in 1.6.2 already exceeds the time it would have taken to fix supernet and go on

From what I understood the change could have been done be either party in 1 hour, so it's annoying to see a lot of value destroyed because of a trial point.

Couldn't the forum link at least be kept to 1.5? There might be other API users who get annoyed enough to stop using Nxt. Even if they would do it later anyway, but this would maximize the time the official version has a stable API.

Ja, I don't know how long it would take but days of crying and bawling around is not very productive and more harmful the the price/community in my opinion.

Quote from: Tosch110 on November 07, 2015, 11:57:19 pm

Yes, I am not ok with the decision not to roll back the API.

NRS devs are destroying NXT platform. You can check NXT price for last year, it shows everything.

There are two ways for us:
1. not to update from 1.5.15 and start developing our own Core.
2. to quit and stop working with NXT at all.

There are way more solutions that came up already. Even if it would be unusual. For example:
1. Return the old API (with changing default output) and say "we have been warned" and delay these updates to 1.7 (when there needs to be major changes anyway)
2. Make 1.6.2 experimental again and this way recommend people to use 1.5.15 instead. Giving Software the time to upgrade
3. Create 1.6.3 where the default API is as before and delay changes until 1.6.4 which will be at a certain date.

I could continue this list. But it does not seem that core devs are open to these discussions.

Quote from: Tosch110 on November 07, 2015, 11:57:19 pm

Yes, I am not ok with the decision not to roll back the API.

NRS devs are destroying NXT platform. You can check NXT price for last year, it shows everything.

There are two ways for us:
1. not to update from 1.5.15 and start developing our own Core.
2. to quit and stop working with NXT at all.

That's a bit extreme. Different parties are trying to find a compromise and way forward, your comments do nothing but hurt NXT.

Quote from: Tosch110 on November 08, 2015, 12:43:09 am

But it does not seem that core devs are open to these discussions.

Bingo!

That's why I see only two ways:
1. sabotage by NXT holders (forgers)
2. to abandon ship

Again, why are you trying to sabotage NXT?

Again, why are you trying to sabotage NXT?

not NXT, but NRS devs!

if NRS devs can change API, they can fork blockchain any time they want.

There is bottleneck in NXT: "official website", so NXT is centralized.

Moreover, NXT holders are not able to choose THEIR version of blockchain, because NRS guys will hardcode any chain they want to choose.

I think NXT was good experiment which prooved that PoS is unreliable.

Quote from: pianist on November 08, 2015, 12:28:50 am

Quote from: Tosch110 on November 07, 2015, 11:57:19 pm

Yes, I am not ok with the decision not to roll back the API.

NRS devs are destroying NXT platform. You can check NXT price for last year, it shows everything.

There are two ways for us:
1. not to update from 1.5.15 and start developing our own Core.
2. to quit and stop working with NXT at all.

There are way more solutions that came up already. Even if it would be unusual. For example:
1. Return the old API (with changing default output) and say "we have been warned" and delay these updates to 1.7 (when there needs to be major changes anyway)
2. Make 1.6.2 experimental again and this way recommend people to use 1.5.15 instead. Giving Software the time to upgrade
3. Create 1.6.3 where the default API is as before and delay changes until 1.6.4 which will be at a certain date.

I could continue this list. But it does not seem that core devs are open to these discussions.

Create 1.6.3 where the default API is as before and delay changes until 1.6.4 which will be at a certain date.

I think it is a right way to minimize the loss in the whole ecosystem. Both of the core devs and the third project owners have their own perspectives/reasons to do their right things, but it's difficult to meet both of their targets. The change needs time, and they need time to calm down and start the action. The discussions also take time. During this period of time, the end users don't always know that, and they just get the broken api, so they own their votes to wait or give up Nxt ecosystem. If the end user of Supernet or other projects leave, it leads more worries for the project owners/leaders, so they will blame more on Nxt core devs, which is a negative effect cycle. On the other hand, V1.6.3 with default API as before will makes all projects work well, and we just make a small delay of 1.6.X and 1.7, but we have the end users to support all the ecosystem. After 1.6.3, all parties can go on discussions and make their own changes, and go on with a great process.

Difficult to understand why devs are talking to Tennessee guys and not directly to the people who are complaining.  Can't see much progress being made through the current process.

100% agreed.

This has become not a technical procedure problem, but an ego problem.

Eth.

Quote from: Jimmy2011 on November 08, 2015, 04:27:49 am

Create 1.6.3 where the default API is as before and delay changes until 1.6.4 which will be at a certain date.

They won't do this!

Their goal is to do hurt to alt clients, they want to be a small center of "decentralized NXT world".

Moreover, they are angry children and want to sell software for private blockchains, and to make NXT as testnet.

Ethereum is coming and think assets will move there. Another way — to use colored coins.

NXT was interesting project, but as for me it is better to keep aloof from NRS devs.

You may disagree with Jean-Luc, but show some respect, after everything J-L has done for NXT.

Your posts are very offensive, why are the mods not stepping in?

why are the mods not stepping in?

Do you want to become NXT forum like this?

Quote from: maddy83 on November 08, 2015, 01:00:33 am

Again, why are you trying to sabotage NXT?

not NXT, but NRS devs!

if NRS devs can change API, they can fork blockchain any time they want.

There is bottleneck in NXT: "official website", so NXT is centralized.

Moreover, NXT holders are not able to choose THEIR version of blockchain, because NRS guys will hardcode any chain they want to choose.

I think NXT was good experiment which prooved that PoS is unreliable.

That's total nonsense, you could start today a Nxt XT fork with changes in fees for example, you might get 70% of the current Nxt userbase but who is maintaining the branch? You? Most people here have other full time jobs.
Nxt is at the current state not a hardcoded protocol like bitcoin and nothing is really set in stone. This has the disadvantage that you have "nrs core client maximalism", all other nxt wallet client developers abandoned there projects. This trend will continue in my opinion till  NRS development will be opend and jean-luc gives a little of his power to other developers. The advantage with the current strategy is that you can develop the nxt roadmap "faster".