Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of rick.hillegas@oracle.com
 designates 141.146.126.69 as permitted sender)
Message-ID: <510C0718.7070601@oracle.com>
Date: Fri, 01 Feb 2013 10:19:04 -0800
From: Rick Hillegas <rick.hillegas@oracle.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US;
 rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: DERBY 10.9.2 release, was: DERBY 10.9.1.0 release
References: 
 <CAM+GMhWQWwcPcD1R1ct2EDbWjd_F36X36o2fCOHGzSJxkMe19A@mail.gmail.com>
	<510AB597.6010409@oracle.com>	<510BF6B5.3090508@sbcglobal.net>
 <CAM+GMhUX-kgVcBxxJ_985utu07abicfYk5Zn+JicXofPegvQnA@mail.gmail.com>
In-Reply-To: 
 <CAM+GMhUX-kgVcBxxJ_985utu07abicfYk5Zn+JicXofPegvQnA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Writing a concise set of release instructions is complicated by the 
following issues:

1) The release process is slightly different for each release branch.

2) The release process is slightly different depending on whether you're 
running on Unix or Windows.

I don't see how a single set of wiki-maintained instructions can be 
concise if the instructions have to include special cases for all of the 
variations caused by (1) and (2).

We may be able to address (1) partially by moving the release 
instructions off the wiki into the codeline. That way, each branch can 
be responsible for documenting its own release process. Unfortunately, 
branches live for a long time and it is hard to guarantee that the 
process will remain constant over the lifetime of a branch. That is 
because parts of the release process are affected by larger Apache 
processes which change over the lifetime of a branch.

I don't know what to do about (2). Maybe we need separate release 
instructions for Unix and Windows.