Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A58A11471 for ; Fri, 25 Jul 2014 09:34:17 +0000 (UTC) Received: (qmail 47459 invoked by uid 500); 25 Jul 2014 09:34:17 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 47337 invoked by uid 500); 25 Jul 2014 09:34:17 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 47326 invoked by uid 99); 25 Jul 2014 09:34:17 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jul 2014 09:34:17 +0000 Received: from localhost (HELO mail-wi0-f179.google.com) (127.0.0.1) (smtp-auth username britter, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jul 2014 09:34:17 +0000 Received: by mail-wi0-f179.google.com with SMTP id f8so653604wiw.0 for ; Fri, 25 Jul 2014 02:34:13 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.73.109 with SMTP id k13mr3363779wiv.11.1406280853450; Fri, 25 Jul 2014 02:34:13 -0700 (PDT) Received: by 10.194.201.168 with HTTP; Fri, 25 Jul 2014 02:34:13 -0700 (PDT) In-Reply-To: References: Date: Fri, 25 Jul 2014 11:34:13 +0200 Message-ID: Subject: Re: release vs. SNAPSHOT sites. From: Benedikt Ritter To: Commons Developers List Content-Type: multipart/alternative; boundary=f46d043891d9b975f304ff014661 --f46d043891d9b975f304ff014661 Content-Type: text/plain; charset=UTF-8 You're probably refering to the Dependency Information report, I've posted on the other thread. I think it would be sufficient to configure it to use the latest release (we already have this information in the properties used by the build plugin). Creating a documentation branch feels like a lot of overhead to me. I'm curious whether git would make this any easier, since working with branches is said to be easier in git. Benedikt 2014-07-23 1:07 GMT+02:00 Gary Gregory : > Hi All: > > Snapshots site are useless to users and somewhat useful to developers. > > It is nice to be able to republish a site at will to fix documentation bugs > _without_ releasing a new version. > > But, this is usually done by dragging along a SNAPSHOT version of > everything. > > What to do? > > We need to publish the current version of a component and keep it there, as > is. What about doc only changes? What if those fixes are Javadoc fixes? > Does not seem doable. > > We could have, on the side a SNAPSHOT site. > > That means two sites: RELEASE and SNAPSHOT. > > Thoughts? > > Gary > > -- > E-Mail: garydgregory@gmail.com | ggregory@apache.org > Java Persistence with Hibernate, Second Edition > > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter --f46d043891d9b975f304ff014661--