date:20200804

Re: The project website

2020-08-04 Thread Matt Sicker

I meant they support building your site from source automatically via
Pelican similar to how GitHub supports Jekyll sources to generate the
HTML from. Since we generate the HTML manually from Maven, you can use
either service as they both support static contents. It's only a
difference if we were using another system for generating the site.

On Tue, 4 Aug 2020 at 10:00, Gary Gregory  wrote:
>
> On Tue, Aug 4, 2020 at 10:56 AM Matt Sicker  wrote:
>
> > See also the asf-site and asf-staging branches for an Infra-supported
> > site publishing system:
> > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> >
> > Seems to work fairly similar to a gh-pages branch, though they offer
> > Pelican instead of Jekyll. Though since Commons sites are all
> > statically generated from Maven, it doesn't matter which you use as
> > you can simply commit the output files to one of those special
> > branches.
> >
>
> Hi Matt,
>
> I was not planning on changing how we deal with component sites, just the
> Commons site itself. Or am I missing something?
>
> Personally, I also don't want to use Jekyl/Pelican, I'd prefer to go
> straight to GitHub.
>
> Gary
>
>
> >
> > On Tue, 4 Aug 2020 at 08:57, Gary Gregory  wrote:
> > >
> > > HI Andrew,
> > >
> > > I think we use both CMS and Buildbot if that makes any sense [1], but
> > > whatever it is, it's no longer working [2][3], so I'm happy to switch.
> > >
> > > I see GitHub pages as an option, so why not go with that.
> > >
> > > Commons its own site obviously but it also has a lot of components each
> > > with their own site. Each component site does not use CMS, it is
> > published
> > > manually as part of a release.
> > >
> > > So this migration should only apply to the Commons site and not component
> > > sites, right?
> > >
> > > Gary
> > >
> > > [1] https://commons.apache.org/site-publish.html
> > > [2] https://ci.apache.org/builders/commons-site-staging
> > > [3] https://issues.apache.org/jira/browse/INFRA-20632
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore 
> > wrote:
> > >
> > > > Hi:
> > > >
> > > > I am part of the Infrastructure team, and am writing to ask whether
> > your
> > > > project is still using the Apache CMS for your project website. As you
> > > > know, the CMS is reaching end-of-life, and we need projects to move
> > their
> > > > websites onto a different option within the next few weeks.
> > > >
> > > > There are several alternatives available, including those listed on
> > this
> > > > page [1] on managing project websites. Infra is assembling a Wiki page
> > [2]
> > > > on migrating a website from the CMS, and is looking forward to helping
> > > > projects with this transition.
> > > >
> > > > Please let me know whether your site is still on the Apache CMS and,
> > if so,
> > > > who will be the project point-of-contact with Infra for the migration.
> > > >
> > > > Thank you!
> > > >
> > > >
> > > >
> > > >
> > > > [1] https://infra.apache.org/project-site.html
> > > >
> > > > [2]
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andr...@apache.org
> > > >
> > > > <
> > > >
> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > > >
> > > > Virus-free.
> > > > www.avast.com
> > > > <
> > > >
> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > > >
> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >
> >
> >
> >
> > --
> > Matt Sicker 
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >



-- 
Matt Sicker 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: The project website

2020-08-04 Thread Gary Gregory

On Tue, Aug 4, 2020 at 10:56 AM Matt Sicker  wrote:

> See also the asf-site and asf-staging branches for an Infra-supported
> site publishing system:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
>
> Seems to work fairly similar to a gh-pages branch, though they offer
> Pelican instead of Jekyll. Though since Commons sites are all
> statically generated from Maven, it doesn't matter which you use as
> you can simply commit the output files to one of those special
> branches.
>

Hi Matt,

I was not planning on changing how we deal with component sites, just the
Commons site itself. Or am I missing something?

Personally, I also don't want to use Jekyl/Pelican, I'd prefer to go
straight to GitHub.

Gary


>
> On Tue, 4 Aug 2020 at 08:57, Gary Gregory  wrote:
> >
> > HI Andrew,
> >
> > I think we use both CMS and Buildbot if that makes any sense [1], but
> > whatever it is, it's no longer working [2][3], so I'm happy to switch.
> >
> > I see GitHub pages as an option, so why not go with that.
> >
> > Commons its own site obviously but it also has a lot of components each
> > with their own site. Each component site does not use CMS, it is
> published
> > manually as part of a release.
> >
> > So this migration should only apply to the Commons site and not component
> > sites, right?
> >
> > Gary
> >
> > [1] https://commons.apache.org/site-publish.html
> > [2] https://ci.apache.org/builders/commons-site-staging
> > [3] https://issues.apache.org/jira/browse/INFRA-20632
> >
> >
> >
> >
> >
> > On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore 
> wrote:
> >
> > > Hi:
> > >
> > > I am part of the Infrastructure team, and am writing to ask whether
> your
> > > project is still using the Apache CMS for your project website. As you
> > > know, the CMS is reaching end-of-life, and we need projects to move
> their
> > > websites onto a different option within the next few weeks.
> > >
> > > There are several alternatives available, including those listed on
> this
> > > page [1] on managing project websites. Infra is assembling a Wiki page
> [2]
> > > on migrating a website from the CMS, and is looking forward to helping
> > > projects with this transition.
> > >
> > > Please let me know whether your site is still on the Apache CMS and,
> if so,
> > > who will be the project point-of-contact with Infra for the migration.
> > >
> > > Thank you!
> > >
> > >
> > >
> > >
> > > [1] https://infra.apache.org/project-site.html
> > >
> > > [2]
> > >
> > >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > >
> > >
> > > --
> > > Andrew Wetmore
> > > Technical Writer-Editor
> > > Infra
> > > *Apache Software Foundation*
> > > andr...@apache.org
> > >
> > > <
> > >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > >
> > > Virus-free.
> > > www.avast.com
> > > <
> > >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > >
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
>
>
>
> --
> Matt Sicker 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: The project website

2020-08-04 Thread Matt Sicker

See also the asf-site and asf-staging branches for an Infra-supported
site publishing system:
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features

Seems to work fairly similar to a gh-pages branch, though they offer
Pelican instead of Jekyll. Though since Commons sites are all
statically generated from Maven, it doesn't matter which you use as
you can simply commit the output files to one of those special
branches.

On Tue, 4 Aug 2020 at 08:57, Gary Gregory  wrote:
>
> HI Andrew,
>
> I think we use both CMS and Buildbot if that makes any sense [1], but
> whatever it is, it's no longer working [2][3], so I'm happy to switch.
>
> I see GitHub pages as an option, so why not go with that.
>
> Commons its own site obviously but it also has a lot of components each
> with their own site. Each component site does not use CMS, it is published
> manually as part of a release.
>
> So this migration should only apply to the Commons site and not component
> sites, right?
>
> Gary
>
> [1] https://commons.apache.org/site-publish.html
> [2] https://ci.apache.org/builders/commons-site-staging
> [3] https://issues.apache.org/jira/browse/INFRA-20632
>
>
>
>
>
> On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore  wrote:
>
> > Hi:
> >
> > I am part of the Infrastructure team, and am writing to ask whether your
> > project is still using the Apache CMS for your project website. As you
> > know, the CMS is reaching end-of-life, and we need projects to move their
> > websites onto a different option within the next few weeks.
> >
> > There are several alternatives available, including those listed on this
> > page [1] on managing project websites. Infra is assembling a Wiki page [2]
> > on migrating a website from the CMS, and is looking forward to helping
> > projects with this transition.
> >
> > Please let me know whether your site is still on the Apache CMS and, if so,
> > who will be the project point-of-contact with Infra for the migration.
> >
> > Thank you!
> >
> >
> >
> >
> > [1] https://infra.apache.org/project-site.html
> >
> > [2]
> >
> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
> >
> > <
> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > >
> > Virus-free.
> > www.avast.com
> > <
> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >



-- 
Matt Sicker 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: The project website

2020-08-04 Thread Gary Gregory

HI Andrew,

I think we use both CMS and Buildbot if that makes any sense [1], but
whatever it is, it's no longer working [2][3], so I'm happy to switch.

I see GitHub pages as an option, so why not go with that.

Commons its own site obviously but it also has a lot of components each
with their own site. Each component site does not use CMS, it is published
manually as part of a release.

So this migration should only apply to the Commons site and not component
sites, right?

Gary

[1] https://commons.apache.org/site-publish.html
[2] https://ci.apache.org/builders/commons-site-staging
[3] https://issues.apache.org/jira/browse/INFRA-20632





On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore  wrote:

> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
>
> There are several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
>
> Please let me know whether your site is still on the Apache CMS and, if so,
> who will be the project point-of-contact with Infra for the migration.
>
> Thank you!
>
>
>
>
> [1] https://infra.apache.org/project-site.html
>
> [2]
>
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

The project website

2020-08-04 Thread Andrew Wetmore

Hi:

I am part of the Infrastructure team, and am writing to ask whether your
project is still using the Apache CMS for your project website. As you
know, the CMS is reaching end-of-life, and we need projects to move their
websites onto a different option within the next few weeks.

There are several alternatives available, including those listed on this
page [1] on managing project websites. Infra is assembling a Wiki page [2]
on migrating a website from the CMS, and is looking forward to helping
projects with this transition.

Please let me know whether your site is still on the Apache CMS and, if so,
who will be the project point-of-contact with Infra for the migration.

Thank you!




[1] https://infra.apache.org/project-site.html

[2]
https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS


-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: JDK 15 is in Rampdown Phase One

2020-08-04 Thread Gary Gregory

On Tue, Aug 4, 2020 at 5:44 AM Rory O'Donnell 
wrote:

> Hi Gary,
>
> I checked with dev team, we are not planning to backport the fix into
> JDK15.
>

Rory,

That is disappointing but good to know. Thank you for keeping us updated.

Gary



>
> Rgds,Rory
>
> On 31/07/2020 15:26, Gary Gregory wrote:
> > On Fri, Jul 31, 2020 at 10:18 AM Rory O'Donnell >
> > wrote:
> >
> >> On 31/07/2020 14:49, Gary Gregory wrote:
> >>> On Fri, Jul 31, 2020 at 5:53 AM Rory O'Donnell <
> rory.odonn...@oracle.com
> >>>
> >>> wrote:
> >>>
>  Hi Xeno,
> 
>  The issue is resolved in JDK 16 EA build 8, (JDK-8248655
>  ) which is
> available
>  on jdk.java.net.
> 
>  Rgds,Rory
> 
> >>> Hi Rory,
> >>>
> >>> Thank you for the update. The latest Java 16 EA builds Apache Commons
> >> Lang
> >>> OK now. We'll have to see when Travis-CI and GitHub Actions provide
> >> updates.
> >> Good to hear.
> >>> What should our expectations be for Java 15? That build is still broken
> >> for
> >>> us, even with build 34 (latest EA).
> >> What's the impact to you, we are very late in the cycle for JDK 15.
> >>
> > Hi Rory,
> >
> > We rely upon Travis-CI and GitHub Action to build and validate GitHub
> PRs.
> >
> > As for now, Java 15 builds always fail because of this issue. We've
> defined
> > these CI build jobs to allow for Java 15 builds to fail to provide us
> with
> > green builds otherwise.
> >
> > But we do not know if a Java 15 build has failed solely because of this
> > single issue or if there are additional compatibility issues, without
> > searching through the build logs, which frankly is too much of a pain to
> do
> > for every single PR that comes in.
> >
> > In effect, for me, at least, this means that I ignore Java 15 builds
> since
> > I know they always fail.
> >
> > Thank you,
> > Gary
> >
> >
> >> Rgds,Rory
> >>
> >>> Thank you!
> >>> Gary
> >>>
> >>>
>  On 30/06/2020 09:36, Xeno Amess wrote:
> > Great, thanks!
> >
> > Rory O'Donnell  > > 于2020年6月30日周二 下午4:25写道：
> >
> >   Hi Xeno,
> >
> >   The bug has moved into the Java Bug System (JBS) - JDK-8248434
> >   
> >
> >   I have added the "apache-maven-found" label to the bug.
> >
> >   Rgds,Rory
> >
> >   On 26/06/2020 13:18, Rory O'Donnell wrote:
> >>   Thanks Xeno!
> >>
> >>   Will let you know if anything else required.
> >>
> >>   Rgds,Rory
> >>
> >>   On 26/06/2020 13:15, Xeno Amess wrote:
> >>>   Hi.
> >>>   I submitted the bug(or issue) on bugs.java.com
> >>>     
> >>>     as you requested.
> >>>   And it said internal review ID : 9065633. on the wabpage.
> >>>   If there anything else I should do please let me know.
> >>>
> >>>   Rory O'Donnell  >>>   
> >>>   
> >>>   > 于2020年6月26日周五
> >>>   下午7:27写道：
> >>>
> >>>   Hi Rob,
> >>>
> >>>   Thanks, we are waiting for a bug report to be logged by
> >> Xeno.
> >>>   Rgds,Rory
> >>>
> >>>   On 26/06/2020 11:10, Rob Tompkins wrote:
> >>>   > Hi Rory,
> >>>   >
> >>>   > @XenoAmess (GitHub) found an error in our DateParser
> >>>   related to
> >>>   the addition of a locale called “ff_LR#Adlm,” which we’re
> >>>   tracking
> >>>   here:https://github.com/apache/commons-lang/pull/558
> >>>   
> >>>   
> >>>   >
> >>>   > We wanted to let you know.
> >>>   >
> >>>   > Cheers,
> >>>   > -Rob
> >>>   >
> >>>   >> On Jun 22, 2020, at 11:46 AM, Rory O'Donnell
> >>>rory.odonn...@oracle.com>
> >>>   
> >>>   > wrote:
> >>>   >>
> >>>   >>
> >>>   >> Hi Benedikt,
> >>>   >>
> >>>   >> *Per the JDK 15 schedule , we are in Rampdown Phase
> One*
> >>>   *[1] *
> >>>   >>
> >>>   >> *Please advise if you find any issues while testing
> the
> >>>   latest
> >>>   Early Access builds.
> >>>   >> *
> >>>   >>
> >>>   >> * Schedule for JDK 15
> >>>   >>  o *2020/06/11 Rampdown Phase One*
> >>>   >>  o 2020/07/16 Rampdown Phase Two
> >>>   >>  o 2020/08/06 Initial Release Candidate
> >

Re: JDK 15 is in Rampdown Phase One

2020-08-04 Thread Rory O'Donnell

Hi Gary,

I checked with dev team, we are not planning to backport the fix into 
JDK15.

Rgds,Rory

On 31/07/2020 15:26, Gary Gregory wrote:

On Fri, Jul 31, 2020 at 10:18 AM Rory O'Donnell
wrote:

On 31/07/2020 14:49, Gary Gregory wrote:

On Fri, Jul 31, 2020 at 5:53 AM Rory O'Donnell 
Hi Xeno,

The issue is resolved in JDK 16 EA build 8, (JDK-8248655
) which is available
on jdk.java.net.

Rgds,Rory

Hi Rory,

Thank you for the update. The latest Java 16 EA builds Apache Commons

Lang

OK now. We'll have to see when Travis-CI and GitHub Actions provide

updates.
Good to hear.

What should our expectations be for Java 15? That build is still broken

for

us, even with build 34 (latest EA).

What's the impact to you, we are very late in the cycle for JDK 15.

Hi Rory,

We rely upon Travis-CI and GitHub Action to build and validate GitHub PRs.

As for now, Java 15 builds always fail because of this issue. We've defined
these CI build jobs to allow for Java 15 builds to fail to provide us with
green builds otherwise.

But we do not know if a Java 15 build has failed solely because of this
single issue or if there are additional compatibility issues, without
searching through the build logs, which frankly is too much of a pain to do
for every single PR that comes in.

In effect, for me, at least, this means that I ignore Java 15 builds since
I know they always fail.

Thank you,
Gary

Rgds,Rory

Thank you!
Gary

On 30/06/2020 09:36, Xeno Amess wrote:

Great, thanks!

Rory O'Donnell mailto:rory.odonn...@oracle.com>> 于2020年6月30日周二 下午4:25写道：

  Hi Xeno,

  The bug has moved into the Java Bug System (JBS) - JDK-8248434

  I have added the "apache-maven-found" label to the bug.

  Rgds,Rory

  On 26/06/2020 13:18, Rory O'Donnell wrote:

  Thanks Xeno!

  Will let you know if anything else required.

  Rgds,Rory

  On 26/06/2020 13:15, Xeno Amess wrote:

  Hi.
  I submitted the bug(or issue) on bugs.java.com

    as you requested.
  And it said internal review ID : 9065633. on the wabpage.
  If there anything else I should do please let me know.

  Rory O'Donnell mailto:rory.odonn...@oracle.com>

  > 于2020年6月26日周五
  下午7:27写道：

  Hi Rob,

  Thanks, we are waiting for a bug report to be logged by

Xeno.

  Rgds,Rory

  On 26/06/2020 11:10, Rob Tompkins wrote:
  > Hi Rory,
  >
  > @XenoAmess (GitHub) found an error in our DateParser
  related to
  the addition of a locale called “ff_LR#Adlm,” which we’re
  tracking
  here:https://github.com/apache/commons-lang/pull/558

  >
  > We wanted to let you know.
  >
  > Cheers,
  > -Rob
  >
  >> On Jun 22, 2020, at 11:46 AM, Rory O'Donnell
  mailto:rory.odonn...@oracle.com>

  > wrote:
  >>
  >>
  >> Hi Benedikt,
  >>
  >> *Per the JDK 15 schedule , we are in Rampdown Phase One*
  *[1] *
  >>
  >> *Please advise if you find any issues while testing the
  latest
  Early Access builds.
  >> *
  >>
  >> * Schedule for JDK 15
  >>  o *2020/06/11 Rampdown Phase One*
  >>  o 2020/07/16 Rampdown Phase Two
  >>  o 2020/08/06 Initial Release Candidate
  >>  o 2020/08/20 Final Release Candidate
  >>  o 2020/09/15 General Availability
  >>
  >> * Features included in JDK 15:
  >>  o JEP 339: Edwards-Curve Digital Signature Algorithm
  (EdDSA)
  >>

  >>  o JEP 360: Sealed Classes (Preview)

  >>  o JEP 371: Hidden Classes

  >>  o JEP 372: Remove the Nashorn JavaScript Engine
  >>

  >>  o JEP 373: Reimplement the Legacy DatagramSocket API
  >>

  >>  o JEP 374: Disable and Deprecate Biased Locking
  >>

  >>  o JEP 375: Pattern Matching for instanceof (Second
  Preview)
  >>

Re: The project website

Re: The project website

Re: The project website

Re: The project website

The project website

Re: JDK 15 is in Rampdown Phase One

Re: JDK 15 is in Rampdown Phase One

7 matches

Site Navigation

Mail list logo

Footer information