Re: Mandatory svnpubsub migration by Jan 2013

Hello Infra!

At the logging project most sub projects commit generated html to svn.
Going live is a matter of "svn up". Guess there is no problem to use
svnpubsub.

But there is one component (the upcoming log4j 2.0) which has started
with mvn site deploy. Is there a recommendation how combine this with
svnpubsub? The idea was to deploy to a local folder which is then
committed to svn. This would probably mean that a log4j2.0 website
update does mean a huge commit because most sources might be touched.
Is it a problem?

Cheers,
Christian

On Wed, Feb 8, 2012 at 1:26 PM, Joe Schaefer <joe_schaefer <at> yahoo.com> wrote:
> [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER
> INQUIRIES TO infrastructure <at> apache.org]
>
> FYI: infrastructure policy regarding website hosting has
> changed as of November 2011: we are requiring all websites
> and dist/ dirs to be svnpubsub or ASF CMS backed by the end of 2012.
> If your PMC has already met this requirement congratulations,
> you can ignore the remainder of this post.
>
> As stated on http://www.apache.org/dev/project-site.html#svnpubsub
> we are migrating our webserver infrastructure to 100% svnpubsub
> over the course of 2012.  If your site does not currently make
> use of this technology, it is time to consider a migration effort,

Log4J 2

As you may be aware I have been working on Log4j 2 for about 2 years now.  It now consists of a fairly large body of
code with fairly decent documentation. I feel it is ready to come out of my experimental branch and onto its
own main branch where others will hopefully feel more inclined to participate.  Although this shouldn't
surprise anyone and I could probably do this without forewarning, I consider it good manners to give
adequate notice.

Ralph

Moving from svn up to mvn site-deploy

Hello all,

over in log4php land we are pretty unhappy with the current site
situation. At the moment we generate, commit that site to svn and then
make a "svn up" in the logging directory. It was now 5 times in a row
(or even more often) that the permissions of files/folders like
subfolders or .svn are not correctly set. In one case we could not
even fix that ourselves.

I know infra would like to have static html pages in svn to restore
all pages in case of a crash. I think, we can easily generate and
upload them ourselves. In case of a crash, log4php'lers would care
themselves on restoring our homepage.

That being said, we want to remove the current procedure with svn up
as it is not working very well for us.

Instead we want to utilize mvn site-deploy for this task. Ivan has
already tested this on his people folder and all went well. I know
this task myself from Apache Commons and another non-apache lib I
develop.

Given there are no objections, we will change this whenever we have
the time, treating this mail as lazy consens.

Cheers
Christian

--

-- 
http://www.grobmeier.de

[ANNOUNCE] Apache log4php 2.2.0 released

Dear all,

The Apache log4php team is pleased to announce the release of Apache
log4php 2.2.0.

Significant changes in this release include:
 * a full rewrite of the configuration logic which greatly improves
error reporting
 * inline configuration using PHP arrays
 * a new web site with better documentation and more examples
 * a new layout: serialized

Release notes, including the full change, log can be found here:
http://logging.apache.org/log4php/changelog.html

The release is available from:
http://logging.apache.org/log4php/download.html

The site has just been updated so it may take a little while to sync.

Thanks to everyone who participated in the making of this release.

Best regards,
The Apache log4php team

Voting on Apache log4php 2.2.0

Hello everyone,

I'm pleased to announce that we're ready to release the next version
of log4php. The voting is open on the log4php dev list [1].

If anyone is willing to review the release and vote, you are most
welcome, especially since we are one PMC member vote short for making
the release.

[1] http://logging.apache.org/log4php/mail-lists.html

Best regards,
Ivan

[ANN] Apache log4net 1.2.11 Released

The Apache log4net team is pleased to announce the release of Apache
log4net 1.2.11.  The release is available for download at

        http://logging.apache.org/log4net/download.html

The Apache log4net library is a tool to help the programmer output log
statements to a variety of output targets.  log4net is a port of the
excellent Apache log4j framework to the Microsoft(R) .NET runtime.

log4net 1.2.11 is not only a bugfix release, it also adds support for
.NET 4.0 as well as the client profiles of .NET 3.5 and .NET 4.0.
See the release-notes at

    http://logging.apache.org/log4net/release/release-notes.html

for a full list of changes.

Starting with this release log4net uses a new strong name key but we
also provide a binary distribution using the "old" strong name key of
log4net 1.2.10 and earlier. See the FAQ at 

        http://logging.apache.org/log4net/release/faq.html#two-snks

for details.

The binary distributions no longer contain assemblies built for the
Compact Framework 1.0 or the Shared Source CLI - you can build those
yourself using the source distribution.

[VOTE] Release Apache log4net 1.2.11 based on RC1

It's been a long time since the last log4net release and we've
accumulated quite a few changes.  It is about time to cut a new release.

[scp dumped core on me repeatedly while I tried to copy the files to
     people.apache.org that's why I've temporarily put the ZIPs on my
     server.]

log4net 1.2.11 RC1 is available for review here:
  http://stefan.samaflost.de/log4net/

Details of changes since 1.2.10 are in the release notes:
  http://people.apache.org/~bodewig/log4net/site/release/release-notes.html

I have tested this with Mono and several .NET frameworks using NAnt.

The tag is here:
  https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.11RC1
  (revision 1179495)

Site:
  http://people.apache.org/~bodewig/log4net/site/

RAT Report:
  http://people.apache.org/~bodewig/log4net/site/rat-report.html

Votes, please.  This vote will close in 72 hours, 1900 GMT 9-Oct 2011

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...

Setting up a google analytics account

Hi all,

I would like to propose setting up a google analytics account for
monitoring access to logging.apache.org.

This has been discussed on @legal-discuss before, specifically by the
Jackrabbit devs [1]. The conclusion was that this is legally
acceptable if a privacy policy such as [2] is posted on the web site.
This was also confirmed in an ASF board meeting [3]. The relevant
extract being:

> * Henning to communicate that every project that uses Google Analytics
>   needs to have a published privacy policy.
>     Update:
>       henning: Jukka and legal-discuss pursued this and produced
>            http://jackrabbit.apache.org/privacy-policy.html,
>            which is great. I will send out mail later this week
>            to pmcs@ and remind them of this and that they have
>            to update their web sites if they are using GA. By
>            using this page as template, it should be easy.

Additionally, for better transparency, Jackrabbit devs decided to post
monthly generated analytics reports to the dev list. However, this
seems optional.

I have done some investigation, and it is possible to create a single
analytics account for the logging.apache.org domain and have multiple
profiles which would track individual sub-project sites [4]. This
would allow monitoring of both individual sites and the whole domain.

Including ASL code in an Apache project

KEYS file

Hi,

is <http://www.apache.org/dist/logging/KEYS> under revision control
anywhere?  I'd need to add my key sooner or later (or so I hope).

Stefan

mvn based log4net website

Hi all,

based in major parts on work done by Curt earlier and inspired by
log4php I've created a mvn site-plugin based version of the log4net
site.  The current result can be seen here
<http://people.apache.org/~bodewig/log4net/site/> and it should be very
similar to the existing site.

The major difference is that I've removed the list of contributors from
the landing page, the same list (with my name added) is available from
the "Project Team" page.

Other than that the site should comply with all branding requirements -
this means it has a few "Apache"s and "TM"s sprinkled all over the site
and a new footer on every page.  I've also fixed a few other JIRA issues
about broken links on the way.

I have not modified the download page as there is a reason it doesn't
use mirrors right now.  The only log4net releases that have ever been
made at the ASF are Incubator releases and the release artifacts have
never been moved under the logging dist area.  By now they have also
been removed from the incubator area.  This means they are not available
from www.apache.org at all (which also mean not from any mirror at all)
and all download links point to archives.apache.org.  This will be fixed
once we have our next release.

Unless anybody yells I plan to replace the current log4net site with the
directory linked above in a few days.

Stefan