niallkp opened a new pull request, #1588:
URL: https://github.com/apache/metron/pull/1588
(no comment)
--
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-mai
niallkp merged PR #646:
URL: https://github.com/apache/usergrid/pull/646
--
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...@attic.apache.or
niallkp opened a new pull request, #646:
URL: https://github.com/apache/usergrid/pull/646
(no comment)
--
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-mai
niallkp merged PR #67:
URL: https://github.com/apache/mxnet-site/pull/67
--
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...@attic.apache.or
niallkp merged PR #569:
URL: https://github.com/apache/streams/pull/569
--
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...@attic.apache.org
niallkp opened a new pull request, #569:
URL: https://github.com/apache/streams/pull/569
(no comment)
--
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
niallkp merged PR #1:
URL: https://github.com/apache/polygene-website/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...@attic.apach
niallkp opened a new pull request, #1:
URL: https://github.com/apache/polygene-website/pull/1
(no comment)
--
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
niallkp opened a new pull request, #67:
URL: https://github.com/apache/mxnet-site/pull/67
(no comment)
--
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-mai
niallkp merged PR #1588:
URL: https://github.com/apache/metron/pull/1588
--
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...@attic.apache.or
niallkp merged PR #20:
URL: https://github.com/apache/hawq-site/pull/20
--
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...@attic.apache.org
niallkp opened a new pull request, #20:
URL: https://github.com/apache/hawq-site/pull/20
(no comment)
--
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
niallkp merged PR #2:
URL: https://github.com/apache/aurora-website/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...@attic.apache.
niallkp opened a new pull request, #2:
URL: https://github.com/apache/aurora-website/pull/2
ATTIC-234 Remove Google Analytics from Aurora Website
ATTIC-235 Fix Aurora Website Rendering Issues caused by the CSP (local copy
of bootstrap.min.css)
--
This is an automated message from the A
niallkp merged PR #2:
URL: https://github.com/apache/archiva-web-content/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...@attic.ap
niallkp opened a new pull request, #2:
URL: https://github.com/apache/archiva-web-content/pull/2
[ATTIC-234](https://issues.apache.org/jira/browse/ATTIC-234) Remove Google
Analytics from Archiva Website
--
This is an automated message from the Apache Git Service.
To respond to the message
dependabot[bot] opened a new pull request, #1584:
URL: https://github.com/apache/metron/pull/1584
Bumps commons-beanutils:commons-beanutils from 1.8.3 to 1.9.4.
[
from 3.2.13.RELEASE to 5.3.39.
Release notes
Sourced from https://github.com/spring-
dependabot[bot] opened a new pull request, #644:
URL: https://github.com/apache/usergrid/pull/644
Bumps
[org.springframework:spring-webmvc](https://github.com/spring-projects/spring-framework)
from 3.2.13.RELEASE to 6.1.14.
Release notes
Sourced from https://github.com/spring-proj
dependabot[bot] opened a new pull request, #643:
URL: https://github.com/apache/usergrid/pull/643
Bumps
[org.springframework:spring-context](https://github.com/spring-projects/spring-framework)
from 3.2.13.RELEASE to 6.1.14.
Release notes
Sourced from https://github.com/spring-pro
dependabot[bot] opened a new pull request, #639:
URL: https://github.com/apache/usergrid/pull/639
Bumps commons-io:commons-io from 2.4 to 2.14.0.
[
from 3.2.13.RELEASE to 6.0.23.
Release notes
Sourced from https://github.com/spring-project
dependabot[bot] opened a new pull request, #641:
URL: https://github.com/apache/usergrid/pull/641
Bumps org.apache.tomcat:tomcat-catalina from 7.0.84 to 9.0.99.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=or
dependabot[bot] opened a new pull request, #640:
URL: https://github.com/apache/usergrid/pull/640
Bumps org.apache.cassandra:cassandra-all from 2.1.14 to 3.0.31.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=o
dependabot[bot] opened a new pull request, #1587:
URL: https://github.com/apache/metron/pull/1587
Bumps org.apache.commons:commons-vfs2 from 2.1 to 2.10.0.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apa
dependabot[bot] opened a new pull request, #1585:
URL: https://github.com/apache/metron/pull/1585
Bumps commons-net:commons-net from 3.1 to 3.9.0.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons-net:comm
dependabot[bot] opened a new pull request, #1586:
URL: https://github.com/apache/metron/pull/1586
Bumps commons-io:commons-io from 2.5 to 2.14.0.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons-io:common
hboutemy merged PR #5:
URL: https://github.com/apache/attic/pull/5
--
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: general-unsubscr...@attic.apache.org
hboutemy commented on PR #5:
URL: https://github.com/apache/attic/pull/5#issuecomment-2812639854
this has been done in the first step of #1: no need to copy paste and ask
infra again
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
sebbASF commented on PR #5:
URL: https://github.com/apache/attic/pull/5#issuecomment-2812330369
The contents of the PR are fine, but changing the website publication needs
to be considered in the context of how the Attic repo and website are used by
other code.
--
This is an automated me
hboutemy opened a new pull request, #5:
URL: https://github.com/apache/attic/pull/5
IIUC, `output/` directory will be auto-detected as "Pelican output"
https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#pelican-sub-directories-for-static-output
fine for me as a repla
hboutemy merged PR #1:
URL: https://github.com/apache/attic/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: general-unsubscr...@attic.apache.org
hboutemy merged PR #4:
URL: https://github.com/apache/attic/pull/4
--
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: general-unsubscr...@attic.apache.org
hboutemy commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2811679058
I use `gh-pages` for years that does not have this subtility: perhaps it's
an `asf-site` extra feature I did not see in the sites I saw
given you provide PRs and it does not stop us for moving
sebbASF opened a new pull request, #4:
URL: https://github.com/apache/attic/pull/4
There will also need to be a manual clearup of the existing asf-site branch
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abo
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2807667002
I can provide PR to move the output, as I have tested it already in a fork.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
niallkp commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2807662641
Sorry @hboutemy, I agree with @sebbASF - better to have the generated site
in an _**/output**_ folder and maintain the _**.asf.yaml**_ file in the
_**asf-site**_ branch.
This is what most
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2807652612
The asf-site branch does not have a README.md; it would help to have one.
Does it really make sense to have to create that in a different branch?
--
This is an automated message from the
hboutemy commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2807611840
simply stop nitpicking: no, your detailed taste is not a must
I respected much, did a lot, it's going too far on too many details
--
This is an automated message from the Apache Git Service.
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2807590642
I am referring to the asf-site branch.
Generally, the website is stored in the content/ or output/ directory,
rather than at top level.
Doing so allows the root folder which contains .asf.ya
hboutemy commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2807335329
> This asf-branch is currently set up differently from most other projects.
we are clearly not looking at the same lines of
https://infra-reports.apache.org/#sitesource
> I think th
hboutemy commented on issue #3:
URL: https://github.com/apache/attic/issues/3#issuecomment-2807302315
as you know, we use Jira as primary issue tracking, no reason to change for
now (or conflate svn to Git for code migration with issue tracking)
if you know how to disable GH Issues, don't
hboutemy commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2803913998
configuration moved to the right location to get to asf-website branch: good
catch
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2804748349
This asf-branch is currently set up differently from most other projects.
Normally, the website data is rooted in a sub-directory of the branch, e.g.
content/ or output/
This allows
sebbASF opened a new issue, #3:
URL: https://github.com/apache/attic/issues/3
The REAME says Jira:
https://github.com/apache/attic/blob/1b8429a79370d6ea41366fa92ee57b641d6f5dcd/README.md?plain=1#L5
but issues are enabled for the repo.
Which is correct?
--
This is an a
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2804764646
I think the current layout is likely to be confusing for maintainers who are
used to the way other asf-site branches are set up.
e.g. if anyone tries to add a README directly to the site, i
hboutemy closed issue #2: Build script does not handle renames or deletions
URL: https://github.com/apache/attic/issues/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 uns
hboutemy closed pull request #1: publish asf-site branch
URL: https://github.com/apache/attic/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: gen
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2803245995
@Humbedooh So does the stanza need to be in the main branch at all?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
Humbedooh commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2803181148
1. yes, this would switch to publishing the website from the asf-site branch
of this repo
2. yes, this would override the existing svn checkout and set a marker to
prevent the original svn s
sebbASF commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2803198751
@Humbedooh Doesn't the publish stanza need to be added to the asf-site
branch for the publish to actually take place?
--
This is an automated message from the Apache Git Service.
To respond to
sebbASF opened a new issue, #2:
URL: https://github.com/apache/attic/issues/2
The build script:
https://github.com/apache/attic/blob/main/.github/workflows/build.yml
does not handle renames or deletions, unlike the existing Buildbot job
--
This is an automated message from th
Humbedooh commented on PR #1:
URL: https://github.com/apache/attic/pull/1#issuecomment-2803223743
You are right in that. The publish block needs to be present in the branch
that is published
--
This is an automated message from the Apache Git Service.
To respond to the message, please lo
53 matches
Mail list logo
