It looks like we have won our first OpenACS project to provide an eCommerce site for one of our customers.

Is the eCommerce package on 5.0 and AOLserver 4 considered fit for a production environment or would I be better sticking to 4.6.3 and AOLs 3.x?

Does anyone have a production site running eCommerce on 5.0?

Am I being unnecessarily paranoid? All pearls of wisdom greatfully received.

  - Steve

Torben

Thanks for that. I should get a better idea after a meeting on Friday afternoon which should put some meat on the bones as far as timescales are concerned. I'd like to use 5 if I can as some of the new features such as localisation would be useful for this site. It also makes the upgrade path easier for future releases.

If I may I'll come back to you and Alfred after Friday when I know how much time we have and see if you think its enough to get a stable 5 out or if I should stick to 4.6.3

Thanks

  - Steve

Alfred

Thats good news as I'd like to use 5.0 if I can. It looks as if we now have two sites to do for this customer and the first is their corporate site which will be a pretty simple affair but still using OACS. The ecommerce site will follow fairly soon after that so I'd like to make a start on it as soon as possible.

Thanks

    - Steve

I held off for the 5.0(3?) release since it's not a core package, then there was chaos on HEAD with an acs-kernel update. I personally am back working on my ecommerce project, so I will post it in the next few days.

We've made several procedural changes recently that should allow package developers to work on and release their packages without being blocked by core releases or the state of core HEAD. See the latest instructions on how to do releases. If your package works with 5.0.x, and requires only other packages that also work with 5.0.x, you can release it at any time, regardless of HEAD and of the core release cycle. (One caveat - repository generation isn't automated yet - I need to set up a batch script to do that.)

Yes.  BCMS on the HEAD repository (http://openacs.org/repository/5-1) is at 0.3 but the version of BCSM tagged with openacs-5-0-compat, hence available in the 5.0 repository (http://openacs.org/repository/5-0), is 0.2.  The point of this is to ensure a stable working space, both in core and in the packages.  It is now the responsibility of individual package developers to verify that their packages work with specific versions of core and to tag the accordingly.  The test servers (http://test.openacs.org/test) should make this reasonably straightforward.

Code is committed. There may be lingering bugs - use the bugtracker.

There is not an upgrade script from 4.x yet. The required script would change one function and convert a lot of fields to timestamptz (at least for postgres).

I'm going to start working through the ecommerce bugs in bugtracker next.

Hi Joel,

I am sorry if the question is a bit dumb.  I didn't know we have to tag the package.  Maybe I missed the discussion.  I would like to have bcms to be used for atleast 5.1, can you point me to the right direction on how to do it?  Thanks.