Forum OpenACS Development: Plea to CVS committers

Collapse
Posted by Malte Sussdorff on
Would all CVS committers spend some time and commit all their own Open Patches?

If you are unsure what to do with a patch, create a forum discussion with a link to the bug and the patch. We can then decide whether we need to TIP the patch or not.

Once you are done and still have some spare minutes on your hands, can you take a look at patches from others and apply them as well, so we can bring the toolkit up to date with all the valuable contributions from the community.

It should not be the sole responsibility of the OCT to commit these patches.

Collapse
2: Re: Plea to CVS committers (response to 1)
Posted by Ben Koot on
Malte,

Wouldn't it be more effective to use the OACS download module to centralize these contributions. Right now the CVS comit is pretty difficult to find. All it takes is to set up to options. 1. Core distribution, 2. CVS

If we don't even use OACS modules to distribute the system, but resort to the current hobby approach, what are users supposed to think?

Cheers

ps. rant not to be taken personaly ofcourse 😉

Collapse
3: Re: Plea to CVS committers (response to 1)
Posted by Malte Sussdorff on
Ben, the point is that CVS committers *know* how to commit and if you have to download something we can go as well with the patches. The idea is that the core team does not have to go through 140 open patches, download them, test them and then put them back into CVS as this is where our code base is officially maintained and where we run the releases from.

This does not prevent anyone else from making a patch or providing something in the download area.

Collapse
4: Re: Plea to CVS committers (response to 1)
Posted by Ben Koot on
Ok I see. point taken