Status reports - why not regularly?

[Erwin Lansing]

On Tue, Jan 13, 2004 at 07:32:50PM +0100, Kirill Ponomarew wrote:
> Hi,
> 
> On Tue, Jan 13, 2004 at 01:28:27PM -0500, Jonathan T. Sage wrote:
> > Exactally, and as Mark pointed out, I think that keeping in changes to 
> > the ports infrastructure (bsd.ports.mk) would be an excellent idea.
> 
> Yes, I think portmgr@ should mail to ports@ and explain the
> most important updates to bsd.*.mk
> 
I am working on a plan to document major changes in about the same style
as for src. That is, a file /usr/src/CHANGES with important information
to developers (bsd.*.mk and port changes that affect a lot of other
porss) and adding a section to Release Notes on the web site with
information to ports users.


-- 
                    _._     _,-'""`-._
Erwin Lansing      (,-.`._,'(       |\`-/|    erwin at lansing.dk
http://droso.org       `-.-' \ )-`( , o o)    erwin at FreeBSD.org
                    -bf-      `-    \`_`"'-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040113/98c4591c/attachment.bin