Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <20060626230106.79113.qmail@web81603.mail.mud.yahoo.com>
Date: Mon, 26 Jun 2006 16:01:06 -0700 (PDT)
From: Jeff Levitt <derby@mylevita.com>
Subject: Re: [jira] Closed: (DERBY-460) Create error message documentation out
 of code
To: derby-dev@db.apache.org
In-Reply-To: <44A0606F.1040909@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


--- David Van Couvering <David.Vancouvering@Sun.COM>
wrote:

> I would like to support Andrew's suggestion, with a
> minor amendment. I 
> think it makes sense to run this for every snapshot
> as well as for the 
> release, to bring the messages up-to-date for the
> snapshot build.
> 
> David
> 
> Andrew McIntyre wrote:
> > On 6/26/06, Jeff Levitt <derby@mylevita.com>
> wrote:
> >> Ah I remember now, we wanted to get the DITA file
> >> correct for 10.1, and worry about the script
> later.
> >> Now that it's later, what do people think about
> using
> >> David's script in the nightly builds?  Is this
> >> something that is even possible?
> > 
> > -0.9
> > 
> > To integrate it into the doc build, the doc build
> would need to
> > guarantee that you have the latest build from the
> code tree available.
> > Currently the doc and code builds are not coupled
> together in any way.
> > I think the fact that the doc build is not
> dependent on the code build
> > is an advantage, especially for contributors who
> are just interested
> > in building the documentation.
> > 
> > Maybe this is something that could be done maybe
> once a release, or
> > whenever someone notices the doc and code have
> drifted apart
> > significantly.
> > 
> > andrew
> 


Sounds reasonable to me...

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com