Mailing-List: contact dev-help@shindig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shindig.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 ddumont@us.ibm.com does not designate 192.147.106.25 as permitted sender)
In-Reply-To: 
 <CAHqirOivZTNmQ8AkmNki=R5DH4BcL8TNjxaqJHPqoB2rGXhzvg@mail.gmail.com>
References: <CB35E95F.A11E%matthewm@oclc.org>
	<OF3418CB7A.3C3441CA-ON87257986.001338EC-85257986.0014AD2D@us.ibm.com>
	<4F14029E.8020306@epfl.ch>
	<061EC03A-42F3-4B2B-A900-9467C17F62EB@chuwori.co.uk>
	<CAHqirOj9Pn1ZfT0Yk63mQDRCS4GmrgGG=7Z2TVHm4qDCu7byTw@mail.gmail.com>
	<CAKxJ6q1=hAKZfeb=L+wqzEFXBMHE4gQNc2cWzRGEps9SCq3Oww@mail.gmail.com>
 <CAHqirOivZTNmQ8AkmNki=R5DH4BcL8TNjxaqJHPqoB2rGXhzvg@mail.gmail.com>
To: dev@shindig.apache.org
Cc: aed13@cornell.edu
MIME-Version: 1.0
Subject: Re: Shindig 3.0 timeline
From: "Dan Dumont" <ddumont@us.ibm.com>
Message-ID: 
 <OF4CC70B90.EF3B2653-ON85257990.005A654E-85257990.005A8977@notesdev.ibm.com>
Date: Wed, 25 Jan 2012 11:28:54 -0500
Content-Type: multipart/alternative;
 boundary="=_alternative 005A895685257990_="

--=_alternative 005A895685257990_=
Content-Type: text/plain; charset="US-ASCII"

Paul, 

I'd like to address some of the JIRAs (close or reassign), but it appears 
that I cannot modify or close JIRAs that I have not created.
Is there a way for me to get this power?   Or do I need to hunt down the 
people who created them and ask them to assign them or close them?


From:   Paul Lindner <lindner@inuus.com>
To:     dev@shindig.apache.org, aed13@cornell.edu, 
Date:   01/25/2012 03:57 AM
Subject:        Re: Shindig 3.0 timeline


Hi Folks.

I started a little housekeeping for 3.0.0:

http://goo.gl/cBNk0

Please add or modify bugs so we only have release blockers that have a
definitive fix.  Feel free to bump to 3.1.0 which is the next version we
can work on.


If you need/want higher-level Jira access let me know.


On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis 
<andrewedavis@gmail.com>wrote:

> Paul,
>
> Our team is reviewing the list of open JIRAs as requested, and I think 
we
> will have a response back to you on Monday or tuesday.
>
> I think it would be much more predictable for the community and 
dependent
> products, if we published a schedule for locking down 3.0, with some one
> or two release candidates planned over a few weeks, as I suspect many
> team's like ours have been in active development and need some time to
> review test coverage before we declare a 3.0 GA.
>
> Aside from the 3.0 immediate release, it would also be helpful to 
publish a
> regular release plan, maybe with a fixed annual schedule like Eclipse?
>  Thoughts?
>
> --Andrew Davis
> IBM
>
> On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <lindner@inuus.com> wrote:
>
> > I'm not keen on version numbers myself.
> >
> > We can release at any time really, code is stable, tests are all 
green.
> >
> > If someone wants to sign up to do maint releases of 3.0.x that would 
be
> > helpful.
> >
> > Vote:
> >  Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
> >
> >  [  ] +1 do it
> >  [  ] +0 meh
> >  [  ] -1 I have just one more patch.
> >
> > If you do -1 please provide code-review links or jira issues you 
consider
> > blockers for 3.0.0
> >
> > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <derek@chuwori.co.uk>
> > wrote:
> >
> > > Hi,
> > > Didn't catch a reply to this?
> > > Could you tell me when stable shindig 3.0 is due for public release?
> > >
> > > Thanks
> > > Derek
> > >
> > >
> > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > >
> > > > Hello,
> > > >
> > > > when the shindig 3.0 is due?
> > > >
> > > > Best
> > > > Evgeny
> > >
> > >
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> >
>


-- 
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner


--=_alternative 005A895685257990_=--