ports/181836

Kevin Oberman rkoberman at gmail.com
Tue Dec 24 17:24:54 UTC 2013


On Tue, Dec 24, 2013 at 8:37 AM, Jay Borkenhagen <jayb at braeburn.org> wrote:

> Hi,
>
> Still no activity that I can see.
>
> Is this really the way the ports process is supposed to work, that
> even after a port's maintainer has put a fix in SVN we need to hope a
> committer notices it and takes action?  Sorry for being ignorant of
> the process -- I was just really hoping to be able to do some
> end-of-year admin tasks with this fixed port, and that's looking less
> promising now...
>
> Thanks.
>
>                                                 Jay B.
>

Hi, Jay. It's been a while!


No, it's not the way it is supposed to work, but in the real world, it
often is the way it does. And, since this is a volunteer operation, around
the time of Saturnalia,  when so many are away or busy with families
celebrating Christmas and the new year, it can get pretty slow trying to
get a bit of time from a committer.

In this case it took a month after the maintainer approved the fix before a
committer picked it up. Now that the committer has it, it will likely
actually get committed as soon as tjil gets back to work. (He picked it up
on Friday.)
-- 
R. Kevin Oberman, Network Engineer
E-mail: rkoberman at gmail.com


More information about the freebsd-ports mailing list