Date: Wed, 16 Dec 2015 01:52:38 -0800 From: Yuri <yuri@rawbw.com> To: =?UTF-8?Q?Torsten_Z=c3=bchlsdorff?= <mailinglists@toco-domains.de>, Matthew Seaman <matthew@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Gogs port: A painless self-hosted Git service Message-ID: <56713466.9090609@rawbw.com> In-Reply-To: <566E75C3.9090601@toco-domains.de> References: <566D38ED.7050406@rawbw.com> <566D5B3C.4040602@FreeBSD.org> <566E75C3.9090601@toco-domains.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/13/2015 23:54, Torsten Zühlsdorff wrote: > I did this often for different processes. I won't work on the issue > this year - there is do much open to do. > > But please write me a desired workflow and the needed requirements and > i will do this in the next year. Just 3 weeks to go :D This isn't a complete workflow, but here is an idea for port updates: Each port update or new port submission could become a pull request. Once the new pull request is created, system should launch poudriere builds for it for all required platforms, and append the notice that builds have started. Then append the build status. If it was successful, committer can just approve the change with one press of a button. I believe there is a way to do a two way sync between git and subversion. If at any point in time that port changes, the process has to be invalidated and restarted if the pull request is still mergeable, or submitter should be notified if it became unmergeable. This could simplify and expedite the process of committing of port changes. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56713466.9090609>