elective-stereophonic
elective-stereophonic
[CORE] Release or Not Release  
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Author Topic: [CORE] Release or Not Release  (Read 6547 times)

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
[CORE] Release or Not Release
« on: May 14, 2015, 07:04:46 pm »

Hi guys,

not sure what Billy Mays would say about this. But 1.5.x series includes tons of new code and substantial changes in the overall transaction processing. Some of them are described here.

In order to be able to release that beast, we need testing. Testing, testing, testing and once again testing. From everybody; from your mother, from your uncle, from you friends and from your neighbors. Sit together, make barbecues and test the new NRS. Try out everything you always wanted to do, especially phased stuff such as phasedly transferring an alias and delete it before the phasing action is done. A bottle of beer or a glas of wine might help you here.

Testnet is waiting for you! Get your testNXTs at https://nxtforum.org/testnet/some-testnxt-to-test-asset-exchange/780/ now!

Cheers,
Chuck
Logged

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: [CORE] Release or Not Release
« Reply #1 on: May 15, 2015, 08:34:56 am »

I think one PC can run mainnet and testnet at the same time,so anyone if you run mainnet,you should run testnet as well,let's testing!
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

BillyMays

  • Jr. Member
  • **
  • Karma: +45/-13
  • Offline Offline
  • Posts: 15
  • HI BILLY MAYS HERE...
    • View Profile
Re: [CORE] Release or Not Release
« Reply #2 on: May 15, 2015, 09:41:23 am »

Logged
NXT IS THE NEXT GENERATION CRYPTOCURRENCY!  THAT'S N... X... T.  AGAIN, THAT'S IN... EX... TEEBUT WAIT... THERE'S MORE!  IF YOU CALL RIGHT NOW, I'LL DOUBLE TRIPLE THE OFFER!  WHAT ARE YOU WAITING FOR?  R U READY TO UNLEASH THE POWER OF NXT?!

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: [CORE] Release or Not Release
« Reply #3 on: May 15, 2015, 10:24:03 am »

Logged

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] Release or Not Release
« Reply #4 on: May 15, 2015, 11:56:08 am »

That's the spirit! :-)

But honestly guys: we REALLY, REALLY need testing, otherwise we just can't release this on mainnet. There are edge cases for the various transaction types in combination with phasing - phased paying & delivering goods on marketplace, phased alias transfer/sell, phased voting, phased currency creation,... - and unless at least most of these various cases are not yet tested at least once (ONCE!) it is just not acceptable to have these cases for the first time executed (and tested) on mainnet.

So please make this a priority so that we are finally able to get this large release over the final hurdle: maybe take a certain feature area (aliases), think about all the test cases you can imagine and write a short summary of what you did ("Transfering an alias, transferral to be approved by one other account", "This and that happened", "Behaviour seems to be normal/expected"). Something like that!

Thanks guys, I know this is not the most entertaining of tasks, but this is really necessary, and - believe me - I've also already done of lot of these! :-)
And: the beer after these 2-3 hours will taste sweeter than ever!
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: [CORE] Release or Not Release
« Reply #5 on: May 15, 2015, 11:58:43 am »

That's the spirit! :-)

But honestly guys: we REALLY, REALLY need testing, otherwise we just can't release this on mainnet. There are edge cases for the various transaction types in combination with phasing - phased paying & delivering goods on marketplace, phased alias transfer/sell, phased voting, phased currency creation,... - and unless at least most of these various cases are not yet tested at least once (ONCE!) it is just not acceptable to have these cases for the first time executed (and tested) on mainnet.

So please make this a priority so that we are finally able to get this large release over the final hurdle: maybe take a certain feature area (aliases), think about all the test cases you can imagine and write a short summary of what you did ("Transfering an alias, transferral to be approved by one other account", "This and that happened", "Behaviour seems to be normal/expected"). Something like that!

Thanks guys, I know this is not the most entertaining of tasks, but this is really necessary, and - believe me - I've also already done of lot of these! :-)
And: the beer after these 2-3 hours will taste sweeter than ever!
We have funds available in the Destroyer fund.
If you can define bug payout thresholds, why not to use these funds for bug bounties?

James

P.S. Assuming none of the destroyer asset holders are objecting
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

yassin54

  • Hero Member
  • *****
  • Karma: +240/-14
  • Offline Offline
  • Posts: 2503
  • I am Homer, Sorry my english is Bad!!
    • View Profile
Re: [CORE] Release or Not Release
« Reply #6 on: May 15, 2015, 12:16:01 pm »

P.S. Assuming none of the destroyer asset holders are objecting
No objecting for me  :)
i agree

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] Release or Not Release
« Reply #7 on: May 15, 2015, 01:53:16 pm »

P.S. Assuming none of the destroyer asset holders are objecting
No objecting for me  :)
i agree

That sound's good actually.

I would suggest to make the bounty based on test report completeness split up by transaction types, cause it would be generally worthwhile to see
what cases are already covered and how the system is behaving, so people would write down their tests describing the cases like this:

A1 ...
A2 ...
A3 Transfer Asset, Phasing BY-Account, Selling in Between
Test Description:
An asset is transfered from account A to account B, C has to approve the transaction at height x. Before transaction finishes it is tested to sell the same asset units on the asset exchange
Observed Behaviour:
UI: This is not possible and prevented in the UI, API: The API returns an error saying that...
Evaluation:
Behaviour seems normal/as expected

Or is this too bureaucratic and contradicts the nature of your fund? :-)

I would suggest the following bounties for executing/describing test cases:

- Test phasing itself: min. 12 test cases, 2.500 NXT
- Asset Exchange: min. 12 test cases, 2.500 NXT
- Monetary System: min. 12 test cases, 2.500 NXT
- Voting System: min. 8 test cases, 1.500 NXT
- Aliases/Messaging: min. 8 test cases, 1.500 NXT
- Marketplace: min. 12 test cases, 2.500 NXT
- Balance Leasing/Payment/Other: min. 8 test cases, 1.500 NXT

Total: 14.500 NXT

Does this make sense? Could you organize the payout for this? Would be great!





Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: [CORE] Release or Not Release
« Reply #8 on: May 15, 2015, 03:15:14 pm »

P.S. Assuming none of the destroyer asset holders are objecting
No objecting for me  :)
i agree

That sound's good actually.

I would suggest to make the bounty based on test report completeness split up by transaction types, cause it would be generally worthwhile to see
what cases are already covered and how the system is behaving, so people would write down their tests describing the cases like this:

A1 ...
A2 ...
A3 Transfer Asset, Phasing BY-Account, Selling in Between
Test Description:
An asset is transfered from account A to account B, C has to approve the transaction at height x. Before transaction finishes it is tested to sell the same asset units on the asset exchange
Observed Behaviour:
UI: This is not possible and prevented in the UI, API: The API returns an error saying that...
Evaluation:
Behaviour seems normal/as expected

Or is this too bureaucratic and contradicts the nature of your fund? :-)

I would suggest the following bounties for executing/describing test cases:

- Test phasing itself: min. 12 test cases, 2.500 NXT
- Asset Exchange: min. 12 test cases, 2.500 NXT
- Monetary System: min. 12 test cases, 2.500 NXT
- Voting System: min. 8 test cases, 1.500 NXT
- Aliases/Messaging: min. 8 test cases, 1.500 NXT
- Marketplace: min. 12 test cases, 2.500 NXT
- Balance Leasing/Payment/Other: min. 8 test cases, 1.500 NXT

Total: 14.500 NXT

Does this make sense? Could you organize the payout for this? Would be great!
I have no time to organize, my idea is just to send the total amount to someone that will manage the individual payouts.
The funds are available, just need someone to manage the process
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] Release or Not Release
« Reply #9 on: May 15, 2015, 04:18:21 pm »

P.S. Assuming none of the destroyer asset holders are objecting
No objecting for me  :)
i agree

That sound's good actually.

I would suggest to make the bounty based on test report completeness split up by transaction types, cause it would be generally worthwhile to see
what cases are already covered and how the system is behaving, so people would write down their tests describing the cases like this:

A1 ...
A2 ...
A3 Transfer Asset, Phasing BY-Account, Selling in Between
Test Description:
An asset is transfered from account A to account B, C has to approve the transaction at height x. Before transaction finishes it is tested to sell the same asset units on the asset exchange
Observed Behaviour:
UI: This is not possible and prevented in the UI, API: The API returns an error saying that...
Evaluation:
Behaviour seems normal/as expected

Or is this too bureaucratic and contradicts the nature of your fund? :-)

I would suggest the following bounties for executing/describing test cases:

- Test phasing itself: min. 12 test cases, 2.500 NXT
- Asset Exchange: min. 12 test cases, 2.500 NXT
- Monetary System: min. 12 test cases, 2.500 NXT
- Voting System: min. 8 test cases, 1.500 NXT
- Aliases/Messaging: min. 8 test cases, 1.500 NXT
- Marketplace: min. 12 test cases, 2.500 NXT
- Balance Leasing/Payment/Other: min. 8 test cases, 1.500 NXT

Total: 14.500 NXT

Does this make sense? Could you organize the payout for this? Would be great!
I have no time to organize, my idea is just to send the total amount to someone that will manage the individual payouts.
The funds are available, just need someone to manage the process

Hmm, I can do that, I have to distribute the funds for Crowdin translation anyway.
I nothing, speaks against it, just send the 14.500 NXT to my account at: NXT-AQ9F-JC4F-NCM2-4JSXZ

I will then start a new thread, look for people, distribute tasks and pay out/or pay you back depending on the outcome.
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: [CORE] Release or Not Release
« Reply #10 on: May 16, 2015, 10:27:05 am »

I will then start a new thread, look for people, distribute tasks and pay out/or pay you back depending on the outcome.

+1440

Excellent idea. Go ahead.
Logged

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: [CORE] Release or Not Release
« Reply #11 on: May 16, 2015, 10:40:33 am »

Noob tester now on board  8) so prepare for some annoyingly confusing ramblings and a lack of comprehension of what is happening in front of me. My main worry is I'll do something and... I won't even be able to tell if it worked properly or not  ;D
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: [CORE] Release or Not Release
« Reply #12 on: May 16, 2015, 10:48:51 am »

I think a title change would be good. Thread looks like a discussion thread rather than a testing thread. Maybe "Release or Not Release? We need TESTERS to help us decide"

Or "Want to see the launch of the next NRS release? We need testers first, help out where you can"
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: [CORE] Release or Not Release
« Reply #13 on: May 16, 2015, 11:17:16 am »

P.S. Assuming none of the destroyer asset holders are objecting
No objecting for me  :)
i agree

That sound's good actually.

I would suggest to make the bounty based on test report completeness split up by transaction types, cause it would be generally worthwhile to see
what cases are already covered and how the system is behaving, so people would write down their tests describing the cases like this:

A1 ...
A2 ...
A3 Transfer Asset, Phasing BY-Account, Selling in Between
Test Description:
An asset is transfered from account A to account B, C has to approve the transaction at height x. Before transaction finishes it is tested to sell the same asset units on the asset exchange
Observed Behaviour:
UI: This is not possible and prevented in the UI, API: The API returns an error saying that...
Evaluation:
Behaviour seems normal/as expected

Or is this too bureaucratic and contradicts the nature of your fund? :-)

I would suggest the following bounties for executing/describing test cases:

- Test phasing itself: min. 12 test cases, 2.500 NXT
- Asset Exchange: min. 12 test cases, 2.500 NXT
- Monetary System: min. 12 test cases, 2.500 NXT
- Voting System: min. 8 test cases, 1.500 NXT
- Aliases/Messaging: min. 8 test cases, 1.500 NXT
- Marketplace: min. 12 test cases, 2.500 NXT
- Balance Leasing/Payment/Other: min. 8 test cases, 1.500 NXT

Total: 14.500 NXT

Does this make sense? Could you organize the payout for this? Would be great!
I have no time to organize, my idea is just to send the total amount to someone that will manage the individual payouts.
The funds are available, just need someone to manage the process

Hmm, I can do that, I have to distribute the funds for Crowdin translation anyway.
I nothing, speaks against it, just send the 14.500 NXT to my account at: NXT-AQ9F-JC4F-NCM2-4JSXZ

I will then start a new thread, look for people, distribute tasks and pay out/or pay you back depending on the outcome.
sounds good. I will send tomorrow
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: [CORE] Release or Not Release
« Reply #14 on: May 16, 2015, 11:22:59 am »

Bug Report  8)

The security notice on the front page says "can loose your NXT! In doubt". It should be "can lose your NXT! If in doubt"

I would suggest removing "sandboxed" too. "Plugins are not restricted in any way have full access to your client including your passphrase." is enough to get the message across clearly. Sandboxed is scary computer language and the world of the unknown.
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

_mr_e

  • Hero Member
  • *****
  • Karma: +88/-18
  • Offline Offline
  • Posts: 956
    • View Profile
Re: [CORE] Release or Not Release
« Reply #15 on: May 16, 2015, 02:39:45 pm »

So did destroyer get paid anything?
Logged

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] Release or Not Release
« Reply #16 on: May 17, 2015, 01:46:50 pm »

Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

ThomasVeil

  • Hero Member
  • *****
  • Karma: +183/-11
  • Offline Offline
  • Posts: 1400
    • View Profile
Re: [CORE] Release or Not Release
« Reply #17 on: May 18, 2015, 09:44:52 am »

So did destroyer get paid anything?

Nope, as they didn't want the precious NXT.
I think the informal consensus is to repurpose the fund for general bug hunting.
Logged
ARDOR-BPV3-837M-QZTQ-9DQ69  oxpal.com

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: [CORE] Release or Not Release
« Reply #18 on: May 20, 2015, 12:15:42 am »

P.S. Assuming none of the destroyer asset holders are objecting
No objecting for me  :)
i agree

That sound's good actually.

I would suggest to make the bounty based on test report completeness split up by transaction types, cause it would be generally worthwhile to see
what cases are already covered and how the system is behaving, so people would write down their tests describing the cases like this:

A1 ...
A2 ...
A3 Transfer Asset, Phasing BY-Account, Selling in Between
Test Description:
An asset is transfered from account A to account B, C has to approve the transaction at height x. Before transaction finishes it is tested to sell the same asset units on the asset exchange
Observed Behaviour:
UI: This is not possible and prevented in the UI, API: The API returns an error saying that...
Evaluation:
Behaviour seems normal/as expected

Or is this too bureaucratic and contradicts the nature of your fund? :-)

I would suggest the following bounties for executing/describing test cases:

- Test phasing itself: min. 12 test cases, 2.500 NXT
- Asset Exchange: min. 12 test cases, 2.500 NXT
- Monetary System: min. 12 test cases, 2.500 NXT
- Voting System: min. 8 test cases, 1.500 NXT
- Aliases/Messaging: min. 8 test cases, 1.500 NXT
- Marketplace: min. 12 test cases, 2.500 NXT
- Balance Leasing/Payment/Other: min. 8 test cases, 1.500 NXT

Total: 14.500 NXT

Does this make sense? Could you organize the payout for this? Would be great!
I have no time to organize, my idea is just to send the total amount to someone that will manage the individual payouts.
The funds are available, just need someone to manage the process

Hmm, I can do that, I have to distribute the funds for Crowdin translation anyway.
I nothing, speaks against it, just send the 14.500 NXT to my account at: NXT-AQ9F-JC4F-NCM2-4JSXZ

I will then start a new thread, look for people, distribute tasks and pay out/or pay you back depending on the outcome.
sent 25k, i want to make sure there are funds for bugs found outside the confines of the test points too

6175007753262640931
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] Release or Not Release
« Reply #19 on: May 20, 2015, 06:33:21 am »

We now have 25.000 NXT as bounties for 1.5 testing together with a broader scope thanks to @jl777/Destroyer Fund:
https://nxtforum.org/general-discussion/(core)-1-5-release-phasing-testing-14-500-nxt-bounty/

I also stripped down instructions (too long read).
« Last Edit: May 20, 2015, 08:19:52 am by HolgerD77 »
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ
 

elective-stereophonic
elective-stereophonic
assembly
assembly