Version 3 released, see comments

[tseven]

I'm in the process of doing a lot of re-theming and notice the repo cleared in preparation for v3. It would be helpful to know a rough ballpark estimate of when it will be ready for production.

Is v3 a complete re-write?

Thank you.

[ktwbc]

Hi, While I don't have an exact release date at this time, we are currently in our beta process so we aren't too far off. V3 is a brand new version built on Yii (yiiframework.com) so if you're doing custom work, it would probably be best to wait for this version and research the theme process on that framework. We'll have supplemental documentation at release as well for customization.

[limeyd]

any chance of having beta testing access as I to have some heavy customizations I'm in the middle of.

[Cabalist]

Any updates? Seems silly to just take all the code down...

[Cabalist]

And it's out. Are you going to update Github?

[ktwbc]

We will probably be closing the github repo. You can download the 3.0 version from http://downloads.xsilva.net/webstore/latest and if you need a zip you can get it from http://downloads.xsilva.net/webstore/latestzip

All information about customizing and programming are on the forums at https://lightspeedsupport.zendesk.com/categories/20099307-Web-Store-Customization/

[Cabalist]

Why close the guthub repo? I thought the new version remained open source?

[ktwbc]

Hi,

It's complete open, you can view anything in the source code you want and if you choose, modify (though we recommend implementing changes by properly extending classes an extensions as opposed to modifying the source code). The links above are for the source code.

If you're referring to accepting code change requests, which is what a lot of people mean when they think open source, we have had the forum for a year or so but really weren't receiving any submissions from others, so it wound up being our own development anyway. Additionally, becoming PCI compliant complicates open source because you can't arbitrarily accept code changes, they have to be done through a documented pipeline that github just isn't set up for.

As I said, it's something being evaluated at this point, so any comments are helpful to present to our dev management team on why maintaining a github repo would still be useful.

Kris

[Cabalist]

I guess it really is your guy's call on what tools you find the most effective but for me having things like a Commit history allows me to track changes much easier. On top of that fixes aren't limited to arbitrary releases. I can merge up to a particular commit or pinpoint one that has introduced an issue.

Your development was happening in public. People could cite and ask questions about the code. There are 561 closed issues that allowed people to submit bugs or see what were the areas you were working on. 'Open Source' is more than releasing a code blob sometimes, it is developing openly.

I liked how the webstore was one of the few things from Lightspeed I could watch develop. So much of the rest of it has very iffy documentation when it comes to issues.

I'm not going to tell you what to do but this repo was a way that you were supporting developers. Pulling this down eliminates another resource for us.

[ktwbc]

I went ahead and pushed up the builds. This is a squashed commit tree that we do, so one commit per tagged version, not individual commits but will show code changes version to version.

I can't guarantee long term what will happen but can keep this updated for now for feedback purposes.

[Cabalist]

We appreciate it. :)