[csw-maintainers] Ongoing projects

[Peter Bonivart]

2011/8/23 Maciej Bliziński <maciej at opencsw.org>:
> == Sendmail with largefile suport ==
>
> Contributors: Peter B
> Status: Ready for testing
> Missing: Testing. It's been sitting in experimental since July 2nd and I've had no feedback on my latest version (Jake Goerzen responded about file permissions which I fixed). I will probably do some kind of test suite myself and if it passes my needs I will release it.

^^^

> As a project, we'll be better off if we focus on one project at a time
> and get it finished, meaning, completed enough to be pushed out to the
> world.  This way, we deliver to our users.

I've been pushing that view to several of you for a long time, glad to
see someone else supporting it. It's obvious, both by your long list
above and by the almost two month long interruption in package
release, that we add tasks quicker than we complete them. Maybe we
should have some cap on how many tasks we have going at once?

Another problem is the size of the tasks and how they tend to grow.
Perl is one example where the last step of 64 bit is holding
everything up, we have open bugs and an obsolete version of Perl, I
think we should have fixed those issues and then continued on with 64
bit after that. Divide the tasks into steps that the users can benefit
from.

If I'm correct the release process task was previously stuck on
signing the catalogs, then on notifying someone when the signing
process stopped and now it has sucked in the package browser on the
web site and Mantis integration into its black hole. :) I'm wondering
if this couldn't have been done in steps so users could have gotten
updates by now? Was this discussed on the list or only between those
involved? I'm fine with people actually doing the work having more say
but by making stuff complex you also exclude people.

/peter