Merging Github patches

[phre4k]

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.

[skurudo]

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...

[phre4k]

Any ETA on the rewrite? Why is this not done via github branch? :)

[imperio]

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.

[phre4k]

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.

[imperio]

We will think about it. Thank you for your suggestion.

[phre4k]

We will think about it. Thank you for your suggestion.

Nice to hear you're considering this!

I'm eager to test it when it's out. Good luck :)

[skurudo]

Closed due inactivity.