Hi Justin,
Thanks for the response, but that's the answer I'm pretty sure everyone
here figured and somewhat perpendicular to the question.
If the other option is chosen, would that cause that much trouble that it
blocks a release?
When it comes to branding, I'm assuming the general brand not ex
Justin, to get more information about the nightlies server, the initial
setup of pekko, and configuring the rsync credentials in the pekko
repositories, do I just message the users@infra list?
On Thu, Nov 3, 2022 at 10:11 AM Sean Glover wrote:
> Thanks. Apache's nightlies repo looks like the per
Hi,
“org.apache.pekko” would be the preferred name from an ASF branding and legal
point of view.
Kind Regards,
Justin
-
To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
For additional commands, e-mail: dev-h...@pekko.apa
danischroeter closed issue #10: Update templates for pull requests
URL: https://github.com/apache/incubator-pekko/issues/10
--
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 u
danischroeter commented on issue #10:
URL: https://github.com/apache/incubator-pekko/issues/10#issuecomment-1304651665
Resolved with #14
--
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 specif
danischroeter opened a new issue, #22:
URL: https://github.com/apache/incubator-pekko/issues/22
We should provide some automated migration that users of akka can use that
adapts their codebase to use pekko.
This migration should automatically
* adapt the dependencies
* in sbt
I concur, if there's formal rules that would likely lead to release
blocking, there's not much use in discussion.
So 2nd the motion.
Could someone which wields the power of release shed some light on whether
omitting org.apache from the java package name would be grounds for a
negative vote, noti
While effective, it doesn't feel quite right.
The dev list should be consumable, without needing to resort to that.
I fear it's also causing noise towards IPMC/mentors, which e.g. have not
responded to the package name discussion.
On Sat, Nov 5, 2022, 18:12 Sean Glover wrote:
> In the meantime
seglo merged PR #19:
URL: https://github.com/apache/incubator-pekko/pull/19
--
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: dev-unsubscr...@pekko.apache
pjfanning opened a new pull request, #20:
URL: https://github.com/apache/incubator-pekko/pull/20
Rename some modules. Aim is to cover other modules like discovery,
persistence and streams in a later PR.
Expecting to have to iterate quite a bit even with this number of modules.
--
T
mdedetrich merged PR #18:
URL: https://github.com/apache/incubator-pekko/pull/18
--
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: dev-unsubscr...@pekko.a
seglo opened a new pull request, #19:
URL: https://github.com/apache/incubator-pekko/pull/19
Despite its name this build doesn't actually publish anything (except for
test reports). It just runs some more verbose testing around cluster, artery,
and some other things. We'll need to add the
In the meantime I'm using a gmail filter for this list: (
to:dev@pekko.apache.org) -(from:g...@apache.org)
On Sat, Nov 5, 2022 at 6:13 AM Greg Methvin wrote:
> Sure, "commits" for commit notifications and "notifications" for all other
> notifications sounds fine to me.
>
> On Sat, Nov 5, 2022 at
pjfanning merged PR #3:
URL: https://github.com/apache/incubator-pekko/pull/3
--
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: dev-unsubscr...@pekko.apac
pjfanning merged PR #1:
URL: https://github.com/apache/incubator-pekko/pull/1
--
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: dev-unsubscr...@pekko.apac
mdedetrich opened a new pull request, #18:
URL: https://github.com/apache/incubator-pekko/pull/18
This PR is a follow up from https://github.com/apache/incubator-pekko/pull/2
but only contains the replacement of sbt check with github actions. It also
implements the git ratcheting system so
mdedetrich merged PR #17:
URL: https://github.com/apache/incubator-pekko/pull/17
--
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: dev-unsubscr...@pekko.a
mdedetrich opened a new pull request, #17:
URL: https://github.com/apache/incubator-pekko/pull/17
Adds a `.git-blame-ignore-revs` file which can be setup on a per project
basis so that git blame ignores scalafmt commits (see
https://akrabat.com/ignoring-revisions-with-git-blame/). I have ad
pjfanning merged PR #14:
URL: https://github.com/apache/incubator-pekko/pull/14
--
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: dev-unsubscr...@pekko.ap
mdedetrich merged PR #2:
URL: https://github.com/apache/incubator-pekko/pull/2
--
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: dev-unsubscr...@pekko.apa
pjfanning opened a new issue, #16:
URL: https://github.com/apache/incubator-pekko/issues/16
There were probably be a number of iterations.
In projects/Publish.scala:
```
override lazy val projectSettings = Seq(
publishTo := Some(akkaPublishTo.value),
publishRsyncH
pjfanning opened a new pull request, #1:
URL: https://github.com/apache/incubator-pekko-connectors/pull/1
Relates to https://github.com/apache/incubator-pekko/issues/15
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use t
Sure, "commits" for commit notifications and "notifications" for all other
notifications sounds fine to me.
On Sat, Nov 5, 2022 at 2:29 AM PJ Fanning wrote:
> 'commits' is one of the standard mailing lists added for all projects.
> I suggest we keep that for commit tracking.
>
> 'notifications'
pjfanning opened a new pull request, #4:
URL: https://github.com/apache/incubator-pekko-http/pull/4
Relates to https://github.com/apache/incubator-pekko/issues/15
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
pjfanning commented on PR #3:
URL:
https://github.com/apache/incubator-pekko-http/pull/3#issuecomment-1304464709
accidentally created the branch on the apache repo - I will restart this PR
using a branch on my fork
--
This is an automated message from the Apache Git Service.
To respond t
pjfanning closed pull request #3: remove mima checks
URL: https://github.com/apache/incubator-pekko-http/pull/3
--
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,
pjfanning opened a new pull request, #3:
URL: https://github.com/apache/incubator-pekko-http/pull/3
Relates to https://github.com/apache/incubator-pekko/issues/15
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
pjfanning opened a new issue, #15:
URL: https://github.com/apache/incubator-pekko/issues/15
* when we change the package names, then the mima binary compatibility
checks will fail anyway
* we are also likely to start releasing as v1.0.0 meaning that the old Akka
version numbers will be o
'commits' is one of the standard mailing lists added for all projects.
I suggest we keep that for commit tracking.
'notifications' is a mailing list used by a lot of teams for Github
notifications - eg
https://lists.apache.org/list.html?notificati...@linkis.apache.org
I'd prefer to use names for
pjfanning merged PR #13:
URL: https://github.com/apache/incubator-pekko/pull/13
--
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: dev-unsubscr...@pekko.ap
30 matches
Mail list logo
