On 2023-08-22, Jason Guild wrote:
> I can confirm that in the not very distant past there were multiple
> people (including myself) who submitted pull requests for Ivy to both
> make improvements as well as address bugs. They were left to rot for
> far too long.
This is unfortunate. In a way this may have happened because nobody is
left around who'd be able to acually verify your changes. This is not
what it should have been, but it happened. And I'm not sure it wouldn't
happen again.
> It was frustrating to me that even a very simple patch required both a
> debate on its utility and then navigating pedantries on the coding
> approach before then taking nearly two years to get merged and
> incorporated into a release.
Ouch. And sorry for that.
> I feel that people who were trying to get started maintaining Ivy,
> like myself, were simply put off by unresponsive
> committers. Absolutely I understand there is a lacking in capacity of
> people to verify changes but the situation, at least with me, felt
> like simple gatekeeping.
It is good you say this, Jason. Believe me, it is not
gatekeeping. Nobody is around anymore who'd want to stand at the gate at
all.
And I'm not sure how to move forward. "giving the keys to people who
want them" sounds a lot simpler than it may be in the end.
> I would really appreciate an update site for Ivy though as I've
> wondered how I can upgrade my IDE, easily, to use Ivy 2.5.{1,2}.
> It would be great if the existing update site for IvyDE [0] could at
> least be updated for the artifacts we have.
I have built the 2.5.{1,2} releases. I have no idea what an update site
is and how to create one. OK, I do have a vague idea what it is, but
absolutely no idea how to create one.
If you (or anybody else) can coach me through the process of creating an
update site starting with a jar and nothing else, then I'm game. Being
able to verify the thing actually works would be great. Bonus points if
I don't need to install anything I wouldn't use otherwise.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
