svn commit: r49068 - head/en_US.ISO8859-1/htdocs/news/status

Dru Lavigne dru at FreeBSD.org
Fri Jul 8 13:11:13 UTC 2016


Author: dru
Date: Fri Jul  8 13:11:12 2016
New Revision: 49068
URL: https://svnweb.freebsd.org/changeset/doc/49068

Log:
  Add GitLab status report submitted by tz at freebsd.org.
  
  Reviewed by: wblock
  Sponsored by: iXsystems

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml	Fri Jul  8 12:01:57 2016	(r49067)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml	Fri Jul  8 13:11:12 2016	(r49068)
@@ -848,4 +848,43 @@
 	machines.</task>
     </help>
   </project>
+
+  <project cat='ports'>
+    <title>Bringing GitLab into the Ports Collection</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Torsten</given>
+	  <common>Zühlsdorff</common>
+	</name>
+	<email>tz at FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://freshports.org/www/gitlab">GitLab port</url>
+      <url href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208793">PR: not starting on boot</url>
+    </links>
+
+    <body>
+      <p>After being in the &os; Ports Collection for three months,
+	GitLab continues to mature and gain adoption.  Most of its
+	starting problems have been resolved, with one known issue
+	left: it does not start on boot.  Any help in solving this
+	issue is welcome.</p>
+
+      <p>Staying in sync with upstream is now easy for minor versions.
+	But, some of the monthly major releases create a big workload
+	by introducing a number of new dependencies.  This makes
+	testing and updating an expensive process.</p>
+
+      <p>The GitLab project itself now mentions native support on
+	&os;, which is quite a commendation.</p>
+
+      <p>Current work aims to fix the open problems, get the latest
+	major version into the port, and create the documentation for
+	the update progress.</p>
+    </body>
+  </project>
 </report>


More information about the svn-doc-all mailing list