As one of the new guys, I can confirm that IRC is misleading and confusing. I
totally missed any topic regarding the "we moved to slack" part. Could've been
a bad IRC client, could've been me, not sure.
I agree with Bernd: New people would very much like to find slack information
on the
Thanks for bringing this to our attention and I agree we should remove the irc
channel in this case.
Not sure about the slack since I don’t use it, but the website is not only for
the public, it’s also the primary source for committers (but if we add the
slack we certainly need to mention who
Hi,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344271
There are still a couple of issues left in JIRA:
Hello all,
I have noticed it's misleading for new contributors to find out the proper
communication channel for this project. The documentation says there is an
IRC channel which topic says "we moved to Slack". Then, it takes some time
to figure out a newcomer cannot get in, since she has to be
michael-o commented on pull request #259:
URL: https://github.com/apache/maven-site/pull/259#issuecomment-915504649
Obrigado!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
michael-o merged pull request #259:
URL: https://github.com/apache/maven-site/pull/259
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
waldyrious opened a new pull request #259:
URL: https://github.com/apache/maven-site/pull/259
Just a one-character fix, but it was enough to confuse me for a bit.
:sweat_smile:
Since there's already a `site-deploy` phase in the built-in `site`
lifecycle, I thought perhaps there was
Sounds good Michael, thanks for the update.
Gary
On Sun, Sep 5, 2021, 12:50 Michael Osipov wrote:
> Gary, I plan to address open issues in the course of the next two weeks.
> Followed by week of testing by the community. If everything goes well I
> will call the vote by the end of this month.
michael-o edited a comment on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915321903
Question to reviews: Do we really need Sisu support for Maven 3.0.x? I'd
rather drop it and focus on 3.1.x+ only.
--
This is an automated message from
michael-o commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915321903
Question to reviews. Do we really need Sisu support for Maven 3.0.x? I'd
rather drop it and focus on 3.1.x+ only.
--
This is an automated message from the
michael-o commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915269142
Maven Deploy Plugin must be tested.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
slachiewicz merged pull request #45:
URL: https://github.com/apache/maven-artifact-transfer/pull/45
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
dependabot[bot] opened a new pull request #45:
URL: https://github.com/apache/maven-artifact-transfer/pull/45
Bumps [groovy](https://github.com/apache/groovy) from 3.0.8 to 3.0.9.
Commits
See full diff in https://github.com/apache/groovy/commits;>compare view
I have now created a Jira issue to move this forward:
https://issues.apache.org/jira/browse/MNG-7238
Regards,
Chris
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
cstamas commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915140926
> To me the change is too big to validate, so it must proof itself for the
several plugins out there that depend on it.
Ok, @slachiewicz tested with
rfscholte commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915137419
To me the change is too big to validate, so it must proof itself for the
several plugins out there that depend on it.
--
This is an automated message from the
cstamas commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-915128652
Any other comment? I'd like to merge or drop this, is lingering for way too
long...
--
This is an automated message from the Apache Git Service.
To respond to
Hi,
I hope someone from the maintainers can cut a new Maven Shade Plugin
release and initialise a new VOTE for Maven Shade Plugin version 3.3.0.
I checked the last voting thread
18 matches
Mail list logo
