ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Tharp <joshua-th...@alumni.calpoly.edu>
Subject Re: is ivy dead?
Date Fri, 10 Jul 2009 22:48:46 GMT
Get lost Jeff.

On Fri, Jul 10, 2009 at 3:41 PM, Jeff Glatz <jdglatz@containerstore.com>wrote:

> interesting, since you work for Halliburton and they've stolen billions
> of dollars, i suppose the US taxpayer would be footing that bill...
>
> > -----Original Message-----
> > From: Shawn Castrianni [mailto:Shawn.Castrianni@halliburton.com]
> > Sent: Friday, July 10, 2009 5:26 PM
> > To: 'ivy-user@ant.apache.org'
> > Subject: RE: is ivy dead?
> >
> > I use ivy for my job and, therefore, any urgent issue or enhancement
> > can be resolved by offering paid development from the company's budget
> > to any of the ivy committers.  I am sure any of the ivy committers
> > would like to make some extra money.
> >
> > ---
> > Shawn Castrianni
> >
> > -----Original Message-----
> > From: Maarten Coene [mailto:maarten_coene@yahoo.com]
> > Sent: Friday, July 10, 2009 5:12 PM
> > To: ivy-user@ant.apache.org
> > Subject: Re: is ivy dead?
> >
> >
> > Hi Jim,
> >
> > I understand your frustration. I have the same feeling when I report
> > issues to some commercial products and never get a response.
> > But please keep in mind that Ivy is not a commercial product. The
> > developers of Ivy are not paid by Apache for their work on Ivy. This
> > means we do fix some bugs, commit some new features when we have some
> > free time to work on it.
> >
> > I can only speek for myself, but the last couple of months I didn't
> had
> > much free time left to work on Ivy. But I'm confident this will
> improve
> > in the near future...
> >
> > regards,
> > Maarten
> >
> >
> >
> >
> > ----- Original Message ----
> > From: Jim Newsham <jnewsham@referentia.com>
> > To: ivy-user@ant.apache.org
> > Sent: Tuesday, July 7, 2009 12:58:48 AM
> > Subject: Re: is ivy dead?
> >
> >
> > I share the same frustration.  It seems that bugs which were reported
> > months
> > ago have no assigned owner, no evaluation, and no activity...
> > regardless of
> > priority level.  Maybe a more sensitive way of rephrasing the question
> > is:
> > Is ivy being actively developed and maintained?  What is the
> > development
> > cycle?  Are maintenance fixes being made to released versions?  How
> > quickly
> > are bugs evaluated?  How quickly can we expect a major bug to be
> > fixed/released in a maintenance release?
> >
> > It's not that I feel a need to draw attention to the particular issues
> > that
> > I'm experiencing.  I've learned to work around those.  It's for the
> > community's benefit.
> >
> > Jim
> >
> > The issues that I've run into are:  retrieve with "sync" is broken
> > (IVY-1044); cleancache sometimes does NOT clean the cache (IVY-1080).
> >
> >
> > On Jun 22, 2009, at 4:50 PM, Alex Zhukov wrote:
> >
> > >
> > > Hello All,
> > >
> > > I opened a critical bug http://issues.apache.org/jira/browse/
> > > IVY-1087 on June 2, no reaction from developers. On June 15 I
> > > increased the priority to Blocker, still no reaction from
> > > developers. Can some one tell me if ivy project is dead or
> > > developers are not interested in maintaining it any more?
> >
> > This is an open source project. Sometimes activity is high, sometimes
> > not so high. Developers are on holidays or have a stressful time with
> > their day time project. Whatever.
> >
> > And obviously, looking at the mailing list you are using, this project
> > seems to be busy and far from dead. I can understand that it is
> > sometimes frustrating that an important issue is not fixed. But I
> > think it is not a nice style to play with the 'Is this project dead?'
> > phrase to raise attention for an issue. This is mud-slinging. I think
> > the fact that within the period of three weeks no one has commented on
> > a certain issue does not justify this at all.
> >
> >
> >
> >
> > ----------------------------------------------------------------------
> > This e-mail, including any attached files, may contain confidential
> and
> > privileged information for the sole use of the intended recipient.
> Any
> > review, use, distribution, or disclosure by others is strictly
> > prohibited.  If you are not the intended recipient (or authorized to
> > receive information for the intended recipient), please contact the
> > sender by reply e-mail and delete all copies of this message.
> ########################################################################
> "This email message, including any attachments, is for the sole use of the
> intended recipients and may contain confidential and privileged information.
>  Unauthorized use, disclosure or distribution of this email is strictly
> forbidden.  If you have received this message in error, please reply to the
> above sender notifying them of this error, and then kindly delete the
> message."
> ########################################################################
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message