Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Nov 2006 04:27:14 GMT
From:      Nakata@FreeBSD.org, Maho<maho@FreeBSD.org>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/105195: repocopy request openoffice.org-2.0 -> openoffice.org-2 openoffice.org-2-RC, openoffice.org-2.0-devel -> openoffice.org-2-devel
Message-ID:  <200611060427.kA64REDD049512@www.freebsd.org>
Resent-Message-ID: <200611060430.kA64UPvF072526@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         105195
>Category:       ports
>Synopsis:       repocopy request openoffice.org-2.0 -> openoffice.org-2 openoffice.org-2-RC, openoffice.org-2.0-devel -> openoffice.org-2-devel
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 06 04:30:25 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Nakata, Maho
>Release:        
>Organization:
FreeBSD.org
>Environment:
>Description:
1. Next version of OpenOffice.org 2.1 and not 2.0.5
This proposal has been accepted by OOo community.
http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=9716
http://wiki.services.openoffice.org/wiki/OOoRelease205
> OOo 2.1 (formerly known as 2.0.5)
Then the next version of 2.1 will be 2.2 etc. we have changed the
version number scheme.

2. Necessity of RC port.
Currently, I commit release candidates onto editors/openoffice.org-2.0,
namely
2.0.3->2.0.4-RC1->2.0.4-RC2->...>2.0.4-RC3->2.0.4
however from 2.0.4-RC1 to filnal release, it takes very long. (RC1: 2006/9/5, and release 2006/10/13)
RC1: 
http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=9837
Release announce
http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=301
While the release cycle of OOo, we always have possibly unstable
OOo (that's why they are release candidates ;) ) in the stable
(released) ooo. Force the users to have unstable OOo longer than
one month is absolutely unacceptable. Thus I decided to split
openoffice.org-2.0 port into two ports, one is ordinal one and
the other is for release candidates.
>How-To-Repeat:

>Fix:
repocopy request:
editors/openoffice.org-2.0 -> editors/openoffice.org-2, editors/openoffice.org-2-RC
editors/openoffice.org-2.0-devel -> editors/openoffice.org-2-devel
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611060427.kA64REDD049512>