We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Merging Github patches
Merging Github patches
Hey guys,
We have a discussion about maintainers of the github repo here:
https://github.com/serghey-rodin/vesta/issues/641
It'd be very nice if Serghey could destine some github users for merging code into a dev branch of the software, since a lot of the PRs (currently 53 and rising!) pile up and nobody merges them.
We have a discussion about maintainers of the github repo here:
https://github.com/serghey-rodin/vesta/issues/641
It'd be very nice if Serghey could destine some github users for merging code into a dev branch of the software, since a lot of the PRs (currently 53 and rising!) pile up and nobody merges them.
Re: Merging Github patches
Thanks for the offer. Serghey aware of the situation, I think that in the near future it will.
Now merge code little sense, since serious refactoring...
Now merge code little sense, since serious refactoring...
Re: Merging Github patches
Any ETA on the rewrite? Why is this not done via github branch? :)
Re: Merging Github patches
Hi,
Now we are rewriting all vestacp code, so you cant see some changes in the github. When the refactoring will be done, we will publish it on the github repository.
Now we are rewriting all vestacp code, so you cant see some changes in the github. When the refactoring will be done, we will publish it on the github repository.
Re: Merging Github patches
Yes, I understood that.
However, I think developing "in the dark" is not the best idea for the future of VestaCP (after the rewrite).
You can create an "alpha" or "beta" branch on github which differs from the master branch and is for rewriting existing code which doesn't land in production. This could also be a test bed for contributions by other people on github so they can be tested and don't land in the master branch immediately.
You could also leverage the tags and releases from github to make the whole development process more streamlined. What do you think about that? At the moment the github repository and development process is pretty suboptimal, in my opinion.
However, I think developing "in the dark" is not the best idea for the future of VestaCP (after the rewrite).
You can create an "alpha" or "beta" branch on github which differs from the master branch and is for rewriting existing code which doesn't land in production. This could also be a test bed for contributions by other people on github so they can be tested and don't land in the master branch immediately.
You could also leverage the tags and releases from github to make the whole development process more streamlined. What do you think about that? At the moment the github repository and development process is pretty suboptimal, in my opinion.
Re: Merging Github patches
We will think about it. Thank you for your suggestion.
Re: Merging Github patches
Nice to hear you're considering this!imperio wrote:We will think about it. Thank you for your suggestion.
I'm eager to test it when it's out. Good luck :)
Re: Merging Github patches
Closed due inactivity.