Version numbering, differences & ETA ???

[nrs]

Hi..
I have been looking on you different VM2 versions.

It looks like the current production version is 2.0.14, developer version is 2.1, and an expected production release is to be 2.2.. correct ?

What news/fix is expected to be in 2.2 and what is the ETA for it ? (and please understand the E as 'Estimated' and not as an A.. for 'Accurate'    .. plus / minus whatever months)

I have been trying to deciffer the info found in the developer portal, but not everything there is "quite" up to date... and it would be SO NICE if someone would update overview and news sections..

(Yes I know some of the developers "hates" to write documentation like this, but as an programmer with +30 years experience I REALLY REALLY appreciate when people  would do this also... )

For the best way to get more people into an open project is to get the info floating :-)

[Milbo]

The ETA of vm2.2 was christmas and I think we postpone it to january.

[beipink]

Hi..
I have been looking on you different VM2 versions.

It looks like the current production version is 2.0.14, developer version is 2.1, and an expected production release is to be 2.2.. correct ?

I understand odd numbers are development and even are stable release
VM2.0  will only receive security updates and 2.0.15 is currently in the pipeline to become VM 2.0.16
Meanwhile VM2.2 is also being developed as a  new branch with new features and of course bug fix.
I would imagine VM 2.0 maintenance will discontinued short after VM2.2 is out .

[bytelord]

atm there are two trunks on for 2.1 and one for 2.0 ... is not discontinued, just 2.0.16 will have some fixes and new features from 2.1 ... the same vm2 version at all, no migration, only update

2.0.16 will also haves the multiprices ...

[capricornio]

Where can we find more info about current and upcoming versions ?
My live site is running 2.0.12f.
Is there a changelog for 2.0.14, 2.0.15 ? Can't find it, and I would like to check whether it's important to update now or wait for a new release.
Since I have a lot template overrides, every update cost me a lot of time testing whether everything works fine. Would love to minimize that.

Also would appreciate a central buglist, so we can check that before spending hours of testing by thinking it's my own config mistake.

[bytelord]

Hello,

For template changes here: http://virtuemart.net/index.php?option=com_content&id=416
also under here: http://dev.virtuemart.net/projects/virtuemart/files
you can find the layout changes by images [com_virtuemart.[version]_layout_changes.zip]

you can track the changes of the code inside the trunk: http://dev.virtuemart.net/projects/virtuemart/wiki/Setting_up_a_Development_Environment

Regards

[Milbo]

Additionally, every news about a new version contains the list with the new features and fixes. You can directly go from 2.0.12 to 2.0.16 then.  The next version will be a vm2.2. Dont be afraid. There is no migration, just an update. Different is this time that you also have to update your plugins using customfields.

[nrs]

When I was checking the code related to custom fields (special in the checkout process, after payment is complete)  the difference in the 2.0.14 code, and the code in GIT did seem quite massive..

in 2.0.14 a lot of the custom fields code is out-comment, but in the git code the code was quite different. (I expect the GIT code to be close to 2.2)

If the change to 2.2 is only an update, will there be an longer description of this ?

And is there an RC package of 2.2, so I can change my modules, instead of using a load of time to adapt it to 2.0.14.. and then 2.2 is out in ultimo jan..

[Milbo]

The customfields are really almost completly "different". I worked 2 weeks on them and it was the same for the shopowner/user, but a massive change in data organisation. The programmer who wrote the customfields is thinking flow orientated and was not the right person to write such a system. Now I start to change a bit the logic for the users. Of course it should be more intuitiv.

An example, I used for this the product shovel, with the dynamic children
vm2.0.15: 205 queries
vm2.1: 134 queries
Mainpage
vm2.0.15 Application 1.407 seconds (+0.011); 25.46 MB
Application 0.689 seconds (+0.009); 20.20 MB (+0.107) vm2.1

But this numbers are not so good to compare, cause even you set everything the same, two installation starts to differ soon on the mainpage, for example the feature recent products, or topten products creates fast different load, depending on user and how old your installation is. In fact I think the new version will be 40% faster compared to 2.0 if you use on your products 2 customfields in the average. Something like this.

Regarding the RC package, please read our wiki https://dev.virtuemart.net/projects/virtuemart/wiki
if you use GIT already, then the best is to learn how to pack your own package https://dev.virtuemart.net/projects/virtuemart/wiki/Create_virtuemart_installer
or follow the tutorial how to use svn directly on your localhost (should work with Git of course also) https://dev.virtuemart.net/projects/virtuemart/wiki/Setting_up_a_Development_Environment

[nrs]

Well, I got 15 custom fields (CF) i that shop (but no children).. Basically it is thing original supplier SKU, the purchase price, ... (Yes I did think about making an additional table but did choose to use the CF's)

So I will start to look closer at the new implementation..

-
Regarding the RC setup.. yes I could do it that way, but it would be easier if you nightly build engine had done that for me ;-)

--
PS. Please update the silver member workshop date... You link is pointing to a old event in November.

[Milbo]

Exactly, cause atm there is no new workshop set.

[lysov]

Well hear what's new in 2.2. But do not forget about a number of bugs in the current version. Many of them have a solution, but for some reason the developers keep them from one version to another over the years, simple example - http://forum.virtuemart.net/index.php?topic=99711.0.
For me, the transition from one version to another ("only update") is accompanied by applying of a dozen patches to get a working version and takes up to two weeks.
For this reason I (and not just me) and rarely updated VM, community loses testers and confidence in the VM falls.