I think it is now more than a year that I cannot find any version to update our outdated one ...\nall the changes under the hood are breaking the functionality. We don't really need a lot: projectdesigner import tasks parent/children/dynamic tasks need to work module installation calrndar due to the change in module syntax, I can't even bring my new modules into the old codebase. It feels a bit strange to rework the modules for old versions. Due to the calendar/event modification, it would be major work efford for one module. I feel somewhat desparate about being stuck with really old versions and the constant break of functionality that was working previously (e.g. I made the projectdesigner working in some pull requests some versions ago, now it is broken again). Keith, is it possible to stop core changes and development until we have a fully working version?\nAnd/or have a better distinction between a stable version that has only bug fixes and the development version?\nI tried to reset the current code base to the version 3.1 tag, but that doesn't get the functionality ok either (at least for projectdesigner, which does not work in 3.1 either). Unfortunately, my working version (I think it does all I mentioned above) is before the calendar/event change, so I cannot bring my adon modules into that (because the addon module mechnism changed between then and now). At the moment, I am really desparate about this (especially seeing that module uplod fix seems to be shifted to 4.0 version - so 3.2 will again be unusable for us, even if it solves all other problems - bug id 1449).

asked 01 Apr '14, 13:40

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

retagged 01 Aug '15, 12:42

I will freeze everything for v4.0 until these issues are resolved. My apologies for the struggle and problems.

(01 Apr '14, 22:39) caseydk ♦♦ caseydk's gravatar image

ok, thanks, that is a big relieve.
permanent link

answered 02 Apr '14, 01:36

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

answered 02 Apr '14, 01:36

What module are you having problems updating?

(05 Apr '14, 12:16) caseydk ♦♦ caseydk's gravatar image

this seems to be gone with the newest version, thanks

(06 Apr '14, 06:21) opto ♦ opto's gravatar image
Unfortunately, this stil holds: too many changes under the hood are breaking the functionality Whenever I try to upgrade, w2p is broken.\nJust trying to go from 3.2 to 3.3.66. Everytimes it is tons of testing to verify whether the Basic functionalities are not broken (YES, they are...) dynamic Tasks don't update, pull down with status in project list view does not unfold in IE, task per user doen't work for admin, resources: cannt assign to task, although there is a tab for resources in Tasks, risks: edit icon is missing in list, projectview did not use TZ aware times for tasks, fix is in HTMLhelper::createCell. All my js/jquery stuff in my own modules doesn't work any longer, etc. and so on. I thought we had agreed to put development into 4.x and only have bug Fixing in 3.x. I see so many changes that it is not surprising that things are broken.\nOn every update this creates load of superflous work, having to debug stuff that previously did work. PLEASE, Keith, do development elsewhere and let us have a branch which only holds bug fixes. See your comment of April 2, 2014 in this question. At the Moment, I will try to have something like mostly pure bugfixing in https://github.com/opto/web2project/tree/w2p_opto_after3.3.66, for whoever is interested, at least if I don't despair and stick with 3.2. Klaus
permanent link

answered 01 Aug '15, 12:39

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

answered 01 Aug '15, 12:39

I'm going to do some cleanup this week and package a 3.4 to take care of some of these things. My apologies once again.

(03 Aug '15, 14:09) caseydk ♦♦ caseydk's gravatar image

to be honest: better no cleanup for 3.4 at this point? Please do the cleanup in some other branch. Otherwise, the whole retesting is necessary again. From my previous experience, the restructuring just creates new issues, sometimes old issues come back in (maybe a git cherrypicking gone wrong?). I would really freeze 3.3.66 and ONLY do bugfixes. No more restructuring. Currently, it is really like doing development on a production branch. By the way, updatedynamics is broken, and Task_path_enumeration and importtasks as well. Will post a fix shortly Klaus

(04 Aug '15, 02:38) opto ♦ opto's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×8
×7
×7
×4
×2

question asked: 01 Apr '14, 13:40

question was seen: 445 times

last updated: 04 Aug '15, 02:38

powered by Bitnami OSQA