date:20171120

Re: [DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

2017-11-20 Thread Jacques Le Roux


Assuming the mission statement is amended following Sebastian's suggestion 
(ditto not being very explicit, I guess KISS way is wanted): +1 (binding)

Jacques


Le 21/11/2017 à 02:20, sebb a écrit :

On 20 November 2017 at 21:32, Pierre Smits  wrote:

The community of the incubating Apache Trafodion Project has discussed and
voted on graduating from incubating. Following instructions from the
graduation guide, this thread is for discussion.

The thread of the community discussion can be found here: [DISCUSSION]
Graduation of The (incubating) Apache Trafodion Project


The thread of the community vote can be found here: [VOTE] Graduate from
Incubator and become a top-level project

,
and the call of the result here: [RESULT][VOTE] Graduate from Incubator and
become a top-level project



*The proposed resolution of the (incubating) Apache Trafodion Project:*

Establish the Apache Trafodion Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to Apache Trafodion is a webscale SQL-on-Hadoop solution
enabling transactional or operational workloads on Hadoop. Trafodion
builds on the scalability, elasticity, and flexibility of Hadoop.
Trafodion extends Hadoop to provide guaranteed transactional integrity,
enabling new kinds of big data applications to run on Hadoop.

The mission statement does not read well.
It's also rather longer than most, and is too detailed.

The last two sentences should be dropped, and the previous one
reworded to look something like:

"... related to a webscale SQL-on-Hadoop solution
enabling transactional or operational workloads on Hadoop."


NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Trafodion Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache Trafodion Project be and hereby is responsible
for the creation and maintenance of software related to Apache Trafodion
is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop. Trafodion builds on the scalability,
elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to
provide guaranteed transactional integrity, enabling new kinds of big
data applications to run on Hadoop; and be it further

Ditto


RESOLVED, that the office of "Vice President, Apache Trafodion" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Trafodion
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Trafodion
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Trafodion
Project:

  * Amanda K Moran 
  * Dave Birdsall  
  * Gunnar Tapper  
  * Ming Liu   
  * Pierre Smits   
  * Roberta Marton 
  * Selva Govindarajan 
  * Steve Varnau   
  * Suresh Subbiah 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Pierre Smits be appointed
to the office of Vice President, Apache Trafodion, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further

RESOLVED, that the Apache Trafodion Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Trafodion
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Trafodion podling encumbered upon the Apache Incubator PMC are hereafter
discharged.



Please provide your feedback on this proposed graduation resolution by the
Trafodion community below. We are hoping to reach a consensus here before
we start a recommendation vote.


Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://oem.ofbizci.net/oci-2/
1 not affiliated to (and not endorsed by) the OFBiz project

[RESULT][VOTE] Accept ServiceComb into the Apache Incubator

2017-11-20 Thread Willem Jiang

Hi all,

The vote for accepting ServiceComb into Apache Incubator passed with 8
binding "+1" votes, 5 nonbinding "+1" votes, and no "0" or "-1" votes.

Binding votes:
   Jean-Baptiste Onofre
   Timothy Chen
   Willem Jiang
   Dave Fisher
   Roman Shaposhnik
   Luke Han
   Gangumalla Uma

Non-binding votes:
   Liang Chen
   Charith Elvitigala
   Vinayakumar B
   Pierre Smits
   Sean Yin

Thanks to all who voted!

Willem Jiang


On Tue, Nov 14, 2017 at 2:15 PM, Willem Jiang 
wrote:

> Hi All,
>
> I would like to start a VOTE to bring the ServiceComb project in as an
> Apache incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept ServiceComb into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept ServiceComb into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/ServiceCombProposal
>
> Best regards,
>
> Willem Jiang
>
> = ServiceComb Proposal =
>
> == Abstract ==
>
> ServiceComb is a microservice framework that provides a set of tools and
> components to make development and deployment of cloud applications easier.
> It provides functionalities such as service contract enforcement, service
> registration, service discovery, load balance, service reliability (latency
> and fault tolerance, flow control and graceful degradation, handler chain
> tracing), eventual data consistency and so forth.
>
> == Proposal ==
>
> The goal of this proposal is to bring the existing ServiceComb codebase
> and existing developers into the Apache Software Foundation (ASF) in order
> to build a vibrant, diverse and self-governed open source community around
> the technology.
> So far the major contributors to the project have been affiliated with
> Huawei and Huawei is planning to continue market and sell the Cloud Service
> Engine leveraging the ServiceComb framework.
> ServiceComb is currently a registered trademark owned by Huawei, and
> Huawei is happy to donate this trademark to Apache.
>
> Huawei is submitting this proposal to donate the Service source code and
> associated artifacts (documentation, web site content, wiki, etc.) to the
> Apache Software Foundation Incubator under the Apache License, Version 2.0
> and is asking Incubator PMC to establish an open source community. These
> artifacts are currently available on GitHub at  https://github.com/
> ServiceComb/ and include:
>  * Java Chassis: a multi-protocol (RPC & Restful) microservice framework
> which adopts contract-first design
>  * Service Center: a service registry that enforces service contract upon
> service registration and discovery
>  * Saga: a distributed coordinator to achieve eventual data consistency
> based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem
>  * ServiceComb.github.io:  the website repo of ServiceComb.
>  * The other projects will be moved to another place if ServiceComb is
> accepted by Apache as an incubator project.
>
> == Background ==
>
> Microservices is a variant of the service-oriented architecture (SOA)
> architectural style that structures an application as a collection of
> loosely coupled services. ServiceComb is an open source microservice
> framework initiated as part of Huawei CSE projects (Cloud Service Engine)
> which was developed in 2015. It is a part of ServiceStage of Huawei Public
> Cloud which is one-stop PaaS platform for enterprises and developers.
> Besides ServiceStage, it’s  also used in the Huawei Core Network IOT
> Platform and Huawei consumer cloud. The number of  companies using
> ServiceComb to develop their enterprise applications, they are
> chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and
> the number is over 5 and counting.
>
> == Rationale ==
>
> ServiceComb has been developed as a total, open source solution for
> developing cloud native applications. So far ServiceComb has existed as a
> GitHub project with committers mostly working for Huawei. We feel that
> moving it to a neutral organization like Apache, with its strong governance
> model, is expected to help get more contributions from various
> organizations and developers, who may be concerned by exclusive control of
> ServiceComb by Huawei.
>
> == Initial Goals ==
>
> Our initial goals are to bring ServiceComb into the ASF, transition
> internal engineering processes into the open, and foster a collaborative
> development model according to the "Apache Way." Huawei and the current
> contributors to ServiceComb plan to develop new functionality in an open,
> community-driven way. To get there, the existing internal build, test and
> release processes will be refactored to support open development.
>
>  1. More

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

2017-11-20 Thread Dave Neuman

Oops. I did reply to the wrong email! Sorry.

On Mon, Nov 20, 2017 at 12:47 Dan Kirkwood  wrote:

> Dave,  did you mean for this to be for 2.1.0 RC2?You replied to
> the wrong email..
>
> -dan
>
> On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman  wrote:
> > +1 However
> > We need to add a release note suggesting that traffic stats works best
> with
> > influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400
> response
> > when the client attempts to write points that are outside of the
> retention
> > policy.  When this happens, Traffic Stats seems to hold on to the "old"
> > points and attempts to write them again on the next POST.  This causes
> what
> > is essentially a memory leak in Traffic Stats since it continues to hold
> > onto and tries to write stats that are outside of the retention policy.
> > This may or may not affect a user, depending upon which stats they are
> > trying to write to influxdb.  For example, we write the wrap_count to
> > influxdb, this is a stat that does not often change within 24 hours, so
> we
> > see the memory leak with stats not written on each poll of traffic stats.
> >
> > In versions < 1.3.x InfluxDB would still not write the point, but it
> would
> > accept the write request and just drop the points outside of the
> retention
> > policy on the floor.
> >
> > This is fixed here:
> > https://github.com/apache/incubator-trafficcontrol/pull/1289 and will
> be in
> > the next release of traffic control.
> >
> > Also, we should note that you need to set selinux to "unenforcing" in
> order
> > to get the build to work, otherwise you fail on permissions erros.  You
> can
> > do this with
> > `setenforce 0` as root.
> >
> >
> > Thanks,
> > Dave
> >
> > On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> > efrie...@cisco.com> wrote:
> >
> >> Dear IPMC Community,
> >>
> >> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6
> of
> >> Apache Traffic Control (Incubating) for release as “Apache Traffic
> Control
> >> (incubating) 2.0.0"
> >>
> >> The vote has passed with:
> >> - three binding "+1" votes
> >> - no "0" votes
> >> - no "-1" votes
> >>
> >> The votes were (https://lists.apache.org/thread.html/
> >> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
> >> 3Cgeneral.incubator.apache.org%3E >> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@ >> neral.incubator.apache.org>>):
> >> - +1, Justin Mclean (binding)
> >> - +1, John D. Ament (binding)
> >> - +1, Phil Sorber (binding)
> >>
> >> Thank you, for your support!
> >>
> >> —Eric
> >>
> >> On Jun 30, 2017, at 5:27 PM, Phil Sorber  >> e...@apache.org>> wrote:
> >>
> >> Checksums match.
> >>
> >> GPG sig verifies, but is untrusted:
> >> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
> >> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
> >> incubating.tar.gz'
> >> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
> >> 9AB7BDD5
> >> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
> >> fri...@apache.org>"
> >> gpg: WARNING: This key is not certified with a trusted signature!
> >> gpg:  There is no indication that the signature belongs to the
> >> owner.
> >> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7
> BDD5
> >>
> >> No signatures:
> >> $ gpg --list-sigs 9AB7BDD5
> >> pub   4096R/9AB7BDD5 2017-04-25
> >> uid  Eric Friedrich (CODE SIGNING KEY) <
> fri...@apache.org
> >> >
> >> sig 39AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> >> fri...@apache.org>
> >> sub   4096R/F445ABB1 2017-04-25
> >> sig  9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> >> fri...@apache.org>
> >>
> >> I won't -1 on that, but we should try to have every RM make sure their
> keys
> >> are trusted. I've already spoken with Eric about this.
> >>
> >> Build also works, with one caveat. You have to set selinux to
> unenforcing,
> >> otherwise you fail from permissions errors. You can do this with
> >> `setenforce 0` as root. I won't -1 for this either, but we should add
> that
> >> to the build documentation.
> >>
> >> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
> >> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
> >> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
> >> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
> >> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
> >> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
> >> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 3.6M

Re: subscribe the mail group

2017-11-20 Thread William Guo

hi Xin,

To subscribe mail list, you need to send email to this address.

general-subscr...@incubator.apache.org




Thanks,
William



From: xin zhang 
Sent: Tuesday, November 21, 2017 10:37 AM
To: general@incubator.apache.org
Subject: subscribe the mail group

Hi All

I want to subscribe the mail group.

Thanks

Xin

subscribe the mail group

2017-11-20 Thread xin zhang

Hi All

I want to subscribe the mail group.

Thanks

Xin

Re: Re:Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]

2017-11-20 Thread Luke Han

+1 (binding)


Best Regards!
-

Luke Han

On Tue, Nov 21, 2017 at 7:56 AM, William Guo  wrote:

> +1, my own cast.
>
> Could some other guys cast your vote?
>
> We appreciate your comments!!!
>
>
>
> Thanks,
> William
> 
> From: Lionel Liu 
> Sent: Friday, November 17, 2017 3:46 PM
> To: general@incubator.apache.org
> Subject: Re:Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]
>
> +1
>
>
>
>
>
> --
>
> Regards,
> Lionel, Liu
>
>
>
> At 2017-11-16 15:39:07, "Lv Alex"  wrote:
> >+1
> >
> >
> >Regards,
> >
> >Alex
> >
> >
> >From: umaganguma...@gmail.com  on behalf of Uma
> gangumalla 
> >Sent: Thursday, November 16, 2017 7:38
> >To: d...@griffin.incubator.apache.org
> >Cc: general@incubator.apache.org
> >Subject: Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]
> >
> >forwarding my +1 from dev list
> >
> >+1 (binding)
> >
> >Regards,
> >Uma
> >
> >On Tue, Nov 14, 2017 at 4:53 PM, William Guo  wrote:
> >
> >> Hi all,
> >> The Apache Griffin community has voted on and approved a proposal to
> >> release Apache Griffin 0.1.6-rc2.
> >> We now kindly request that the Incubator PMC members review and vote
> >> on this incubator release candidate.
> >>
> >> Apache Griffin is data quality service for modern data system, it
> >> defines a standard process to define, measure data quality for
> well-known
> >> dimensions. With Apache Griffin, users will be able to quickly define
> their
> >> data quality requirements and then get the result in near real time in
> >> systematical approach.
> >>
> >>
> >> Griffin vote thread
> >> https://lists.apache.org/thread.html/c538bf4293d410bfdb574f605b6da9
> >> e508f3ef9dc64127e1945888e9@%3Cdev.griffin.apache.org%3E
> >> Griffin vote result thread
> >> https://lists.apache.org/thread.html/769d1c7ad3da35cc02cca960763965
> >> 48d199126f6e9d6da33ecaf581@%3Cdev.griffin.apache.org%3E
> >>
> >> The source tarball, including signatures, digests, etc. can be found
> >> at:
> >> https://dist.apache.org/repos/dist/dev/incubator/griffin/0.
> >> 1.6-incubating
> >>
> >> The tag to be voted upon is 0.1.6-incubating:
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-griffin.
> >> git;a=shortlog;h=refs/tags/0.1.6-incubating
> >>
> >> The release hash is :
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-griffin.
> >> git;a=commit;h=60e23edc96656f7382b74956bfb057e3eee9dda6
> >>
> >> The Nexus Staging URL:
> >> https://repository.apache.org/content/repositories/
> >> orgapachegriffin-1009
> >>
> >> Release artifacts are signed with the following key:
> >> 753AD8D8DF507D7232A9BDBD9B403B9B1BFBCC23
> >>
> >> KEYS file available:
> >> https://dist.apache.org/repos/dist/dev/incubator/griffin/KEYS
> >>
> >> For information about the contents of this release, see:
> >> https://dist.apache.org/repos/dist/dev/incubator/griffin/0.
> >> 1.6-incubating/CHANGES.txt
> >>
> >>
> >> Please download the release candidate and evaluate the necessary
> items
> >> including checking hashes, signatures, build from source, run and test.
> >> Please vote on releasing this package as Apache Griffin
> >> 0.1.6-incubating
> >> The vote will be open for 72 hours.
> >> [ ] +1 Release this package as Apache Griffin 0.1.6-incubating
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because ...
> >>
> >>
> >> Thanks,
> >> William
> >> on behalf of Apache Griffin PPMC
> >>
> >>
>

Re: [DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

2017-11-20 Thread sebb

On 20 November 2017 at 21:32, Pierre Smits  wrote:
> The community of the incubating Apache Trafodion Project has discussed and
> voted on graduating from incubating. Following instructions from the
> graduation guide, this thread is for discussion.
>
> The thread of the community discussion can be found here: [DISCUSSION]
> Graduation of The (incubating) Apache Trafodion Project
> 
>
> The thread of the community vote can be found here: [VOTE] Graduate from
> Incubator and become a top-level project
> 
> ,
> and the call of the result here: [RESULT][VOTE] Graduate from Incubator and
> become a top-level project
> 
>
>
> *The proposed resolution of the (incubating) Apache Trafodion Project:*
>
> Establish the Apache Trafodion Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache Trafodion is a webscale SQL-on-Hadoop solution
> enabling transactional or operational workloads on Hadoop. Trafodion
> builds on the scalability, elasticity, and flexibility of Hadoop.
> Trafodion extends Hadoop to provide guaranteed transactional integrity,
> enabling new kinds of big data applications to run on Hadoop.

The mission statement does not read well.
It's also rather longer than most, and is too detailed.

The last two sentences should be dropped, and the previous one
reworded to look something like:

"... related to a webscale SQL-on-Hadoop solution
enabling transactional or operational workloads on Hadoop."

> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Trafodion Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Trafodion Project be and hereby is responsible
> for the creation and maintenance of software related to Apache Trafodion
> is a webscale SQL-on-Hadoop solution enabling transactional or
> operational workloads on Hadoop. Trafodion builds on the scalability,
> elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to
> provide guaranteed transactional integrity, enabling new kinds of big
> data applications to run on Hadoop; and be it further

Ditto

> RESOLVED, that the office of "Vice President, Apache Trafodion" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Trafodion
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Trafodion
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Trafodion
> Project:
>
>  * Amanda K Moran 
>  * Dave Birdsall  
>  * Gunnar Tapper  
>  * Ming Liu   
>  * Pierre Smits   
>  * Roberta Marton 
>  * Selva Govindarajan 
>  * Steve Varnau   
>  * Suresh Subbiah 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Pierre Smits be appointed
> to the office of Vice President, Apache Trafodion, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache Trafodion Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Trafodion
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Trafodion podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
>
> Please provide your feedback on this proposed graduation resolution by the
> Trafodion community below. We are hoping to reach a consensus here before
> we start a recommendation vote.
>
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OEM - The OFBiz Extensions Marketplace1
> http://oem.ofbizci.net/oci-2/
> 1 not affiliated to (and not endorsed by) the OFBiz project

-
To unsubscribe, e-mail:

Re: Re:Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]

2017-11-20 Thread William Guo

+1, my own cast.

Could some other guys cast your vote?

We appreciate your comments!!!



Thanks,
William

From: Lionel Liu 
Sent: Friday, November 17, 2017 3:46 PM
To: general@incubator.apache.org
Subject: Re:Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]

+1





--

Regards,
Lionel, Liu



At 2017-11-16 15:39:07, "Lv Alex"  wrote:
>+1
>
>
>Regards,
>
>Alex
>
>
>From: umaganguma...@gmail.com  on behalf of Uma 
>gangumalla 
>Sent: Thursday, November 16, 2017 7:38
>To: d...@griffin.incubator.apache.org
>Cc: general@incubator.apache.org
>Subject: Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]
>
>forwarding my +1 from dev list
>
>+1 (binding)
>
>Regards,
>Uma
>
>On Tue, Nov 14, 2017 at 4:53 PM, William Guo  wrote:
>
>> Hi all,
>> The Apache Griffin community has voted on and approved a proposal to
>> release Apache Griffin 0.1.6-rc2.
>> We now kindly request that the Incubator PMC members review and vote
>> on this incubator release candidate.
>>
>> Apache Griffin is data quality service for modern data system, it
>> defines a standard process to define, measure data quality for well-known
>> dimensions. With Apache Griffin, users will be able to quickly define their
>> data quality requirements and then get the result in near real time in
>> systematical approach.
>>
>>
>> Griffin vote thread
>> https://lists.apache.org/thread.html/c538bf4293d410bfdb574f605b6da9
>> e508f3ef9dc64127e1945888e9@%3Cdev.griffin.apache.org%3E
>> Griffin vote result thread
>> https://lists.apache.org/thread.html/769d1c7ad3da35cc02cca960763965
>> 48d199126f6e9d6da33ecaf581@%3Cdev.griffin.apache.org%3E
>>
>> The source tarball, including signatures, digests, etc. can be found
>> at:
>> https://dist.apache.org/repos/dist/dev/incubator/griffin/0.
>> 1.6-incubating
>>
>> The tag to be voted upon is 0.1.6-incubating:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-griffin.
>> git;a=shortlog;h=refs/tags/0.1.6-incubating
>>
>> The release hash is :
>> https://git-wip-us.apache.org/repos/asf?p=incubator-griffin.
>> git;a=commit;h=60e23edc96656f7382b74956bfb057e3eee9dda6
>>
>> The Nexus Staging URL:
>> https://repository.apache.org/content/repositories/
>> orgapachegriffin-1009
>>
>> Release artifacts are signed with the following key:
>> 753AD8D8DF507D7232A9BDBD9B403B9B1BFBCC23
>>
>> KEYS file available:
>> https://dist.apache.org/repos/dist/dev/incubator/griffin/KEYS
>>
>> For information about the contents of this release, see:
>> https://dist.apache.org/repos/dist/dev/incubator/griffin/0.
>> 1.6-incubating/CHANGES.txt
>>
>>
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, run and test.
>> Please vote on releasing this package as Apache Griffin
>> 0.1.6-incubating
>> The vote will be open for 72 hours.
>> [ ] +1 Release this package as Apache Griffin 0.1.6-incubating
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because ...
>>
>>
>> Thanks,
>> William
>> on behalf of Apache Griffin PPMC
>>
>>

Re: [DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

2017-11-20 Thread Gunnar Tapper

+1 (non-binding)

On Mon, Nov 20, 2017 at 3:32 PM, Pierre Smits 
wrote:

> The community of the incubating Apache Trafodion Project has discussed and
> voted on graduating from incubating. Following instructions from the
> graduation guide, this thread is for discussion.
>
> The thread of the community discussion can be found here: [DISCUSSION]
> Graduation of The (incubating) Apache Trafodion Project
>  3ad86ff21839e98e0ae68520e3@%3Cdev.trafodion.apache.org%3E>
>
> The thread of the community vote can be found here: [VOTE] Graduate from
> Incubator and become a top-level project
>  03a1585d398d7820b26be9a255@%3Cdev.trafodion.apache.org%3E>
> ,
> and the call of the result here: [RESULT][VOTE] Graduate from Incubator and
> become a top-level project
>  56302cf98fe212909fefb8e76f@%3Cdev.trafodion.apache.org%3E>
>
>
> *The proposed resolution of the (incubating) Apache Trafodion Project:*
>
> Establish the Apache Trafodion Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache Trafodion is a webscale SQL-on-Hadoop solution
> enabling transactional or operational workloads on Hadoop. Trafodion
> builds on the scalability, elasticity, and flexibility of Hadoop.
> Trafodion extends Hadoop to provide guaranteed transactional integrity,
> enabling new kinds of big data applications to run on Hadoop.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Trafodion Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Trafodion Project be and hereby is responsible
> for the creation and maintenance of software related to Apache Trafodion
> is a webscale SQL-on-Hadoop solution enabling transactional or
> operational workloads on Hadoop. Trafodion builds on the scalability,
> elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to
> provide guaranteed transactional integrity, enabling new kinds of big
> data applications to run on Hadoop; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Trafodion" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Trafodion
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Trafodion
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Trafodion
> Project:
>
>  * Amanda K Moran 
>  * Dave Birdsall  
>  * Gunnar Tapper  
>  * Ming Liu   
>  * Pierre Smits   
>  * Roberta Marton 
>  * Selva Govindarajan 
>  * Steve Varnau   
>  * Suresh Subbiah 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Pierre Smits be appointed
> to the office of Vice President, Apache Trafodion, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache Trafodion Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Trafodion
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Trafodion podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
>
> Please provide your feedback on this proposed graduation resolution by the
> Trafodion community below. We are hoping to reach a consensus here before
> we start a recommendation vote.
>
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OEM - The OFBiz Extensions Marketplace1
> http://oem.ofbizci.net/oci-2/
> 1 not affiliated to (and not endorsed by) the OFBiz project
>



-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*

[DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

2017-11-20 Thread Pierre Smits

The community of the incubating Apache Trafodion Project has discussed and
voted on graduating from incubating. Following instructions from the
graduation guide, this thread is for discussion.

The thread of the community discussion can be found here: [DISCUSSION]
Graduation of The (incubating) Apache Trafodion Project


The thread of the community vote can be found here: [VOTE] Graduate from
Incubator and become a top-level project

,
and the call of the result here: [RESULT][VOTE] Graduate from Incubator and
become a top-level project



*The proposed resolution of the (incubating) Apache Trafodion Project:*

Establish the Apache Trafodion Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to Apache Trafodion is a webscale SQL-on-Hadoop solution
enabling transactional or operational workloads on Hadoop. Trafodion
builds on the scalability, elasticity, and flexibility of Hadoop.
Trafodion extends Hadoop to provide guaranteed transactional integrity,
enabling new kinds of big data applications to run on Hadoop.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Trafodion Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache Trafodion Project be and hereby is responsible
for the creation and maintenance of software related to Apache Trafodion
is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop. Trafodion builds on the scalability,
elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to
provide guaranteed transactional integrity, enabling new kinds of big
data applications to run on Hadoop; and be it further

RESOLVED, that the office of "Vice President, Apache Trafodion" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Trafodion
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Trafodion
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Trafodion
Project:

 * Amanda K Moran 
 * Dave Birdsall  
 * Gunnar Tapper  
 * Ming Liu   
 * Pierre Smits   
 * Roberta Marton 
 * Selva Govindarajan 
 * Steve Varnau   
 * Suresh Subbiah 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Pierre Smits be appointed
to the office of Vice President, Apache Trafodion, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further

RESOLVED, that the Apache Trafodion Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Trafodion
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Trafodion podling encumbered upon the Apache Incubator PMC are hereafter
discharged.



Please provide your feedback on this proposed graduation resolution by the
Trafodion community below. We are hoping to reach a consensus here before
we start a recommendation vote.


Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://oem.ofbizci.net/oci-2/
1 not affiliated to (and not endorsed by) the OFBiz project

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

2017-11-20 Thread Dan Kirkwood

Dave,  did you mean for this to be for 2.1.0 RC2?You replied to
the wrong email..

-dan

On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman  wrote:
> +1 However
> We need to add a release note suggesting that traffic stats works best with
> influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400 response
> when the client attempts to write points that are outside of the retention
> policy.  When this happens, Traffic Stats seems to hold on to the "old"
> points and attempts to write them again on the next POST.  This causes what
> is essentially a memory leak in Traffic Stats since it continues to hold
> onto and tries to write stats that are outside of the retention policy.
> This may or may not affect a user, depending upon which stats they are
> trying to write to influxdb.  For example, we write the wrap_count to
> influxdb, this is a stat that does not often change within 24 hours, so we
> see the memory leak with stats not written on each poll of traffic stats.
>
> In versions < 1.3.x InfluxDB would still not write the point, but it would
> accept the write request and just drop the points outside of the retention
> policy on the floor.
>
> This is fixed here:
> https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
> the next release of traffic control.
>
> Also, we should note that you need to set selinux to "unenforcing" in order
> to get the build to work, otherwise you fail on permissions erros.  You can
> do this with
> `setenforce 0` as root.
>
>
> Thanks,
> Dave
>
> On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> efrie...@cisco.com> wrote:
>
>> Dear IPMC Community,
>>
>> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
>> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
>> (incubating) 2.0.0"
>>
>> The vote has passed with:
>> - three binding "+1" votes
>> - no "0" votes
>> - no "-1" votes
>>
>> The votes were (https://lists.apache.org/thread.html/
>> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
>> 3Cgeneral.incubator.apache.org%3E> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@> neral.incubator.apache.org>>):
>> - +1, Justin Mclean (binding)
>> - +1, John D. Ament (binding)
>> - +1, Phil Sorber (binding)
>>
>> Thank you, for your support!
>>
>> —Eric
>>
>> On Jun 30, 2017, at 5:27 PM, Phil Sorber > e...@apache.org>> wrote:
>>
>> Checksums match.
>>
>> GPG sig verifies, but is untrusted:
>> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
>> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
>> incubating.tar.gz'
>> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
>> 9AB7BDD5
>> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
>> fri...@apache.org>"
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg:  There is no indication that the signature belongs to the
>> owner.
>> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5
>>
>> No signatures:
>> $ gpg --list-sigs 9AB7BDD5
>> pub   4096R/9AB7BDD5 2017-04-25
>> uid  Eric Friedrich (CODE SIGNING KEY) > >
>> sig 39AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
>> fri...@apache.org>
>> sub   4096R/F445ABB1 2017-04-25
>> sig  9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
>> fri...@apache.org>
>>
>> I won't -1 on that, but we should try to have every RM make sure their keys
>> are trusted. I've already spoken with Eric about this.
>>
>> Build also works, with one caveat. You have to set selinux to unenforcing,
>> otherwise you fail from permissions errors. You can do this with
>> `setenforce 0` as root. I won't -1 for this either, but we should add that
>> to the build documentation.
>>
>> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
>> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil  17M Jun 30 15:12
>> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>>
>> +1 binding.
>>
>>

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

2017-11-20 Thread Dave Neuman

+1 However
We need to add a release note suggesting that traffic stats works best with
influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400 response
when the client attempts to write points that are outside of the retention
policy.  When this happens, Traffic Stats seems to hold on to the "old"
points and attempts to write them again on the next POST.  This causes what
is essentially a memory leak in Traffic Stats since it continues to hold
onto and tries to write stats that are outside of the retention policy.
This may or may not affect a user, depending upon which stats they are
trying to write to influxdb.  For example, we write the wrap_count to
influxdb, this is a stat that does not often change within 24 hours, so we
see the memory leak with stats not written on each poll of traffic stats.

In versions < 1.3.x InfluxDB would still not write the point, but it would
accept the write request and just drop the points outside of the retention
policy on the floor.

This is fixed here:
https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
the next release of traffic control.

Also, we should note that you need to set selinux to "unenforcing" in order
to get the build to work, otherwise you fail on permissions erros.  You can
do this with
`setenforce 0` as root.


Thanks,
Dave

On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:

> Dear IPMC Community,
>
> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
> (incubating) 2.0.0"
>
> The vote has passed with:
> - three binding "+1" votes
> - no "0" votes
> - no "-1" votes
>
> The votes were (https://lists.apache.org/thread.html/
> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
> 3Cgeneral.incubator.apache.org%3E c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@ neral.incubator.apache.org>>):
> - +1, Justin Mclean (binding)
> - +1, John D. Ament (binding)
> - +1, Phil Sorber (binding)
>
> Thank you, for your support!
>
> —Eric
>
> On Jun 30, 2017, at 5:27 PM, Phil Sorber  e...@apache.org>> wrote:
>
> Checksums match.
>
> GPG sig verifies, but is untrusted:
> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
> incubating.tar.gz'
> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
> 9AB7BDD5
> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
> fri...@apache.org>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5
>
> No signatures:
> $ gpg --list-sigs 9AB7BDD5
> pub   4096R/9AB7BDD5 2017-04-25
> uid  Eric Friedrich (CODE SIGNING KEY)  >
> sig 39AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> fri...@apache.org>
> sub   4096R/F445ABB1 2017-04-25
> sig  9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> fri...@apache.org>
>
> I won't -1 on that, but we should try to have every RM make sure their keys
> are trusted. I've already spoken with Eric about this.
>
> Build also works, with one caveat. You have to set selinux to unenforcing,
> otherwise you fail from permissions errors. You can do this with
> `setenforce 0` as root. I won't -1 for this either, but we should add that
> to the build documentation.
>
> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil  17M Jun 30 15:12
> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>
> +1 binding.
>
> Thanks!
>
> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean  mailto:jus...@classsoftware.com>>
> wrote:
>
> Hi,
>
> The build instructions will be put in place once the release is done
> -- catch-22.
>
> Yep another reason for including them in the release IMO.
>
> Would Jira issues

Re: [VOTE] Release 1.5.1 of NetBeans HTML/Java API

2017-11-20 Thread sebb

On 20 November 2017 at 08:27, Jaroslav Tulach  wrote:
> 2017-11-19 23:04 GMT+01:00 sebb :
>
>> On 19 November 2017 at 16:52, Jaroslav Tulach 
>> wrote:
>> > 18. 11. 2017 v 21:46, sebb :
>> >
>> >> BTW, I've just noticed that the vote mail does not include a link to
>> >> the source tag.
>> >
>> > True, I've added the tag yesterday when the vote was approved:
>> https://github.com/apache/incubator-netbeans-html4j/tree/release-1.5.1
>> >
>>
>> IMO the tag should be created first, and the RC created from it.
>>
>
> I can try it for next release.
>
> However when working on the first Apache version (e.g. 1.5) of HTML/Java
> API such approach wouldn't be very practical. The tag would have to be
> moved few times, and it is better to avoid moving of tags in a repository.
> As such I needed the review to be finished before creating the tag. Now,
> when most of the structural issues have been discussed and resolved, we can
> optimistically tag before creating the source ZIP file.

What we do in Commons is to use a tag with an RCn suffix.
There may be several before the vote passes.
The successful tag is copied to the GA tag.

Failed tags are generally deleted _after_ the release, as they can be
useful for comparing RCs.

But at the very least the vote mail should contain the revision hash.
That's not ideal, because AFAIK Git revisions can be squashed away.

>
>> >> So I don't know how anyone can have checked the contents of the source
>> >> archive against the code repo.
>> >
>> > One would have to check against the revision used by the Jenkins builder
>> job run that I referenced in my email: https://builds.apache.org/
>> view/Incubator%20Projects/job/incubator-netbeans-html4j-release/20/
>>
>> Apart from having to rummage through the log to find the revision,
>> AIUI Jenkins log files are not kept forever, so this information is
>> not preserved for posterity.
>>
>> IMO for traceability it's vital that the vote email contains all the
>> info that would be needed to re-run the checks at a later date if
>> necessary.
>>
>
> I keep that in mind. Thanks for your comments.
> -jt

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

Re: [VOTE] Release 1.5.1 of NetBeans HTML/Java API

2017-11-20 Thread Jaroslav Tulach

2017-11-19 23:04 GMT+01:00 sebb :

> On 19 November 2017 at 16:52, Jaroslav Tulach 
> wrote:
> > 18. 11. 2017 v 21:46, sebb :
> >
> >> BTW, I've just noticed that the vote mail does not include a link to
> >> the source tag.
> >
> > True, I've added the tag yesterday when the vote was approved:
> https://github.com/apache/incubator-netbeans-html4j/tree/release-1.5.1
> >
>
> IMO the tag should be created first, and the RC created from it.
>

I can try it for next release.

However when working on the first Apache version (e.g. 1.5) of HTML/Java
API such approach wouldn't be very practical. The tag would have to be
moved few times, and it is better to avoid moving of tags in a repository.
As such I needed the review to be finished before creating the tag. Now,
when most of the structural issues have been discussed and resolved, we can
optimistically tag before creating the source ZIP file.


> >> So I don't know how anyone can have checked the contents of the source
> >> archive against the code repo.
> >
> > One would have to check against the revision used by the Jenkins builder
> job run that I referenced in my email: https://builds.apache.org/
> view/Incubator%20Projects/job/incubator-netbeans-html4j-release/20/
>
> Apart from having to rummage through the log to find the revision,
> AIUI Jenkins log files are not kept forever, so this information is
> not preserved for posterity.
>
> IMO for traceability it's vital that the vote email contains all the
> info that would be needed to re-run the checks at a later date if
> necessary.
>

I keep that in mind. Thanks for your comments.
-jt

Re: [DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

[RESULT][VOTE] Accept ServiceComb into the Apache Incubator

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Re: subscribe the mail group

subscribe the mail group

Re: Re:Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]

Re: [DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

Re: Re:Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]

Re: [DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

[DISCUSS] Resolution to graduate the incubating Apache Trafodion Project

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Re: [VOTE] Release 1.5.1 of NetBeans HTML/Java API

Re: [VOTE] Release 1.5.1 of NetBeans HTML/Java API

14 matches

Site Navigation

Mail list logo

Footer information