I've been trying to address the new project branding requirements at the same.
Otherwise, we'd be needed to do a refresh of at least the web site in a few
months. Stumbled through with extras looking for a path, but should be able to
apply it to the other companions pretty quickly.
You could look at the changes that I made on extras in the release push and try
to apply the same concepts to the other companions
svn diff -r \{2010-11-01\}:HEAD
http://svn.apache.org/repos/asf/logging/log4j/companions/extras/trunk >
release.diff
should get you a cumulative patch for the changes in the extras push. Should
be a good checklist for things that need to be checked in the other release. I
always forget to put the anticipated release date in src/changes/changes.xml
Then the BUILD-INFO doc in the log4j walks through the release prep and site
deployment setup.
If you don't beat me too it, I should be able to get at least one other
companion release candidate up over the weekend when I call the vote on extras
and move to the distribution servers.
On Nov 16, 2010, at 8:07 PM, Scott Deboy wrote:
> The Receivers companion has a dependency on Extras & Component, but Component
> only depends on log4j.
>
> Are there any objections to me building a release candidate for the Component
> companion prior to the Extras companion release?
>
> I haven't built a release candidate before but I have set up gpg2 and I now
> have a key..
>
> Curt, do you mind providing the steps you went through to build the Extras
> companion, just to help save me from having to build a ton of release
> candidates while I learn the process? I assume most of the heavy lifting was
> performed by the maven release plugin.
>
> Thanks
>
> Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
