GLBSE 2.0 release delayed again!

[Nefario]

UPDATE!

Once again we're going to delay the release of GLBSE2.0

You can see the progress that has been made at http://dev.glbse.com, but there are still some bugs to work out and a couple of crucial things to add (like bitcoin deposits/withdrawals lol).

I've been working on this non-stop since Friday, taking a little time of only to work on something else, during this time I've not slept.

I'm quite sure if I was to try to stick with today as the release date two things:
1) It wouldn't be ready, and everyone would be unhappy
2) The stress would most probably kill me.

What was meant to be 2-3 days has become a lot longer, I'm sorry for the delay.

Nefario.

[marked]

I'm logged in but getting nothing but balance sitting at retrieving, and trying to click on bitcoin/assets/market history just sticks at refreshing.

I've logged in and out a few times over the last few hours, but still the same.

marked

[Nefario]

Thank m, fixed that.

Nefario.

[marked]

Thank m, fixed that.

Nefario.

many thanks. Logged in now.

Out of interest this is the third week in a row that it's gone down monday that I know of in this manner.

Is this due to all the dividends being paid out Sunday/Monday?

marked

[JL421]

Nefario, 3 questions.

1) When GLBSE 2.0 gets pushed, how will account owners transfer their information into the new system, or how will we have to prove our ownership of accounts in the new system if everything is automatically migrated?

2) Will all asset contracts held by an account be moved into the new system?

3) Will we finally be able to edit contracts? I have plans for the original JLP but I'd obviously have to edit the contract to something that made sense.

Thanks

[Nefario]

I'm not sure as to the reason why it's happening on Mondays. my experience is that it usually happens just as my net connect goes down, like today for example.

JL, when 2.0 launches, I'll freeze 1.0, and move the most active assets over(at first).

The next step will be to log into you 1.0 account and it will give you a code, enter that into 2.0 and it will transfer everything.

Yes we'll finally be able to edit contracts, however not right away. Contract edits will be put to a vote, if passed then the edit becomes the contract.

Nefario.

[JL421]

Thank you much sir. This should be exciting, I'm liking how the new system looks an functions so far. (At least on the dev site).

[Nefario]

It should really improve things, easier to use, more functionality, and we'll have more users (and liquidity) as a result.

[marked]

It should really improve things, easier to use, more functionality, and we'll have more users (and liquidity) as a result.

Looking forward to it...

marked

[JL421]

so the web keys idea was ahead of time?
switching back to username / password seems like kind of fail to me
hope it improves somehow site availability

Go to dev.glbse.com, check out how it's going to look. I believe it will add much more usability to the site, and be much more user-friendly than the current version.

Web keys were a good idea, the problem was that users didn't understand how they worked, and that they needed to back them up.

[labestiol]

Take as much time as you need. I vastly prefer the safe approach.

[Herodes]

Good decision to postphone the upgrade. No point in deploying software that's not finished.

[Kluge]

Thanks for the work, Nefario! Looking forward to release!

[JL421]

Still delayed I take it?

[Bitcoin Oz]

Id like to gather sample contracts together to give people an idea on how to construct their own. Is there a way to view them all without having to go into each companies page ?

[Nefario]

Still delayed I take it?

Yeah, I've just finished a presentation at TEDx in Leeds (which went terrible), and I'm off to bed, I'll kick off development in the morning and aim to have all the features for the release (with loads of bugs) up on the demo site for bug hunting and feedback.

Mila's found a ton of bugs in the current demo that I've not fixed yet, I've been racing to get release features done and dealing with tons of non GLBSE2.0 stuff that's held me back.

Nefario.

[eroxors]

I'm anxiously awaiting this. I've waited to pull the trigger on some shares because I'm utterly confused by the process. Hopefully this will help.

[JL421]

what about call off 2.0 and  call it 2.01 (tomorrow's release).
before weekend you get another ton of bugs and 2.02 might be final RC

and what about using glbse forum for bugs or even better a tracking tool?
I would reduce testing effort on each new version announcement. srsl.

not want to impose issue tracking and proper tagging of affect/fix version or status and stuff. but it could self announce new version once well tested (no critical bug found in 5 days, count of open medium bugs lower than X). you manage community at intersango, what about community around glbse?

would you mind to use the github tool provided?

As much as I hate to say it, as long as there aren't any security holes, just push it how it looks on the dev...it can be a constantly evolving project. This vs trying to push it all out at once.

[Nefario]

Certain functionality is needed, IPO's haven't been done yet, etc.

[JL421]

Will we be having fewer sql database lockups in the new version?