quarterly branches and transition to post-pkg_* [was: svn commit: r364739 - in head: . sysutils sysutils/syslog-ng-devel sysutils/syslog-ng-devel/files]
John Marino
freebsd.contact at marino.st
Fri Aug 15 06:20:25 UTC 2014
On 8/13/2014 09:55, John Marino wrote:
> On 8/13/2014 09:45, Alexey Dokuchaev wrote:
>> [*] Well, there are quarterly branches if one wants it to feel like Debian
>> stable without the quality control; IMHO they are of no use and should
>> be ignored altogether.
>
>
> In concept the quarterly branches are a good idea. Execution is a
> different matter.
>
> #1 issue: There's no portsnap with quarterly branches
> #2 issue: backporting fixes to quarterly branch, the process is a PITA
> #3 issue: There's no basic integrity check (e.g. freeze) before branching
>
>
> We have a huge problem looming: The pkg_* tools are going to be removed,
> maybe as soon as 1 September.
>
> I think the following should happen:
> 1) A version of portsnap be modified and added to the ports tree before
> then, a version that is quarter-branch capable
> 2) Waiting until 2014Q4 before removing pkg_* tools, which means at
> least wait until Oct 1.
> 3) Encourage everyone that has no intention to move to pkgng immediately
> to switch to the 2014Q4 branch
> 4) Maintain security updates to 2014Q4 branch for 6 months instead of
> the normal 3 months
> 5) Get the updated portsnap into base
>
> And eventually make quarterly branches the norm and working on head "at
> your own risk".
>
>
> Right now I see no plan for the post-pkg_* transition and the absence of
> one is pretty scary. You guys should consider my proposal above or
> something similar.
>
>
> John
Should I re-post this in developers@?
Or does everyone think providing an outlet for those that can't adjust
to pkg_* tools removal by 1 Sept is unnecessary?
John
More information about the svn-ports-all
mailing list