cvs commit: ports/net-im/openfire Makefile distinfo pkg-plist
gahr at gahr.ch
Tue Jan 11 12:56:17 UTC 2011
On 2011-Jan-11, 13:32, Alexandr Kovalenko wrote:
> P.S. I suppose _after_ 3.7.0 _stable_ release it may be acceptable to
> go 2 different ways:
> 1. Create net-im/openfire37 leaving alone net-im/openfire
> 2. Repocopy net-im/openfire to net-im/openfire36 and commit of 3.7.0
> into net-im/openfire with adding note in UPDATING
Well, when 3.7.0 is released (stable) I'll update net-im/openfire to
3.7.0 and mark net-im/openfire-devel as INGORE or DEPRECATED.
I don't think I'm going to maintain a backport of 3.6.0, but anyone is
free to create a net-im/openfire36 if they like.
> To clarify - I'm not against seeing 3.7.0 in net-im/openfire, but
> against -beta there or appear it there without notice in UPDATING at
> least, because 3.6.x and 3.7.x are not completely backward compatible.
UPDATING is used when upgrading a port requires special actions to be
carried out. I'd like it not to become a general replacement for Release
Notes or ChangeLog files. I.e., it is the user's resposibility to go
find out what a new release of a software brings in terms of
retro-compatibility, and what is needed to upgrade one's configuration.
Anyway I'll double-check the release notes and make sure to make the
transition as clean as possible for our users.
The FreeBSD Project
gahr at FreeBSD.org
PGP Public Key:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-ports/attachments/20110111/b93897ec/attachment.pgp
More information about the cvs-ports