Thanks for sorting that out, Kevin!
Sorry for dropping the ball on this one. I was under the impression that
infra had it enabled for us.
On 27/03/2019 1:30 am, Kevin Risden wrote:
gitpubsub was enabled and changes to gitbox calcite-site repo are live on
the site. The SVN repo should be read
gitpubsub was enabled and changes to gitbox calcite-site repo are live on
the site. The SVN repo should be read only now as well so we can't push to
the wrong one :)
Kevin Risden
On Tue, Mar 26, 2019 at 10:29 AM Michael Mior wrote:
> Thanks for tracking this Kevin!
>
> --
> Michael Mior
>
Thanks for tracking this Kevin!
--
Michael Mior
mm...@apache.org
Le mar. 26 mars 2019 à 08:18, Kevin Risden a écrit :
>
> Actually just followed up with infra. The gitpubsub hook should be enabled
> in the next ~hour or less when puppet runs. I will hold off on the SVN
> change and make sure the
Actually just followed up with infra. The gitpubsub hook should be enabled
in the next ~hour or less when puppet runs. I will hold off on the SVN
change and make sure the gitbox calcite-site repo is working.
Kevin Risden
On Tue, Mar 26, 2019 at 8:11 AM Kevin Risden wrote:
> Tried to push to
Tried to push to the new gitbox site last night for the 1.19.0 release and
ran into some issues. The gitpubsub hook was not setup so any changes to
calcite-site on gitbox are not reflected on the site. I pinged INFRA to get
this resolved.
I am going to push the changes to SVN as well to get the
@Michael, the svn repo will still be kept, but just unused. See kafka's
old site: https://svn.apache.org/repos/asf/kafka/site/
I have now pushed a the current working copy of our site to
https://github.com/apache/calcite-site using svn export.
I have also updated my ticket with infra to ask
Agreed, the history of the web site is not very important.
Julian
> On Feb 15, 2019, at 5:58 AM, Michael Mior wrote:
>
> I think we may want to keep the old SVN repository around if this is
> the case, but I personally don't have a problem with losing history in
> the new git repo. On a
I think we may want to keep the old SVN repository around if this is
the case, but I personally don't have a problem with losing history in
the new git repo. On a related note, it would be good to find a
process for the new repo that can work with a shallow clone so we
don't have to have the
Hey everyone,
I have now created the calcite-site repo in Gitbox. It is now available
via Github and the Gitbox endpoint, but currently empty.
I am currently trying to migrate the svn repo, but it is taking a very
long time and eventually timed out for me. A member of the ASF infra
team has
I have opened a request with INFRA to get the site moved to Gitbox [1].
[1] https://issues.apache.org/jira/browse/INFRA-17846
On 11/02/2019 9:00 pm, Francis Chuang wrote:
Hey all,
ASF project sites have the ability to use git instead of subversion as
their repository for web site content
The site will be in its own Git repo. See [1] for a list of other ASF
projects' sites in their own repo.
I will be updating the instructions once when the repo is moved. Once
the move is completed, there should be no changes to the existing
workflow for publishing the site, except for
I support this as long as (1) the site content remains in a separate repo from
the source code, and (2) the documentation gets updated.
(1) is important because the generated site is large and changes frequently,
and I don’t want to bloat the size of our source code repo (which gets copied
+1
Having one vcs to deal with, is good; automating the publication of the
site is great!
Στις Δευ, 11 Φεβ 2019 στις 8:00 μ.μ., ο/η Michael Mior
έγραψε:
> +1 for me as well and another +1 for automation if we can have this
> happen from the "site" branch.
> --
> Michael Mior
> mm...@apache.org
+1
On Mon, Feb 11, 2019 at 9:44 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:
> We also use it for PLC4X and it works flawlessly.
> +1
>
> Julian
>
> Am 11.02.19, 11:23 schrieb "Vova Vysotskyi" :
>
> Great idea! Drill website already uses gitbox [1]
>
> +1
>
> [1]
We also use it for PLC4X and it works flawlessly.
+1
Julian
Am 11.02.19, 11:23 schrieb "Vova Vysotskyi" :
Great idea! Drill website already uses gitbox [1]
+1
[1] https://gitbox.apache.org/repos/asf?p=drill-site.git
Kind regards,
Volodymyr Vysotskyi
Great idea! Drill website already uses gitbox [1]
+1
[1] https://gitbox.apache.org/repos/asf?p=drill-site.git
Kind regards,
Volodymyr Vysotskyi
On Mon, Feb 11, 2019 at 12:01 PM Francis Chuang
wrote:
> Hey all,
>
> ASF project sites have the ability to use git instead of subversion as
>
Francis> How do you guys feel about moving our site's repository from
svn to GitBox?
+1
Vladimir
Hey all,
ASF project sites have the ability to use git instead of subversion as
their repository for web site content [1]. It has been available since
2015 and appears to be quite stable. Quite a few other projects have
also moved their websites to git and subsequently, Gitbox (for using
18 matches
Mail list logo
