Any news on Version 0.9.8-17

[dpeca]

They said " 2 weed " , they lie

each day we late is used to make better code... (testing, fixing bugs)...
so, you will get better v17...

[alexcy]

Lying is a not a nice word for people working on a project without getting paid. Their work should be greatly appreciated by all of us.

What I don't understand is why bug fixes that have been already fixed are not being released, somethin like 0.9.8-16.1 or something.

[mehargags]

why bug fixes that have been already fixed are not being released, somethin like 0.9.8-16.1 or something.

I exactly agree... I think VestaCP should have a monthly rolling model release in which security and bug fixes are pushed out.
features and new things can wait.

[alexcy]

We completely agree on this. It doesn't mean that every new release needs new features. Not at all.

[dpeca]

I was talking the same before I became contributor - and I'm still thinking the same.
After v16 - which is a little buggy - it was good idea to release v16-1... but however, obviously main developers didn't think the same...

Anyway...
In some way - you already can get latest code - by fetching new code from github.
By my opinion - source from github is much more stable and less buggy than v16 - it contains A LOT of bugfixes - and personally I'm using that code on all my production servers - BUT - big important BUT - I will not give advice that you should use it - just because I don't want to be responsible if something goes wrong on your server.

I can afford it - because I know all code that developers is pushing in github - and eventually I can make a fix very quickly if I figure out that something is wrong (that way I can also see if there are new bugs - and fix them immediately).
I can say that I have a trust in that code from github, because I read all code that is pushed there.
And personally I believe that code from github is much more stable than v16.
But again - I can not give you advice to use it - just because I don't want to be responsible for that advice.

However...
I feel v17 will be released very soon... so little more pateince will be the best choice.

[alexcy]

Thanks a lot dpeca for both your contribution and comments.

We agree for github, that you can get some fixes from there. However this is an unnecessary pain (I am running 14 VPS, all in production with Vesta at the moment). I am asking for several months (maybe a year) for an answer why not pushing the bugfixes and didn't get any.

All software works like this. Alpha, Beta, Release, Fixes and after all these new features. You guys know that much better than me (I am not a programmer).

[alexcy]

And I am not talking only for v17. It's a general suggestion for all releases from now on.

And I say this again. There is no pressure to add new features in every update. Just bugfixes and security fixes (if any).

[imperio]

Yes, we understand you. After the release 17, bug fixes will come out more often. We already think about it.
New release will be soon. Now we are fixing bugs after development. After that will be final testing on all operating systems.
Please wait, we already finish work on the new version.

[alexcy]

Great news imperio. Do you have an expected release date?

Thanks.

[web-seo-consulting]

What I find much more complicated is the matter with bugs.vestacp.com and github.

What is the main archive, where should you report and where can you see the current status of the project?

Why double-care or agree on Github and good.

The issues of Github are not categorized, no milestones are entered.

For several days on Github but much on bugs.vest ... is everything "dead".

My wish would be the bugs.vesta. To github and we can see everything there and report and have a starting point to the forum and not two as currently and none knows which is the leading, whereby the user with Github have already decided ;)