Topic: GLBSE 2.0 release delayed again! - page 2. (Read 4304 times)
Yes it is. Thanks
Yep, can't switch away from JLP-BMDT
Brilliant, thanks for that, it was a bug, fixed now.
Yep, can't switch away from JLP-BMDT
I got an ArgumentError at /asset/create...when trying to ...well you know...even though it still shows up?
But when you click on the asset you get a lovely NoMethodError at /asset/view/JLP-BMDT
Then when I choose an asset account, I can't change back to my BTC accounts.
But when you click on the asset you get a lovely NoMethodError at /asset/view/JLP-BMDT
Then when I choose an asset account, I can't change back to my BTC accounts.
Thanks, fixed the first bug, is the second one (not being able to switch back to BTC account) still happening?
I got an ArgumentError at /asset/create...when trying to ...well you know...even though it still shows up?
But when you click on the asset you get a lovely NoMethodError at /asset/view/JLP-BMDT
Then when I choose an asset account, I can't change back to my BTC accounts.
But when you click on the asset you get a lovely NoMethodError at /asset/view/JLP-BMDT
Then when I choose an asset account, I can't change back to my BTC accounts.
I've updated the test site, added loads of functionality and introduced loads of bugs.
It's ugly, but it just about works.
Go to http://dev.glbse.com
Feedback welcome
It's ugly, but it just about works.
Go to http://dev.glbse.com
Feedback welcome
Will we be having fewer sql database lockups in the new version?
0 is the expected number of DB lockups in the new version.
Just an update on where I'm currently at, the demo site will be updated in a couple of hours, hacking away, wired up to my eyeballs on Rockstar XDurance(think RedBull but strong, bigger can, and cheaper).
Will we be having fewer sql database lockups in the new version?
Certain functionality is needed, IPO's haven't been done yet, etc.
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?
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.
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.
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.
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 ?
Still delayed I take it?
Thanks for the work, Nefario! Looking forward to release!
Good decision to postphone the upgrade. No point in deploying software that's not finished.
Take as much time as you need. I vastly prefer the safe approach.
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
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.
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
It should really improve things, easier to use, more functionality, and we'll have more users (and liquidity) as a result.
Jump to: