On 20.10.10 18:41, Lily Wei wrote:
Kristian Waagan wrote:
> On 19.10.10 17:41, Rick Hillegas wrote:
[ snip ]
> There is one thing I'd like to nail down though, and that is what
the development community wants regarding the history section in
maven2/README.txt. My motivation for this is that the current
instructions are inaccurate and may cause a little extra hassle for
the release manager.
>
> Based on the discussion we have had in this thread, I propose two
options:
> a) update the version living on trunk, regardless of release branch
> b) remove it - leave no traces in the code repository of Maven
artifact deployment, we will have to consult the Apache staging
repository or the central Maven repository [1] to figure out what has
been published
>>
>> Since I have been working a little with the Maven stuff, I'm
comfortable with option (b). This will remove one small task for the
release manager, so I'm giving it my +1.
>+1 to reducing the complexity of our release process.
+1. It is so nice that you are working with the Maven stuff. :-)
Hi all,
I removed the history section from the readme-file (tracked the work
under DERBY-4865), and I also removed the item instructing the release
manager to update the file in
http://wiki.apache.org/db-derby/ReleasePublication .
--
Kristian
Thanks,
Lily
