db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: Recording published Maven 2 artifacts
Date Tue, 12 Oct 2010 11:52:06 GMT
Kristian Waagan <kristian.waagan@oracle.com> writes:

>  Hi,
>
> When I worked on the scripts generating and publishing the Maven 2
> artifacts, I added a release history to the maven2/README.txt
> file. This file exists on every branch.
> I did not think a lot about how this would work out as we publish new
> releases. Its only purpose is to serve as a record for artifacts
> released by the Derby community. I don't think Derby users will read
> it. Keeping it up to date on all branches seems like a drag. Here are
> some options, including the tedious one:
>
>   a) Update trunk, merge to all branches.
>   b) Update trunk, merge to release branch.
>      Merging may not work here, so we may have to simply update the
> file directly on both trunk and the release branch.
>   c) Update trunk only.
>
> I have chosen to always update trunk so that we have a place where we
> keep the full history.
>
> Any opinions on this?
> I'm leaning towards (c) for simplicity. I prefer to avoid (a).

Hi Kristian,

Of those three options, I agree that (b) and (c) sound like less work
than (a). But do we need to keep this in the repository? Perhaps a wiki
page would do? Then we'd only need to update the list a single place per
release.

You mentioned that users will probably not read the list. Is there any
reason why developers would read it? If not, we might just as well
remove it, since the release manager probably has enough tasks to
remember already.

-- 
Knut Anders

Mime
View raw message