Hi,
> I know you voted +1, so I think you're okay with it as-is this time around.
> Is this correct?
Yep, it only a minor thing.
> I'm still a little confused about the location to place the files
> pre-release for voting. Should I understand that there is an "official"
> staging area to use fo
On Sat, Jul 30, 2016 at 10:52 PM Justin Mclean
wrote:
> Hi,
>
> Looking a bit further the the Apache Fluo web site I see a couple of
> concerning things, but presumably this is part of a ongoing effort and will
> be sorted out before graduation:
> - It seems the main source of distribution is git
Thanks Justin. I have a few questions still.
On Sat, Jul 30, 2016 at 10:26 PM Justin Mclean
wrote:
> Hi,
>
> +1 binding
>
> I checked:
> - release name includes incubating
> - signature and hashes correct
> - DISCLAIMER exits
> - LICENSE and NOTICE correct. Although you might want to add
> “(inc
Hi,
Looking a bit further the the Apache Fluo web site I see a couple of concerning
things, but presumably this is part of a ongoing effort and will be sorted out
before graduation:
- It seems the main source of distribution is github [1][2] and Sonatype [2]
not the Apache mirrors.
- There are
Hi,
+1 binding
I checked:
- release name includes incubating
- signature and hashes correct
- DISCLAIMER exits
- LICENSE and NOTICE correct. Although you might want to add “(incubating)”
after the project name in NOTICE.
- No source files to check for Apache headers
- No binary files in release
Hi,
> It's not released yet. It was my understanding that we don't put stuff
> there until the vote actually passes a vote for a release, and for that we
> need the IPMC to vote after the PPMC votes
You put stuff into the dev area after a release has been approved but before
that it needs to go
On Sat, Jul 30, 2016 at 10:07 PM Justin Mclean
wrote:
> Hi,
>
> Also you seem to non approved releases [1] on your Apache website [2]
> please remove these or make it clear that these are not Apache releases
> (which I assume is the case).
>
>
Good catch. Thanks. Those releases were non-Apache re
Hi,
Also you seem to non approved releases [1] on your Apache website [2] please
remove these or make it clear that these are not Apache releases (which I
assume is the case).
Thanks,
Justin
1. http://www.apache.org/dev/release.html#what
2. https://fluo.apache.org/docs/
---
On Sat, Jul 30, 2016 at 9:55 PM Justin Mclean
wrote:
> Hi,
>
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachefluo-1003
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapachefluo-1003/org/apache/fluo/fluo-parent/
Hi,
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachefluo-1003
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapachefluo-1003/org/apache/fluo/fluo-parent/1-incubating/fluo-parent-1-incubating-source-release.tar.gz
I’m a l
The voting period has ended and the vote is now closed.
There was 1 binding +0 vote which identified a number of LICENSE issues.
We will correct these issues and resubmit a new candidate RC5.
Thanks Kam
io.fluo was the groupId for Fluo before it transitioned to incubation. This
parent POM references a previously released (prior to acceptance into
incubation) resources artifact under that identity, which contains
checkstyle and Eclipse code formatter rules which this project still uses
to apply con
What is io.fluo and why does this depend on it? Sounds like a branding
issue.
On Jul 30, 2016 14:14, "Christopher" wrote:
> In preparation for a 1.0.0-incubating release of Fluo, the Fluo team is
> first separately releasing a parent POM. This release passed a PPMC vote on
> the Fluo dev@ list
In preparation for a 1.0.0-incubating release of Fluo, the Fluo team is
first separately releasing a parent POM. This release passed a PPMC vote on
the Fluo dev@ list here:
https://lists.apache.org/thread.html/2f801cc81b7eab1f3438da23d8973626755a77e9038f80cce2b30ae9@%3Cdev.fluo.apache.org%3E
Pleas
Соберем для Вас по интернет базу данных
потенциальных клиентов для Вашего Бизнеса!
В базе будут все контактные данные необходимые
для массовой продажи Ваших товаров и услуг.
По Вашему запросу пришлем пример и подробную информацию.
Если интересно запросите подробности сейчас
Email: bawupecoda-3...@y
On Fri, 29 Jul 2016, Jim Apple wrote:
I'd like to add our incubator report for Impala[0] to the report wiki
page[1]. However, the header of that page informs me, when logged in
with my username "JimApple" that it is an "Immutable Page".
What is the procedure for getting append access to that pag
I'd like to add our incubator report for Impala[0] to the report wiki
page[1]. However, the header of that page informs me, when logged in
with my username "JimApple" that it is an "Immutable Page".
What is the procedure for getting append access to that page? I see
that sometimes people ask on th
Hi Justin,
Thank your for voting and advices, We will try to improve the README.md about
compiling on MacOSX and Yes it is not optional by default, I guess the reason
why cannot include module mnemonic-pmalloc-service that probably stems from
compiling or installation of pmalloc project, Thanks
18 matches
Mail list logo
