cvs commit: ports/net-im/openfire Makefile distinfo pkg-plist ports/net-im/openfire/files patch-build-build.xml

[Pietro Cerutti]

On 2011-Jan-12, 21:42, Peter Jeremy wrote:
> >In this particular case, openfire-3.7.0.beta seemed to my workable enough.
> 
> It may well be - after all, many of us are running 8-stable or
> 9-current, both of which are "beta" software.  And it could be that
> the "beta" designation relates to issues that do not affect the
> FreeBSD port.  But, IMHO, by taking this step, you are stating that
> openfire-3.7.0.beta is suitable for production use.

I think this is a very important point. Maybe this thread could be the
trigger to create a clear (and documented) policy about port suffixes and
production-readiness.

I can agree on:

myport/         <-- latest stable / production ready, maybe version 3.4
myport12/       <-- old, supported 1.2 version
myport21/       <-- old, supported 2.1 version
myport-devel/   <-- development branch, version 4.0.beta

Anybody from doc@ wants to write down a chapter for the handbook? :)

Best Regards,

-- 
Pietro Cerutti
The FreeBSD Project
gahr at FreeBSD.org

PGP Public Key:
http://gahr.ch/pgp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20110112/4318d17d/attachment.pgp