You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Evans Ye <ev...@apache.org> on 2015/01/08 10:38:16 UTC
list out BOM on the bigtop website
Hi folks,
I'm thinking about to add current 0.8.0 release BOM on bigtop website so
that users can easily know what do we have.
I'll take the list from roman's comment in
https://issues.apache.org/jira/browse/BIGTOP-1110
(please advice if I'm wrong)
OS:
- CentOS6, CentOS7, Fedora 20
- SLES11sp3, OpenSUSE 13.1
- Ubuntu 14.04 LTS
Java:
- JDK7/OpenJDK7
Projects:
- Zookeeper 3.4.5
- Hadoop 2.4.1
- HBase 0.98.5
- Pig 0.12.1
- Hive 0.13
- Sqoop 1.99.2
- Oozie 4..0.1
- Whirr 0.8.2
- Mahout 0.9
- Flume 1.5.0.1
- Giraph 1.1.0
- Hue 3.6.0
- DataFU 1.0.0
- Solr 4.6.0
- Crunch 0.10.0
- Spark 0.9.1
- Phoenix 4.1.0
- Tomcat 6.0.36
- jsvc 1.0.15
If you think it's ok to do so,
do I need to create a patch for the change or to update the site directly?
Re: list out BOM on the bigtop website
Posted by Konstantin Boudnik <co...@apache.org>.
I gave it a quick spin and was able to quickly convert index file from xdoc to
asciidoctor. The resulting code is clearly smaller and easier to
navigate/extend. However, I wasn't been able to produce any "advanced" stuff
like menus and stuff. I am sure it is quite possible is that a general lack of
artistic talent fails me :( I have put an initial snapshot into
'asciidoc-trial' branch if someone wants to take a look
I am pretty sure it would be a great exercise for someone who wants to
contribute to the project and don't know where to start.
Cos
On Mon, Jan 26, 2015 at 03:12PM, nate@reactor8.com wrote:
> Definitely would be a good forward movement on site/doc content.
>
> No too familiar with asciidoc format, mostly just markdown and rdoc, but looks close enough and cant go wrong since github supports it as a parsable format which enables simple/quick viewing from the repo page(s).
>
> -----Original Message-----
> From: Konstantin Boudnik [mailto:cos@apache.org]
> Sent: Monday, January 26, 2015 12:07 PM
> To: dev@bigtop.apache.org
> Subject: Re: list out BOM on the bigtop website
>
> Lately I've been watching at what Groovy (and many other projects) guys are doing for their websites with asciidoctor. It seems to be pretty well tied up into the build system and the source code. I was wondering if this is something we should take a look at? This https://t.co/NNLrg1avtv looks pretty amazing to me. And I guess something like this will help with the question that Evans brought up earlier...
>
> Unless someone else has an itch, let me try to do a shot at it and see what we can get out ;)
>
> Cos
>
> On Thu, Jan 08, 2015 at 07:58PM, Konstantin Boudnik wrote:
> > I believe it'd be very beneficial for the overall release process
> > improvements. There's even an umbrella JIRA for this BIGTOP-1463
> >
> > oh, and once we replace existing bigtop.mk with Groovy DSL such tasks
> > would be a way simpler.
> >
> > Cos
> >
> > On Thu, Jan 08, 2015 at 11:58PM, Evans Ye wrote:
> > > Sounds like a good idea.
> > > I'll try to work out a patch on this.
> > > But need to make myself familiar with mvn site plugin first.
> > > Thanks for the reply, Roman
> > >
> > > 2015-01-08 22:50 GMT+08:00 Roman Shaposhnik <ro...@shaposhnik.org>:
> > >
> > > > What would be awesome is to have a bit of code in our build system
> > > > to slurp bigtop.mk and generate a layout based on that
> > > > information.
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> > > > > Hi folks,
> > > > >
> > > > > I'm thinking about to add current 0.8.0 release BOM on bigtop
> > > > > website so that users can easily know what do we have.
> > > > >
> > > > > I'll take the list from roman's comment in
> > > > > https://issues.apache.org/jira/browse/BIGTOP-1110
> > > > > (please advice if I'm wrong)
> > > > >
> > > > > OS:
> > > > >
> > > > > - CentOS6, CentOS7, Fedora 20
> > > > > - SLES11sp3, OpenSUSE 13.1
> > > > > - Ubuntu 14.04 LTS
> > > > >
> > > > > Java:
> > > > >
> > > > > - JDK7/OpenJDK7
> > > > >
> > > > > Projects:
> > > > >
> > > > > - Zookeeper 3.4.5
> > > > > - Hadoop 2.4.1
> > > > > - HBase 0.98.5
> > > > > - Pig 0.12.1
> > > > > - Hive 0.13
> > > > > - Sqoop 1.99.2
> > > > > - Oozie 4..0.1
> > > > > - Whirr 0.8.2
> > > > > - Mahout 0.9
> > > > > - Flume 1.5.0.1
> > > > > - Giraph 1.1.0
> > > > > - Hue 3.6.0
> > > > > - DataFU 1.0.0
> > > > > - Solr 4.6.0
> > > > > - Crunch 0.10.0
> > > > > - Spark 0.9.1
> > > > > - Phoenix 4.1.0
> > > > > - Tomcat 6.0.36
> > > > > - jsvc 1.0.15
> > > > >
> > > > >
> > > > > If you think it's ok to do so,
> > > > > do I need to create a patch for the change or to update the site
> > > > directly?
> > > >
>
Re: list out BOM on the bigtop website
Posted by Konstantin Boudnik <co...@apache.org>.
I gave it a quick spin and was able to quickly convert index file from xdoc to
asciidoctor. The resulting code is clearly smaller and easier to
navigate/extend. However, I wasn't been able to produce any "advanced" stuff
like menus and stuff. I am sure it is quite possible is that a general lack of
artistic talent fails me :( I have put an initial snapshot into
'asciidoc-trial' branch if someone wants to take a look
I am pretty sure it would be a great exercise for someone who wants to
contribute to the project and don't know where to start.
Cos
On Mon, Jan 26, 2015 at 03:12PM, nate@reactor8.com wrote:
> Definitely would be a good forward movement on site/doc content.
>
> No too familiar with asciidoc format, mostly just markdown and rdoc, but looks close enough and cant go wrong since github supports it as a parsable format which enables simple/quick viewing from the repo page(s).
>
> -----Original Message-----
> From: Konstantin Boudnik [mailto:cos@apache.org]
> Sent: Monday, January 26, 2015 12:07 PM
> To: dev@bigtop.apache.org
> Subject: Re: list out BOM on the bigtop website
>
> Lately I've been watching at what Groovy (and many other projects) guys are doing for their websites with asciidoctor. It seems to be pretty well tied up into the build system and the source code. I was wondering if this is something we should take a look at? This https://t.co/NNLrg1avtv looks pretty amazing to me. And I guess something like this will help with the question that Evans brought up earlier...
>
> Unless someone else has an itch, let me try to do a shot at it and see what we can get out ;)
>
> Cos
>
> On Thu, Jan 08, 2015 at 07:58PM, Konstantin Boudnik wrote:
> > I believe it'd be very beneficial for the overall release process
> > improvements. There's even an umbrella JIRA for this BIGTOP-1463
> >
> > oh, and once we replace existing bigtop.mk with Groovy DSL such tasks
> > would be a way simpler.
> >
> > Cos
> >
> > On Thu, Jan 08, 2015 at 11:58PM, Evans Ye wrote:
> > > Sounds like a good idea.
> > > I'll try to work out a patch on this.
> > > But need to make myself familiar with mvn site plugin first.
> > > Thanks for the reply, Roman
> > >
> > > 2015-01-08 22:50 GMT+08:00 Roman Shaposhnik <ro...@shaposhnik.org>:
> > >
> > > > What would be awesome is to have a bit of code in our build system
> > > > to slurp bigtop.mk and generate a layout based on that
> > > > information.
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> > > > > Hi folks,
> > > > >
> > > > > I'm thinking about to add current 0.8.0 release BOM on bigtop
> > > > > website so that users can easily know what do we have.
> > > > >
> > > > > I'll take the list from roman's comment in
> > > > > https://issues.apache.org/jira/browse/BIGTOP-1110
> > > > > (please advice if I'm wrong)
> > > > >
> > > > > OS:
> > > > >
> > > > > - CentOS6, CentOS7, Fedora 20
> > > > > - SLES11sp3, OpenSUSE 13.1
> > > > > - Ubuntu 14.04 LTS
> > > > >
> > > > > Java:
> > > > >
> > > > > - JDK7/OpenJDK7
> > > > >
> > > > > Projects:
> > > > >
> > > > > - Zookeeper 3.4.5
> > > > > - Hadoop 2.4.1
> > > > > - HBase 0.98.5
> > > > > - Pig 0.12.1
> > > > > - Hive 0.13
> > > > > - Sqoop 1.99.2
> > > > > - Oozie 4..0.1
> > > > > - Whirr 0.8.2
> > > > > - Mahout 0.9
> > > > > - Flume 1.5.0.1
> > > > > - Giraph 1.1.0
> > > > > - Hue 3.6.0
> > > > > - DataFU 1.0.0
> > > > > - Solr 4.6.0
> > > > > - Crunch 0.10.0
> > > > > - Spark 0.9.1
> > > > > - Phoenix 4.1.0
> > > > > - Tomcat 6.0.36
> > > > > - jsvc 1.0.15
> > > > >
> > > > >
> > > > > If you think it's ok to do so,
> > > > > do I need to create a patch for the change or to update the site
> > > > directly?
> > > >
>
RE: list out BOM on the bigtop website
Posted by na...@reactor8.com.
Definitely would be a good forward movement on site/doc content.
No too familiar with asciidoc format, mostly just markdown and rdoc, but looks close enough and cant go wrong since github supports it as a parsable format which enables simple/quick viewing from the repo page(s).
-----Original Message-----
From: Konstantin Boudnik [mailto:cos@apache.org]
Sent: Monday, January 26, 2015 12:07 PM
To: dev@bigtop.apache.org
Subject: Re: list out BOM on the bigtop website
Lately I've been watching at what Groovy (and many other projects) guys are doing for their websites with asciidoctor. It seems to be pretty well tied up into the build system and the source code. I was wondering if this is something we should take a look at? This https://t.co/NNLrg1avtv looks pretty amazing to me. And I guess something like this will help with the question that Evans brought up earlier...
Unless someone else has an itch, let me try to do a shot at it and see what we can get out ;)
Cos
On Thu, Jan 08, 2015 at 07:58PM, Konstantin Boudnik wrote:
> I believe it'd be very beneficial for the overall release process
> improvements. There's even an umbrella JIRA for this BIGTOP-1463
>
> oh, and once we replace existing bigtop.mk with Groovy DSL such tasks
> would be a way simpler.
>
> Cos
>
> On Thu, Jan 08, 2015 at 11:58PM, Evans Ye wrote:
> > Sounds like a good idea.
> > I'll try to work out a patch on this.
> > But need to make myself familiar with mvn site plugin first.
> > Thanks for the reply, Roman
> >
> > 2015-01-08 22:50 GMT+08:00 Roman Shaposhnik <ro...@shaposhnik.org>:
> >
> > > What would be awesome is to have a bit of code in our build system
> > > to slurp bigtop.mk and generate a layout based on that
> > > information.
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> > > > Hi folks,
> > > >
> > > > I'm thinking about to add current 0.8.0 release BOM on bigtop
> > > > website so that users can easily know what do we have.
> > > >
> > > > I'll take the list from roman's comment in
> > > > https://issues.apache.org/jira/browse/BIGTOP-1110
> > > > (please advice if I'm wrong)
> > > >
> > > > OS:
> > > >
> > > > - CentOS6, CentOS7, Fedora 20
> > > > - SLES11sp3, OpenSUSE 13.1
> > > > - Ubuntu 14.04 LTS
> > > >
> > > > Java:
> > > >
> > > > - JDK7/OpenJDK7
> > > >
> > > > Projects:
> > > >
> > > > - Zookeeper 3.4.5
> > > > - Hadoop 2.4.1
> > > > - HBase 0.98.5
> > > > - Pig 0.12.1
> > > > - Hive 0.13
> > > > - Sqoop 1.99.2
> > > > - Oozie 4..0.1
> > > > - Whirr 0.8.2
> > > > - Mahout 0.9
> > > > - Flume 1.5.0.1
> > > > - Giraph 1.1.0
> > > > - Hue 3.6.0
> > > > - DataFU 1.0.0
> > > > - Solr 4.6.0
> > > > - Crunch 0.10.0
> > > > - Spark 0.9.1
> > > > - Phoenix 4.1.0
> > > > - Tomcat 6.0.36
> > > > - jsvc 1.0.15
> > > >
> > > >
> > > > If you think it's ok to do so,
> > > > do I need to create a patch for the change or to update the site
> > > directly?
> > >
Re: list out BOM on the bigtop website
Posted by Konstantin Boudnik <co...@apache.org>.
Lately I've been watching at what Groovy (and many other projects) guys are
doing for their websites with asciidoctor. It seems to be pretty well tied up
into the build system and the source code. I was wondering if this is
something we should take a look at? This https://t.co/NNLrg1avtv looks pretty
amazing to me. And I guess something like this will help with the question
that Evans brought up earlier...
Unless someone else has an itch, let me try to do a shot at it and see what we
can get out ;)
Cos
On Thu, Jan 08, 2015 at 07:58PM, Konstantin Boudnik wrote:
> I believe it'd be very beneficial for the overall release process
> improvements. There's even an umbrella JIRA for this BIGTOP-1463
>
> oh, and once we replace existing bigtop.mk with Groovy DSL such tasks would be
> a way simpler.
>
> Cos
>
> On Thu, Jan 08, 2015 at 11:58PM, Evans Ye wrote:
> > Sounds like a good idea.
> > I'll try to work out a patch on this.
> > But need to make myself familiar with mvn site plugin first.
> > Thanks for the reply, Roman
> >
> > 2015-01-08 22:50 GMT+08:00 Roman Shaposhnik <ro...@shaposhnik.org>:
> >
> > > What would be awesome is to have a bit of code in
> > > our build system to slurp bigtop.mk and generate
> > > a layout based on that information.
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> > > > Hi folks,
> > > >
> > > > I'm thinking about to add current 0.8.0 release BOM on bigtop website so
> > > > that users can easily know what do we have.
> > > >
> > > > I'll take the list from roman's comment in
> > > > https://issues.apache.org/jira/browse/BIGTOP-1110
> > > > (please advice if I'm wrong)
> > > >
> > > > OS:
> > > >
> > > > - CentOS6, CentOS7, Fedora 20
> > > > - SLES11sp3, OpenSUSE 13.1
> > > > - Ubuntu 14.04 LTS
> > > >
> > > > Java:
> > > >
> > > > - JDK7/OpenJDK7
> > > >
> > > > Projects:
> > > >
> > > > - Zookeeper 3.4.5
> > > > - Hadoop 2.4.1
> > > > - HBase 0.98.5
> > > > - Pig 0.12.1
> > > > - Hive 0.13
> > > > - Sqoop 1.99.2
> > > > - Oozie 4..0.1
> > > > - Whirr 0.8.2
> > > > - Mahout 0.9
> > > > - Flume 1.5.0.1
> > > > - Giraph 1.1.0
> > > > - Hue 3.6.0
> > > > - DataFU 1.0.0
> > > > - Solr 4.6.0
> > > > - Crunch 0.10.0
> > > > - Spark 0.9.1
> > > > - Phoenix 4.1.0
> > > > - Tomcat 6.0.36
> > > > - jsvc 1.0.15
> > > >
> > > >
> > > > If you think it's ok to do so,
> > > > do I need to create a patch for the change or to update the site
> > > directly?
> > >
Re: list out BOM on the bigtop website
Posted by Konstantin Boudnik <co...@apache.org>.
I believe it'd be very beneficial for the overall release process
improvements. There's even an umbrella JIRA for this BIGTOP-1463
oh, and once we replace existing bigtop.mk with Groovy DSL such tasks would be
a way simpler.
Cos
On Thu, Jan 08, 2015 at 11:58PM, Evans Ye wrote:
> Sounds like a good idea.
> I'll try to work out a patch on this.
> But need to make myself familiar with mvn site plugin first.
> Thanks for the reply, Roman
>
> 2015-01-08 22:50 GMT+08:00 Roman Shaposhnik <ro...@shaposhnik.org>:
>
> > What would be awesome is to have a bit of code in
> > our build system to slurp bigtop.mk and generate
> > a layout based on that information.
> >
> > Thanks,
> > Roman.
> >
> > On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> > > Hi folks,
> > >
> > > I'm thinking about to add current 0.8.0 release BOM on bigtop website so
> > > that users can easily know what do we have.
> > >
> > > I'll take the list from roman's comment in
> > > https://issues.apache.org/jira/browse/BIGTOP-1110
> > > (please advice if I'm wrong)
> > >
> > > OS:
> > >
> > > - CentOS6, CentOS7, Fedora 20
> > > - SLES11sp3, OpenSUSE 13.1
> > > - Ubuntu 14.04 LTS
> > >
> > > Java:
> > >
> > > - JDK7/OpenJDK7
> > >
> > > Projects:
> > >
> > > - Zookeeper 3.4.5
> > > - Hadoop 2.4.1
> > > - HBase 0.98.5
> > > - Pig 0.12.1
> > > - Hive 0.13
> > > - Sqoop 1.99.2
> > > - Oozie 4..0.1
> > > - Whirr 0.8.2
> > > - Mahout 0.9
> > > - Flume 1.5.0.1
> > > - Giraph 1.1.0
> > > - Hue 3.6.0
> > > - DataFU 1.0.0
> > > - Solr 4.6.0
> > > - Crunch 0.10.0
> > > - Spark 0.9.1
> > > - Phoenix 4.1.0
> > > - Tomcat 6.0.36
> > > - jsvc 1.0.15
> > >
> > >
> > > If you think it's ok to do so,
> > > do I need to create a patch for the change or to update the site
> > directly?
> >
Re: list out BOM on the bigtop website
Posted by Evans Ye <ev...@apache.org>.
Sounds like a good idea.
I'll try to work out a patch on this.
But need to make myself familiar with mvn site plugin first.
Thanks for the reply, Roman
2015-01-08 22:50 GMT+08:00 Roman Shaposhnik <ro...@shaposhnik.org>:
> What would be awesome is to have a bit of code in
> our build system to slurp bigtop.mk and generate
> a layout based on that information.
>
> Thanks,
> Roman.
>
> On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> > Hi folks,
> >
> > I'm thinking about to add current 0.8.0 release BOM on bigtop website so
> > that users can easily know what do we have.
> >
> > I'll take the list from roman's comment in
> > https://issues.apache.org/jira/browse/BIGTOP-1110
> > (please advice if I'm wrong)
> >
> > OS:
> >
> > - CentOS6, CentOS7, Fedora 20
> > - SLES11sp3, OpenSUSE 13.1
> > - Ubuntu 14.04 LTS
> >
> > Java:
> >
> > - JDK7/OpenJDK7
> >
> > Projects:
> >
> > - Zookeeper 3.4.5
> > - Hadoop 2.4.1
> > - HBase 0.98.5
> > - Pig 0.12.1
> > - Hive 0.13
> > - Sqoop 1.99.2
> > - Oozie 4..0.1
> > - Whirr 0.8.2
> > - Mahout 0.9
> > - Flume 1.5.0.1
> > - Giraph 1.1.0
> > - Hue 3.6.0
> > - DataFU 1.0.0
> > - Solr 4.6.0
> > - Crunch 0.10.0
> > - Spark 0.9.1
> > - Phoenix 4.1.0
> > - Tomcat 6.0.36
> > - jsvc 1.0.15
> >
> >
> > If you think it's ok to do so,
> > do I need to create a patch for the change or to update the site
> directly?
>
Re: list out BOM on the bigtop website
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
What would be awesome is to have a bit of code in
our build system to slurp bigtop.mk and generate
a layout based on that information.
Thanks,
Roman.
On Thu, Jan 8, 2015 at 1:38 AM, Evans Ye <ev...@apache.org> wrote:
> Hi folks,
>
> I'm thinking about to add current 0.8.0 release BOM on bigtop website so
> that users can easily know what do we have.
>
> I'll take the list from roman's comment in
> https://issues.apache.org/jira/browse/BIGTOP-1110
> (please advice if I'm wrong)
>
> OS:
>
> - CentOS6, CentOS7, Fedora 20
> - SLES11sp3, OpenSUSE 13.1
> - Ubuntu 14.04 LTS
>
> Java:
>
> - JDK7/OpenJDK7
>
> Projects:
>
> - Zookeeper 3.4.5
> - Hadoop 2.4.1
> - HBase 0.98.5
> - Pig 0.12.1
> - Hive 0.13
> - Sqoop 1.99.2
> - Oozie 4..0.1
> - Whirr 0.8.2
> - Mahout 0.9
> - Flume 1.5.0.1
> - Giraph 1.1.0
> - Hue 3.6.0
> - DataFU 1.0.0
> - Solr 4.6.0
> - Crunch 0.10.0
> - Spark 0.9.1
> - Phoenix 4.1.0
> - Tomcat 6.0.36
> - jsvc 1.0.15
>
>
> If you think it's ok to do so,
> do I need to create a patch for the change or to update the site directly?