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

[Alexandr Kovalenko]

On Tue, Jan 11, 2011 at 10:13 AM, Pietro Cerutti <gahr at gahr.ch> wrote:
> On 2011-Jan-10, 20:33, Alexandr Kovalenko wrote:
>> Beta?
>>
>> May I ask, why this went into net-im/openfire port, but not to new
>> port net-im/openfire-devel ?
>
> Ok, I guess I owe an explanation here, since quite a few people have
> raised concerns about me committing a beta version to openfire/.
>
> I am personally against -devel ports. These tends to get marked as
> IGNORE or anyway no longer be valid after the -devel branch has turned
> to stable. I prefer to keep the latest available version in myport/,
> upon user request, keep previous (stable and maintained) versions in
> myport10, myport11, etc... See for example java/netbeans, java/netbeans5,
> java/netbeans55, java/netbeans61. This brings two advantages:
>
> - the cost of maintaining a previous version in myport10/ is ~= 0
> - the myport/ directory always contains the latest available version
>
> It is a porter's discretion to ponder wheter a particular release
> version is stable enough to get into the main myport/ directory.
>
> In this particular case, openfire-3.7.0.beta seemed to my workable enough.

Can you understand, that many of people use ports in production
systems (surprise!) and expect NO beta versions in non -devel ports,
no sudden breakage of their systems without any notice in UPDATING and
so on, whatever you personally think about that. Ports system is not
your personal sandbox/private branch of ports. It is what people use
on their production systems.

If you want to commit beta, you have 2 choices:

1. Wait until non-beta to commit.
2. Commit beta to -devel port after repocopy.

> Users have reported problems upgrading their configuration, and this is
> the reason for me requesting a repocopy to backport the previous version
> to openfire36.

Even if (although, I think it is totally incorrect) you really
wanted/it was needed to commit -beta version, you should have reversed
order of procedures:

1. Become aware of incompatibilities and problems
2. Repocopy of openfire to openfire36
3. Commit your -beta to openfire
4. ADD to UPDATING file note about this, because such change won't get

> I welcome any feedbacks on this matter.
>
> Best Regards,
>
>>
>> On Mon, Jan 3, 2011 at 2:36 PM, Pietro Cerutti <gahr at freebsd.org> wrote:
>> > gahr        2011-01-03 12:36:49 UTC
>> >
>> >  FreeBSD ports repository
>> >
>> >  Modified files:
>> >    net-im/openfire      Makefile distinfo pkg-plist
>> >  Removed files:
>> >    net-im/openfire/files patch-build-build.xml
>> >  Log:
>> >  - Update to 3.7.0.beta
>> >    Release notes: http://community.igniterealtime.org/blogs/ignite/2010/08/26/openfire-370-beta-is-released
>> >
>> >  Revision  Changes    Path
>> >  1.28      +4 -4      ports/net-im/openfire/Makefile
>> >  1.20      +2 -3      ports/net-im/openfire/distinfo
>> >  1.2       +0 -10     ports/net-im/openfire/files/patch-build-build.xml (dead)
>> >  1.14      +29 -2     ports/net-im/openfire/pkg-plist
>> > _______________________________________________
>> > cvs-all at freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/cvs-all
>> > To unsubscribe, send any mail to "cvs-all-unsubscribe at freebsd.org"
>> >
>>
>>
>>
>> --
>> Alexandr Kovalenko
>> http://uafug.org.ua/
>
> --
> Pietro Cerutti
> The FreeBSD Project
> gahr at FreeBSD.org
>
> PGP Public Key:
> http://gahr.ch/pgp
>



-- 
Alexandr Kovalenko
http://uafug.org.ua/