That would be so awesome!
So close to fleming can’t handle it, I am so excited! fleming · GitHub
Use Linux
You’ll never look back VirtualBox(and others) are available for those who must taper off their use of MS products
Probably will not get an answer but then thinking loud, is testnet going to be run after all the routing improvements are in place (will take some weeks) or before hmm
Edit: A fresh new interesting repo just appeared in Github
We’re already running local testnets You will see a lot of activity in the next wee while. Just watch it happen
Ooh, exciting stuff! Looking forward to more updates!
Interesting new actions tab in routing.
If I could actually read it and understand it…
Looks like GitHub Actions continuous integration configurations to me …
Amazing to be able to see the developers work with such a level of transparency.
Thank you all @maidsafe !!
It is, it’s nice as it allows us to see easily where any failures are without logging into different systems. Also allows community to easily see the tests and outputs. So faster, simpler and probably drawing us into microsofts lair For now it works well for us though.
I thought you were going to use Jenkins? Too big a hammer for the nut?
GH actions are so much simpler really. Plus we don’t pay for all the jenkins stuff that we would need (remote host etc.) We do pay for GH actions though.
I thought that GitHub Actions usage was free for public repositories (because GH “loves open source”). Are there some limits?
Yes there are, we pay for faster and more parallel builds/tests etc. I’s just we have a lot of repos. It was the same with appveyor and the other CI frameworks. I understand it really, if you can wait you don’t pay, but a decent size team and you need to.
Friend,
for the millionth time. They explained to you that you shouldn’t pay much attention to GitHub…
You asked this previously, do you not accept the answer
For more than 2 months safe-api has been incompatible with safe_vault fleming branch. But today this situation has changed: safe-api has been updated with promising commits, so I tested them, and they seem to work together.
I don’t know if this is the sign of an imminent announcement, but at least, we can play again with a local vault using the latest releases of MaidSafe repositories.
@gouda123, MaidSafe organisation on GitHub is only the tip of iceberg. Developments are done in developers’ repositories and MaidSafe repositories only consolidate them.
Which is just common git ops practice. Start with a base repo. New enhancements and work either go in a branch or your own full fledged fork. Then promote back into the original repo once its pull request worthy(meaning its has been tested on their end, and hopefully contains unit tests) for validation from other engineers.