Return-Path: 
 <dev-return-9596-apmail-beehive-dev-archive=beehive.apache.org@beehive.apache.org>
Delivered-To: apmail-beehive-dev-archive@www.apache.org
Received: (qmail 62896 invoked from network); 3 Nov 2006 04:06:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 3 Nov 2006 04:06:23 -0000
Received: (qmail 20225 invoked by uid 500); 3 Nov 2006 04:06:33 -0000
Delivered-To: apmail-beehive-dev-archive@beehive.apache.org
Received: (qmail 20196 invoked by uid 500); 3 Nov 2006 04:06:33 -0000
Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@beehive.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@beehive.apache.org>
List-Post: <mailto:dev@beehive.apache.org>
List-Id: <dev.beehive.apache.org>
Reply-To: "Beehive Developers" <dev@beehive.apache.org>
Delivered-To: mailing list dev@beehive.apache.org
Received: (qmail 20181 invoked by uid 99); 3 Nov 2006 04:06:33 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 20:06:33 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of carlin.rogers@gmail.com
 designates 66.249.82.239 as permitted sender)
Received: from [66.249.82.239] (HELO wx-out-0506.google.com) (66.249.82.239)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 20:06:19 -0800
Received: by wx-out-0506.google.com with SMTP id s7so274383wxc
        for <dev@beehive.apache.org>; Thu, 02 Nov 2006 20:05:59 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=i22q3KQ7qKA9R87MatFK31opfA44HvkdF2lDcoAhjcujGdMS6jsBPSADBc+7IqRq4wgexCOcyurSf1z3t3tLMkEH7XTP/+ykyQgPytSQ5Jl57yzM3Ggg6Qxov513t+qJuofBrcB1UqRy+XJchNchuF2rBmznH0FnK7+6Sxmwe98=
Received: by 10.90.105.19 with SMTP id d19mr859259agc.1162526759123;
        Thu, 02 Nov 2006 20:05:59 -0800 (PST)
Received: by 10.90.66.15 with HTTP; Thu, 2 Nov 2006 20:05:59 -0800 (PST)
Message-ID: <ba6911de0611022005n570fcd59y436a1b7908773151@mail.gmail.com>
Date: Thu, 2 Nov 2006 21:05:59 -0700
From: "Carlin Rogers" <carlin.rogers@gmail.com>
To: "Beehive Developers" <dev@beehive.apache.org>
Subject: Re: a new patch release [was: Re: Question about the next release...]
In-Reply-To: <ba6911de0611021816g55c6a940m8fa59072fa8be65f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <e9ac83540610232238m5df9741cjd53a2f5be4d3212e@mail.gmail.com>
	 <ba6911de0610240817s491cd27dl62f378e28862e26a@mail.gmail.com>
	 <ba6911de0611021816g55c6a940m8fa59072fa8be65f@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

Eddie,

I have another question about pulling the incomplete data grid
features from the branch. I should remove the "checkpoint work" you
did in the PagedDataSet class, etc. from revision 415150,
http://mail-archives.apache.org/mod_mbox/beehive-commits/200606.mbox/%3c20060618155232.DB13A1A983A@eris.apache.org%3e
as well as the work in revision 431515, right? Or, did you want me to
leave that in?

Thanks,
Carlin

On 11/2/06, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> Hey Eddie,
>
> I've made the initial branch and updated several reference of the
> release version number to 1.0.2. However, I have a couple of questions
> about some other files...
>
> - doap_Beehive.rdf -   I have not yet modified the DOAP. Do we just
> modify <revision> field and update the <created> field when we roll
> out the release, or just the version in trunk? Do we need to remove
> some of the references to WSM in this file or clarify that it is a
> subproject?
>
> - docs/maven-support.txt -   is this just a readme text file and
> should I update the versions at the bottom of the doc?
>
> - POMs -     looks like these use a property for the beehive version, correct?
>
> I haven't made any changes in beehive/site/... yet. I guess we wait
> until the release to update these.
>
> I'll start the work to remove incomplete data grid features in branch.
>
> Thanks for your help.
> Carlin
>
> On 10/24/06, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > Excellent and thanks Eddie. After Wednesday sounds fine. I'm also
> > happy to help if that makes it easier for you.
> >
> > Your idea of including the LICENSE file in all the jars sounds good as well.
> >
> > Kind regards,
> > Carlin
> >
> > On 10/23/06, Eddie O'Neil <ekoneil@gmail.com> wrote:
> > >   Sure -- that'd definitely help.  As my slow replies probably
> > > indicate, I've been busy with some other things and haven't been
> > > super-active recently.
> > >
> > >   There are several tasks that need to happen for release:
> > >
> > > - branching
> > > - remove incomplete data grid features in branch
> > > - update version numbers in the documentation, build, and POMs
> > > - create / sign release package
> > > - vote on release package
> > > - publish approved binaries / maven distributables / refreshed documentation
> > >
> > >   I'll be able to help with branching / data grid work after Wednesday
> > > and can take care of the release packaging / signing after that.  If
> > > you'd like to get started before then, take it away.  :)
> > >
> > >   One thing we should review is whether we need to include LICENSE
> > > files in all of our JARs.  My reading of this:
> > >
> > >   http://www.apache.org/dev/apply-license.html
> > >
> > > indicates that we don't strictly need to do this -- but other projects
> > > are currently doing this so that the JARs are self-describing outside
> > > the context of the distribution package.  I'd be in favor of doing
> > > this work.
> > >
> > > Eddie
> > >
> > > On 10/16/06, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > > > Hey Eddie,
> > > >
> > > > I could volunteer by creating the branch and backing out the changes,
> > > > if that would help.
> > > >
> > > > Are there other release tasks that you think some of us other folks in
> > > > the dev community should/could be doing?
> > > >
> > > > Kind regards,
> > > > Carlin
> > > >
> > > > On 10/16/06, Eddie O'Neil <ekoneil@gmail.com> wrote:
> > > > >   #1 wouldn't be a lot of work and is basically just a couple of
> > > > > changes to revert.  AFAICT, that's my task unless someone else wants
> > > > > to volunteer.  :)
> > > > >
> > > > >   The problem with shipping an incomplete feature is exposing
> > > > > unfinished and unfrozen APIs.  This means that the APIs could change
> > > > > in the future potentially breaking applications that used such
> > > > > features, and this doesn't seem desirable.
> > > > >
> > > > >   Plus, I tend to believe that patch releases should be as stable as
> > > > > possible to ensure continuity from a previously released version.
> > > > >
> > > > >   My $0.02.
> > > > >
> > > > > Eddie
> > > > >
> > > > >
> > > > >
> > > > > On 10/16/06, Scott Musser <scott.musser@gmail.com> wrote:
> > > > > > How much work would there be in option #1?
> > > > > > Naturally it would be cleaner than option #2 but I agree with Carlin that
> > > > > > either option would work.
> > > > > > Finishing the partial data set support could then be finished when you have
> > > > > > time rather than rushing.
> > > > > > Would the impact of shipping incomplete data set support be disagreeable to
> > > > > > the rest of the community?
> > > > > > It would be useful to understand what will the ramifications of shipping
> > > > > > this incomplete feature might be.
> > > > > >
> > > > > >
> > > > > > On 10/13/06, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > > > > > >
> > > > > > > Hey Eddie,
> > > > > > >
> > > > > > > Are you thinking there would be some API changes in what you have for
> > > > > > > the datagrid partial data set support to make it fully baked or just
> > > > > > > some clean up? I'm not a binding vote but I'd be good with either 1 or
> > > > > > > 2 (if there's nothing drastic in API changes for data set support).
> > > > > > >
> > > > > > > Carlin
> > > > > > >
> > > > > > > On 10/13/06, Eddie O'Neil <ekoneil@gmail.com> wrote:
> > > > > > > >   Hm -- a new release would be great except...
> > > > > > > >
> > > > > > > >   I've started new feature work in trunk/ for supporting partial data
> > > > > > > > sets; this work isn't baked / frozen yet.  Some options:
> > > > > > > >
> > > > > > > > #1) branch, remove the partial data set support, and ship 1.0.2
> > > > > > > > #2) ship partial data set support as-is in 1.0.2
> > > > > > > > #3) finish partial data set support and then ship 1.0.2
> > > > > > > >
> > > > > > > >   Thoughts?
> > > > > > > >
> > > > > > > > Eddie
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 10/5/06, Ken Tam <kentaminator@gmail.com> wrote:
> > > > > > > > > +1 for a 1.0.2 patch release
> > > > > > > > >
> > > > > > > > > On 10/2/06, Rich Feit <richfeit@gmail.com> wrote:
> > > > > > > > > > Agreed -- seems like 1.0.2 to me...
> > > > > > > > > > Rich
> > > > > > > > > >
> > > > > > > > > > Chad Schoettger wrote:
> > > > > > > > > > > It seems like a patch release to me.  We've fixed a lot of bugs --
> > > > > > > I
> > > > > > > > > > > know that in the controls area there have been a number of bugs
> > > > > > > fixed
> > > > > > > > > > > which were found by users using Beehive from within an IDE (many
> > > > > > > of
> > > > > > > > > > > them APT related).  Also bugs releated to security and deadlocks
> > > > > > > have
> > > > > > > > > > > been addressed as well.
> > > > > > > > > > >
> > > > > > > > > > > I think it would be a good thing to get these fixes into a patch
> > > > > > > > > > > release at this time.
> > > > > > > > > > >
> > > > > > > > > > >  - Chad
> > > > > > > > > > >
> > > > > > > > > > > On 9/28/06, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > > > > > > > > > >> I was wondering about the scheduling of the next beehive release.
> > > > > > > > > > >> There's been more than 65 bugs and improvements fixed along with
> > > > > > > a few
> > > > > > > > > > >> smaller new features. Some of these seem like good improvements
> > > > > > > on
> > > > > > > > > > >> 1.0.1 and worth getting out to the user community. This includes
> > > > > > > > > > >> things like a security fix and some page flow deadlock fixes as
> > > > > > > well.
> > > > > > > > > > >>
> > > > > > > > > > >> What are the thoughts on whether this would be a patch release (
> > > > > > > 1.0.2)
> > > > > > > > > > >> or a point release (1.1)? Just curious what folks where thinking
> > > > > > > and
> > > > > > > > > > >> getting a discussion started.
> > > > > > > > > > >>
> > > > > > > > > > >> Kind regards,
> > > > > > > > > > >> Carlin
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>