BitShares Forum
Main => General Discussion => Topic started by: clayop on January 05, 2016, 04:35:31 am
-
Polo still hasn't upgraded to the newest version. They may miss the news.
I argued for running a mailing list for exchanges, but someone rebutted me saying they can follow a thread.
But I think the thread is badly organized and not timely updated. This small thing makes a huge difference. Please have a good communication with our business partners.
-
they should follow github like any other professional exchange.
-
I think they're following the github. However there is no much information on the newest release like before.
BM mentioned that CNX will announce something soon in the "witness alert and status" thread.
This release:
Changes:
* Hardfork to fix hung blockchain
* removed debug spam
Last release:
This release 2.0.151216b fixes a dereference issue in the previous release, 2.0.151216. The following users are advised to upgrade:
* All users running 2.0.151216
* All users running 2.0.151209 or earlier
Replaying the blockchain will be required, and should occur automatically.
-
I have also proposed an email alert list: https://bitsharestalk.org/index.php/topic,20609
That one could be also used for informing exchanges about any changes they might need to know.
-
https://bitsharestalk.org/index.php/topic,19040.msg269828/topicseen.html#new
We also have a skype group for exchanges .. just tell them to send a mail to fabian@cryptonomex.com
-
Exchanges should be notified individually of things like this if you want them to keep up to date. How difficult is it to send an email?
-
Exchanges should be notified individually of things like this if you want them to keep up to date. How difficult is it to send an email?
github sends out emails on a change, that's not the problem here.
The question is, why is no one referring to bitshares github? Is it an administration problem?
-
github sends out emails on a change, that's not the problem here.
The question is, why is no one referring to bitshares github? Is it an administration problem?
I'm sure it does, but that requires each exchange to subscribe to every single github for every single coin; the email traffic that would create would be an untenable mess - consider exchanges which have 100s of coins, that's 100s of emails per day containing irrelevant noise.
-
Has anyone asked exchanges how they prefer to be alerted? We are still so small that we have to be ready to actively serve the exchanges and not the other way around.
-
Exchanges should be notified individually of things like this if you want them to keep up to date. How difficult is it to send an email?
It's easy. After click the "notify" button above/below a thread, you'll get an email when there is a new reply in that thread.
-
Exchanges should be notified individually of things like this if you want them to keep up to date. How difficult is it to send an email?
It's easy. After click the "notify" button above/below a thread, you'll get an email when there is a new reply in that thread.
This kind of attitude is what caused the mess moving over from 1.0 to 2.0.
-
Exchanges should be notified individually of things like this if you want them to keep up to date. How difficult is it to send an email?
It's easy. After click the "notify" button above/below a thread, you'll get an email when there is a new reply in that thread.
This kind of attitude is what caused the mess moving over from 1.0 to 2.0.
So what did you do? complain to BM?