Why BBP has no any commit on Github from the end of March?
Thanks
It was moved to another repository:
https://github.com/biblepay/biblepay-evolutionNoko proves my point from earlier: I strongly believe we should use the original repository and now merge the new commits to it. Many users and particularly tracker websites are following the original repository, so BiblePay is falling down in their algorithmic rankings, due to perceived stopped development.
To help our third party sites (and any lost biblepay-classic users) realize we moved:
Since github supports repo redirects, I have added a github redirect file to our old repo:
https://github.com/biblepay/biblepayAnd added a note that we have moved also.
Note that moving Evo to BiblePay would not be possible (unless we first decided to Delete the BiblePay repo during our last mandatory upgrade)- but since I decided to maintain both repos for an additional quarter (while classic was being maintained from a code perspective and prod perspective), that decision was made for a smooth transition, and now, it is not possible to move Evo back to BiblePay (without breaking all kinds of scripts, deployments, exchanges, integrations and relationships) - and there are many places in the code that relies on the github location - and - it would require a very large effort and a mandatory upgrade with every provider. Now, they all should know us as "biblepay-evolution" and they need to upgrade to our new github location - and realize we have a new product name to update. If we ever decide to move back to "BiblePay", or to a new name, we will have to take all of this into account before the mandatory upgrade. (I'm not insinuating we made an error; the change was deliberate because we were maintaining a prod branch while running side by side with Evo to make sure it was compatible).
Our product is now Biblepay-Evolution.