Home
The Toolkit for Online Communities
17516 Community Members, 0 members online, 2030 visitors today
Log In Register
OpenACS Home : Forums : OpenACS Development : danger: HEAD changed for TIP#42,43 - could be unstable : One Message

Forum OpenACS Development: Re: danger: HEAD changed for TIP#42,43 - could be unstable

Collapse
Posted by Lars Pind on
My inclination would be to roll back these changes and postpone to 5.2.

I think the changes implement some very important and desired functionality, but it comes at a great risk to our 5.1 release.

Here's why:

- We need to ship frequently, so people can take advantage of the rapid pace of improvements to our software (software is useless unless you ship it).

- We have decided to cut scope when required to meet release targets, due to our limited resources (can't just throw more bodies at the problem).

- This commit is huge, destabilizing, is 5 days late, it breaks installation, and is likely to introduce many more subtle bugs down the road.

- It's my impression that at the point right before this commit, 5.1/HEAD was fairly stable, and could be tested, stabilized, and released relatively quickly.

- This has to do with the fact that, aside from this particular change, 5.1 was mostly a simple, incremental upgrade, with no radical changes. I would like to keep it that way.

Therefore, I'm going to suggest at the OCT meeting tonight that we roll back this commit, and focus all efforts (hopefully including Timo's) on stabilizing and releasing a 5.1 release as quickly as absolutely possible.

Ideally, we want all community effort to go into shipping 5.1, rather than fixing and playing with Timo's new changes. So perhaps we could ask Timo to work privately for another week or so, until install, upgrade, test cases, and cursory browsing works again, then commit.

This would also help break our expensive (in time, resources, frustration) habit of committing broken functionality.

Then this much desired change can go in as soon as we have branched, and Timo and all effort can go towards stabilizing and taking advantage of this change.

I do want to stress that I'm grateful to Timo for doing this important piece of work. I see these changes as critical to OpenACS going forward, and it's great to see the enthusiasm and confidence and ability to getting it done. Thanks, Timo!

/Lars