Re: Website Build + Release

[Thomas Nadeau]

Cool. Lets work together on this, so that more than 1 person learns how 
this works. 8)

—Tom


> On Dec 7, 2017, at 6:51 PM, Arthur Berezin  wrote:
> 
> I can pick this one up.
> 
> Arthur
> 
> On Thu, Dec 7, 2017, 17:13 John D. Ament  wrote:
> 
>> Tom,
>> 
>> I don't know how to do this, so I'd recommend someone else jump in to take
>> care of it.  I would recommend as an immediate step to update the website
>> with the 0.1.1 release docs to avoid downloading the release on each build.
>> 
>> John
>> 
>> On Thu, Dec 7, 2017 at 5:06 AM Thomas Nadeau  wrote:
>> 
>>> John,
>>> 
>>> Can I help you with this or is this something you can do quickly?
>>> 
>>> --Tom
>>> 
>>> 
>>> On Wed, Dec 6, 2017 at 10:01 PM, Arthur Berezin 
>>> wrote:
>>> 
 John, +1.
 
 Let's update the aria's release process to push  sphynx update on Aria
 releases.
 
 The reason the website is currently pulling the release docs and not
>> the
 other way around is because we published the docs right after we
>> released
 0.1.1 and didn't want to introduce changes in that point in time.
 
 Arthur.
 
 On Wed, Dec 6, 2017, 16:58 Thomas Nadeau 
>> wrote:
 
> 
> 
>> On Dec 6, 2017, at 4:40 PM, John D. Ament 
 wrote:
>> 
>> Tom,
>> 
>> Based on what I'm seeing, you're getting the current release
>> (0.1.1).
> I'm
>> not seeing anything that pulls the current master into the site.
>> 
>> I would recommend that we push from the build to the website,
>> rather
 than
>> have the website pull this information in.
> 
>Ok. Ill take a look shortly.
> 
>—Tom
> 
> 
>> 
>> John
>> 
>> On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau <
>> tnadeaua...@gmail.com>
> wrote:
>> 
>>> We use 2 tools to generate the website: Jekyll (html) and spynx
 (docs),
> and
>>> both tools generate outputs based on the latest code.
>>> 
>>> --Tom
>>> 
>>> 
>>> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament <
>>> johndam...@apache.org>
>>> wrote:
>>> 
 All,
 
 I'm troubleshooting from yesterday's identified website issues.
>>> One
>>> thing
 I noticed is that as a part of the website build, we download our
>>> release.
 Why is that?
 
 John
 
>>> 
> 
> 
 
>>> 
>> 

Re: Website Build + Release

[Arthur Berezin]

I can pick this one up.

Arthur

On Thu, Dec 7, 2017, 17:13 John D. Ament  wrote:

> Tom,
>
> I don't know how to do this, so I'd recommend someone else jump in to take
> care of it.  I would recommend as an immediate step to update the website
> with the 0.1.1 release docs to avoid downloading the release on each build.
>
> John
>
> On Thu, Dec 7, 2017 at 5:06 AM Thomas Nadeau  wrote:
>
> > John,
> >
> > Can I help you with this or is this something you can do quickly?
> >
> > --Tom
> >
> >
> > On Wed, Dec 6, 2017 at 10:01 PM, Arthur Berezin 
> > wrote:
> >
> > > John, +1.
> > >
> > > Let's update the aria's release process to push  sphynx update on Aria
> > > releases.
> > >
> > > The reason the website is currently pulling the release docs and not
> the
> > > other way around is because we published the docs right after we
> released
> > > 0.1.1 and didn't want to introduce changes in that point in time.
> > >
> > > Arthur.
> > >
> > > On Wed, Dec 6, 2017, 16:58 Thomas Nadeau 
> wrote:
> > >
> > > >
> > > >
> > > > > On Dec 6, 2017, at 4:40 PM, John D. Ament 
> > > wrote:
> > > > >
> > > > > Tom,
> > > > >
> > > > > Based on what I'm seeing, you're getting the current release
> (0.1.1).
> > > > I'm
> > > > > not seeing anything that pulls the current master into the site.
> > > > >
> > > > > I would recommend that we push from the build to the website,
> rather
> > > than
> > > > > have the website pull this information in.
> > > >
> > > > Ok. Ill take a look shortly.
> > > >
> > > > —Tom
> > > >
> > > >
> > > > >
> > > > > John
> > > > >
> > > > > On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau <
> tnadeaua...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> We use 2 tools to generate the website: Jekyll (html) and spynx
> > > (docs),
> > > > and
> > > > >> both tools generate outputs based on the latest code.
> > > > >>
> > > > >> --Tom
> > > > >>
> > > > >>
> > > > >> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament <
> > johndam...@apache.org>
> > > > >> wrote:
> > > > >>
> > > > >>> All,
> > > > >>>
> > > > >>> I'm troubleshooting from yesterday's identified website issues.
> > One
> > > > >> thing
> > > > >>> I noticed is that as a part of the website build, we download our
> > > > >> release.
> > > > >>> Why is that?
> > > > >>>
> > > > >>> John
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: Website Build + Release

[John D. Ament]

Tom,

I don't know how to do this, so I'd recommend someone else jump in to take
care of it.  I would recommend as an immediate step to update the website
with the 0.1.1 release docs to avoid downloading the release on each build.

John

On Thu, Dec 7, 2017 at 5:06 AM Thomas Nadeau  wrote:

> John,
>
> Can I help you with this or is this something you can do quickly?
>
> --Tom
>
>
> On Wed, Dec 6, 2017 at 10:01 PM, Arthur Berezin 
> wrote:
>
> > John, +1.
> >
> > Let's update the aria's release process to push  sphynx update on Aria
> > releases.
> >
> > The reason the website is currently pulling the release docs and not the
> > other way around is because we published the docs right after we released
> > 0.1.1 and didn't want to introduce changes in that point in time.
> >
> > Arthur.
> >
> > On Wed, Dec 6, 2017, 16:58 Thomas Nadeau  wrote:
> >
> > >
> > >
> > > > On Dec 6, 2017, at 4:40 PM, John D. Ament 
> > wrote:
> > > >
> > > > Tom,
> > > >
> > > > Based on what I'm seeing, you're getting the current release (0.1.1).
> > > I'm
> > > > not seeing anything that pulls the current master into the site.
> > > >
> > > > I would recommend that we push from the build to the website, rather
> > than
> > > > have the website pull this information in.
> > >
> > > Ok. Ill take a look shortly.
> > >
> > > —Tom
> > >
> > >
> > > >
> > > > John
> > > >
> > > > On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau 
> > > wrote:
> > > >
> > > >> We use 2 tools to generate the website: Jekyll (html) and spynx
> > (docs),
> > > and
> > > >> both tools generate outputs based on the latest code.
> > > >>
> > > >> --Tom
> > > >>
> > > >>
> > > >> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament <
> johndam...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> All,
> > > >>>
> > > >>> I'm troubleshooting from yesterday's identified website issues.
> One
> > > >> thing
> > > >>> I noticed is that as a part of the website build, we download our
> > > >> release.
> > > >>> Why is that?
> > > >>>
> > > >>> John
> > > >>>
> > > >>
> > >
> > >
> >
>

Re: Website Build + Release

[Thomas Nadeau]

John,

Can I help you with this or is this something you can do quickly?

--Tom


On Wed, Dec 6, 2017 at 10:01 PM, Arthur Berezin  wrote:

> John, +1.
>
> Let's update the aria's release process to push  sphynx update on Aria
> releases.
>
> The reason the website is currently pulling the release docs and not the
> other way around is because we published the docs right after we released
> 0.1.1 and didn't want to introduce changes in that point in time.
>
> Arthur.
>
> On Wed, Dec 6, 2017, 16:58 Thomas Nadeau  wrote:
>
> >
> >
> > > On Dec 6, 2017, at 4:40 PM, John D. Ament 
> wrote:
> > >
> > > Tom,
> > >
> > > Based on what I'm seeing, you're getting the current release (0.1.1).
> > I'm
> > > not seeing anything that pulls the current master into the site.
> > >
> > > I would recommend that we push from the build to the website, rather
> than
> > > have the website pull this information in.
> >
> > Ok. Ill take a look shortly.
> >
> > —Tom
> >
> >
> > >
> > > John
> > >
> > > On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau 
> > wrote:
> > >
> > >> We use 2 tools to generate the website: Jekyll (html) and spynx
> (docs),
> > and
> > >> both tools generate outputs based on the latest code.
> > >>
> > >> --Tom
> > >>
> > >>
> > >> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament 
> > >> wrote:
> > >>
> > >>> All,
> > >>>
> > >>> I'm troubleshooting from yesterday's identified website issues.  One
> > >> thing
> > >>> I noticed is that as a part of the website build, we download our
> > >> release.
> > >>> Why is that?
> > >>>
> > >>> John
> > >>>
> > >>
> >
> >
>

Re: Website Build + Release

[Arthur Berezin]

John, +1.

Let's update the aria's release process to push  sphynx update on Aria
releases.

The reason the website is currently pulling the release docs and not the
other way around is because we published the docs right after we released
0.1.1 and didn't want to introduce changes in that point in time.

Arthur.

On Wed, Dec 6, 2017, 16:58 Thomas Nadeau  wrote:

>
>
> > On Dec 6, 2017, at 4:40 PM, John D. Ament  wrote:
> >
> > Tom,
> >
> > Based on what I'm seeing, you're getting the current release (0.1.1).
> I'm
> > not seeing anything that pulls the current master into the site.
> >
> > I would recommend that we push from the build to the website, rather than
> > have the website pull this information in.
>
> Ok. Ill take a look shortly.
>
> —Tom
>
>
> >
> > John
> >
> > On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau 
> wrote:
> >
> >> We use 2 tools to generate the website: Jekyll (html) and spynx (docs),
> and
> >> both tools generate outputs based on the latest code.
> >>
> >> --Tom
> >>
> >>
> >> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament 
> >> wrote:
> >>
> >>> All,
> >>>
> >>> I'm troubleshooting from yesterday's identified website issues.  One
> >> thing
> >>> I noticed is that as a part of the website build, we download our
> >> release.
> >>> Why is that?
> >>>
> >>> John
> >>>
> >>
>
>

Re: Website Build + Release

[Thomas Nadeau]

> On Dec 6, 2017, at 4:40 PM, John D. Ament  wrote:
> 
> Tom,
> 
> Based on what I'm seeing, you're getting the current release (0.1.1).  I'm
> not seeing anything that pulls the current master into the site.
> 
> I would recommend that we push from the build to the website, rather than
> have the website pull this information in.

Ok. Ill take a look shortly.

—Tom


> 
> John
> 
> On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau  wrote:
> 
>> We use 2 tools to generate the website: Jekyll (html) and spynx (docs), and
>> both tools generate outputs based on the latest code.
>> 
>> --Tom
>> 
>> 
>> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament 
>> wrote:
>> 
>>> All,
>>> 
>>> I'm troubleshooting from yesterday's identified website issues.  One
>> thing
>>> I noticed is that as a part of the website build, we download our
>> release.
>>> Why is that?
>>> 
>>> John
>>> 
>> 

Re: Website Build + Release

[John D. Ament]

Tom,

Based on what I'm seeing, you're getting the current release (0.1.1).  I'm
not seeing anything that pulls the current master into the site.

I would recommend that we push from the build to the website, rather than
have the website pull this information in.

John

On Wed, Dec 6, 2017 at 8:59 AM Thomas Nadeau  wrote:

> We use 2 tools to generate the website: Jekyll (html) and spynx (docs), and
> both tools generate outputs based on the latest code.
>
> --Tom
>
>
> On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament 
> wrote:
>
> > All,
> >
> > I'm troubleshooting from yesterday's identified website issues.  One
> thing
> > I noticed is that as a part of the website build, we download our
> release.
> > Why is that?
> >
> > John
> >
>

Re: Website Build + Release

[Thomas Nadeau]

We use 2 tools to generate the website: Jekyll (html) and spynx (docs), and
both tools generate outputs based on the latest code.

--Tom


On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament  wrote:

> All,
>
> I'm troubleshooting from yesterday's identified website issues.  One thing
> I noticed is that as a part of the website build, we download our release.
> Why is that?
>
> John
>

Website Build + Release

[John D. Ament]

All,

I'm troubleshooting from yesterday's identified website issues.  One thing
I noticed is that as a part of the website build, we download our release.
Why is that?

John