Podling request steps have been updated

2016-12-27 Thread John D. Ament 
All,

I just got done editing the podling request page on the public website.
Its based on areas that have changed recently.

http://www.apache.org/dev/infra-contact#requesting-podling

If everyone could take a look and give feedback and where there needs to be
more detail, I would appreciate it.

Thanks,

John

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC3)

2016-12-27 Thread Jean-Baptiste Onofré 

+1 (binding)

Regards
JB

On 12/22/2016 01:38 AM, Mike Jumper wrote:

Hello Incubator PMC,

The Apache Guacamole community has voted on and approved a proposal to
release Apache Guacamole 0.9.10-incubating.

We now kindly request that the Incubator PMC members review and vote
on this incubator release.

The VOTE RESULT is here:

http://mail-archives.apache.org/mod_mbox/incubator-guacamole-dev/201612.mbox/%3CCALKeL-P-nSVEO92Zbo3c%3D-obhD-sk8t_b26kMVFxc8eixqbt1Q%40mail.gmail.com%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://guacamole.incubator.apache.org/releases/0.9.10-incubating/

The git tag for all relevant repositories is "0.9.10-incubating-RC3":

https://github.com/apache/incubator-guacamole-client/tree/0.9.10-incubating-RC3
https://github.com/apache/incubator-guacamole-server/tree/0.9.10-incubating-RC3
https://github.com/apache/incubator-guacamole-manual/tree/0.9.10-incubating-RC3

Build instructions are included in the manual, which is part of the
updated documentation referenced above. For convenience:

http://guacamole.incubator.apache.org/doc/0.9.10-incubating/gug/installing-guacamole.html

Maven artifacts for guacamole-common, guacamole-common-js, and
guacamole-ext can be found in the following staging repository:

https://repository.apache.org/content/repositories/orgapacheguacamole-1004/

Source and binary distributions (also linked within the release notes):

https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC3/

Artifacts have been signed with the "mjum...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/guacamole/KEYS

Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Ho ho ho,

- Mike

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



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[DISCUSS ] Graduate Apache Ranger project to TLP

2016-12-27 Thread Ramesh Mani 
Dear Incubator members,

Apache Ranger Project community has successfully released 0.6.2 version and 
with this there had been a lot of discussion within Apache Ranger community to 
consider graduation to TLP.  Apache Ranger entered into incubation on 24th July 
2014 and from there on this welcoming community had done a tremendous job in 
various technical areas like refactoring the Ranger project core model to be 
service based, supporting additional Apache Hadoop components like  Apache 
Knox, Apache YARN, Apache Storm, Apache Kafka, Apache NiFi, Apache Ranger KMS 
into Ranger authorizing  model for security and making it into a core product 
in the Apache Hadoop security space. Apache Ranger PPMC has exhibited a clear 
understanding of this growing community by electing  4 individuals as 
committers  and  including 22 individuals as contributors. PPMC also has done 8 
successful releases under the guidance of mentors demonstrating their mastery 
over AFS’s IP policies.

An voting was conducted with in Apache Ranger Community to graduate Apache 
Ranger Project to Top Level Project. Vote passed with 16 +1 votes, no 0 or –1 
votes.

Saying this I see that Apache Ranger Project has shown a great potential to 
become a true TLP.  Following summary of the Apache Ranger Project gives a good 
amount of details on the project.
This is a DISCUSS thread to open up the discussion with other IPMC, so please 
feel free to ask questions and discuss.

Thanks

Project Summary:

=
http://incubator.apache.org/projects/ranger.html

Project website:
=

http://ranger.incubator.apache.org

Project Documentation:
===

http://ranger.incubator.apache.org/index.html
http://ranger.incubator.apache.org/quick_start_guide.html
https://cwiki.apache.org/confluence/display/RANGER/Release+Folders

Project maturity Assessment:
===

https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+Ma
turity+Model

Proposed PMC size: 17

Total number of committers   : 14 members
Total number of contributors : 22 members

PMC affiliation (* indicated chair)

* Hortonworks (9)
   Privacera (2)
   BlueTalon (1)
   Others(1)

1802 commits on develop
22 contributors across all branches
Dev list averaged ~50 msgs/month in 2016
User list averaged ~40 msgs/month in 2016
1208 issues created
997 issues resolved

Committer’s affiliation:
===
Active:
Hortonworks
Talend
Freestone infotech
BlueTalon
eBay
Others


Apache Ranger Top Level Project Resolution:


Establish the Apache Ranger 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 a data management platform That provides real-time, consistent access
to data-intensive applications throughout widely distributed cloud
architectures.

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

RESOLVED,that the Apache Ranger Project be and hereby is responsible for
the creation and maintenance of software related to a data management
platform that provides real-time, consistent access to data-intensive
applications throughout widely distributed cloud architectures.

RESOLVED, that the office of "Vice President, Apache Ranger" 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 Ranger
Project, and to have primary responsibility for management of the projects
within the scope of responsibility of the Apache Ranger 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 Ranger Project:

Alok Lal
a...@apache.org
Alan Gates
ga...@apache.org
Balaji Ganesan
bgane...@apache.org
Colm O hEigeartaigh
cohei...@apache.org
Daniel Gruno
rum...@cord.dk
Devaraj Das
d...@hortonworks.com
Don Bosco Durai
bo...@apache.org
Dilli Arumugam
dillido...@apache.org
Gautam Borad
gau...@apache.org
Kevin Minder
kmin...@apache.org
Larry Mccay
lmc...@apache.org

Re: Podling request steps have been updated

2016-12-27 Thread Roman Shaposhnik 
On Tue, Dec 27, 2016 at 8:45 AM, John D. Ament  wrote:
> All,
>
> I just got done editing the podling request page on the public website.
> Its based on areas that have changed recently.
>
> http://www.apache.org/dev/infra-contact#requesting-podling
>
> If everyone could take a look and give feedback and where there needs to be
> more detail, I would appreciate it.

Overall, this looks good. A couple of questions/notes:
   1. I am not sure you need to call #3 explicitly. In setting up of all of my
   podlings I've never had to request it separately.
   2. This check list touches some (ML, SCM) but not all (e.g. JIRA, builds)
   items. If we're striving for the bare minimum I'd say that at least we
   need to include a point on setting up JIRA. If we're covering everything
   builds, wiki and GH also need to be covered.

Thanks,
Roman.

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

[RESULT][VOTE] Ratis to enter Apache Incubator

2016-12-27 Thread Jitendra Pandey 
The vote passes with 11 +1 votes and no -1.

Binding votes (9)
  Jakob Homan, Andrew Purtell, Uma Maheswara Rao G, Chris Nauroth, Roman
Shaposhnik, Suneel Marthi, Chris Douglas, Enis Soztutar, Jitendra Pandey

Non Binding votes (2)
  Anu Engineer, Arpit Agarwal


Thanks everyone for voting and the discussion.

I will start the podling creation process as stated here:
http://www.apache.org/dev/infra-contact#requesting-podling

Thanks
jitendra


On 12/17/16, 7:05 PM, "Chris Douglas"  wrote:

>+1 (binding) -C
>
>On Fri, Dec 16, 2016 at 3:41 PM, Jitendra Pandey
> wrote:
>> Dear All,
>>I would like to call a vote for accepting "Ratis" for incubation in
>>the Apache Incubator.
>> The full proposal is available below, and is also available at this
>>wiki link.
>>https://wiki.apache.org/incubator/RatisProposal
>> There are two discussion threads for this proposal, because the project
>>was renamed from Concur to Ratis based on feedback. Please look for both
>>Concur and Ratis in the archives.
>>
>> Please cast your vote:
>>
>>   [ ] +1, bring Ratis into Incubator
>>   [ ] +0, I don't care either way,
>>   [ ] -1, do not bring Ratis into Incubator, because...
>>
>>  The vote will open at least for 72 hours and only votes from the
>>Incubator PMC are binding.
>>
>> I start with my vote:
>> +1 (binding)
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>
>


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

Re: Podling request steps have been updated

2016-12-27 Thread John D. Ament 
Roman,

On Tue, Dec 27, 2016 at 1:30 PM Roman Shaposhnik 
wrote:

> On Tue, Dec 27, 2016 at 8:45 AM, John D. Ament 
> wrote:
> > All,
> >
> > I just got done editing the podling request page on the public website.
> > Its based on areas that have changed recently.
> >
> > http://www.apache.org/dev/infra-contact#requesting-podling
> >
> > If everyone could take a look and give feedback and where there needs to
> be
> > more detail, I would appreciate it.
>
> Overall, this looks good. A couple of questions/notes:
>1. I am not sure you need to call #3 explicitly. In setting up of all
> of my
>podlings I've never had to request it separately.
>

I added it based on input from the infra team members.  This is a trade off
from not creating the podling parent request.  This way they'll know that
there's something to be done.  If it's not there by the time the ML's are
requested, it may get created, or the ML's may get skipped due to DNS not
existing.


>2. This check list touches some (ML, SCM) but not all (e.g. JIRA,
> builds)
>items. If we're striving for the bare minimum I'd say that at least
> we
>need to include a point on setting up JIRA. If we're covering
> everything
>builds, wiki and GH also need to be covered.
>

I wouldn't expect this to be an exhaustive list.  I'll point out the end of
the section includes a link to service desk to request other resources.  I
could see JIRA being called out explicitly in this area since almost every
project will end up with one.  Assuming that GH == GitHub, I'll point out
that it's automatic now if you're using reporeq.

There are some services that can be enabled that I don't see listed
anywhere.  These include Travis, Coveralls, Hipchat, and Review Board.
Maybe for another day, but may be worth talking about more on comdev or
infra MLs.


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

Re: [DISCUSS] Drop the 2013 Alternate Voting Policy

2016-12-27 Thread Roman Shaposhnik 
I'd rather not sanctify exceptions with a precise list, but rather stop at:

"During incubation, a podling's release package may not be perfect. It
will be up to mentors and IPMC members
to define the appropriate leeway".

Or something to that extent.

Thanks,
Roman.

On Mon, Dec 26, 2016 at 6:03 PM, John D. Ament  wrote:
> On Mon, Dec 26, 2016 at 12:36 PM Marvin Humphrey 
> wrote:
>
>> On Mon, Dec 26, 2016 at 7:29 AM, John D. Ament 
>> wrote:
>>
>> > This policy as far as I can tell has never been used by any podling.
>>
>> It has been used once (by ODF Toolkit).
>>
>> > I believe the problem it was trying to solve was getting binding votes on
>> > releases which has mostly been fixed (release votes would go on for 20+
>> days
>> > back then).
>>
>> The initiative which culminated in the 2013 Alternate Voting Process had
>> some
>> secondary effects which turned out to be more important than the primary
>> effect.
>>
>> Most crucially, the IPMC achieved a common understanding about when to
>> approve
>> flawed release candidates that were legally OK yet not in compliance with
>> Apache policy.  ("Does it put the Foundation at risk?"  If not, then bias
>> towards approval.)  Between that and the eventual success of a separate
>> initiative to codify and clarify official release policy, two important
>> ends
>> were achieved:
>>
>> *   Arguments over release candidates ended sooner and became less
>> embittered.
>> *   Podlings no longer had to cycle through so many release candidates,
>> reducing burnout for Mentors and allowing us to use the limited IPMC
>> release reviewing capacity more effectively.
>>
>
> So, would it perhaps make sense to include a blurb about what is expected
> of a release and what the goals of incubation should be?  Something like:
>
> During incubation, a podling's release package may not be perfect.  These
> errors may include:
> - Improper NOTICE/LICENSE files
> - Failures building from source
> - Inclusion of binaries in the source release
> - Source release not staged properly.
> - etc... (Justin any notes here?)
>
> These issues vary in severity, and may be pointed out as blocking or not
> blocking the release by the IPMC.  Any blocking issues should cause the
> release to rerolled to fix the issue.  Non-blocking issues should be
> entered into your issue tracker and planned to be fixed for the next
> release.
>
> John
>
>
>
>>
>> The problem of insufficient Mentor participation in release review has not
>> gone away, and we remain heavily dependent on Justin (most often) to
>> provide
>> both review and the additional vote.  If Justin's involvement drops, the
>> Incubator is likely to have problems again.
>>
>> However, to address the remaining systemic flaws it seems wise to channel
>> our energies into policy and documentation streamlining, since that has
>> yielded better results.
>>
>> > So I was wondering, is this a policy we want to keep around?
>>
>> +1 to revert.
>>
>> The language was deliberately crafted as an addendum which would be easy to
>> back out.  Ditching it will have no problematic consequences.
>>
>> Marvin Humphrey
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

Re: [DISCUSS] Drop the 2013 Alternate Voting Policy

2016-12-27 Thread Stian Soiland-Reyes 
On 27 December 2016 at 20:44, Roman Shaposhnik  wrote:
> I'd rather not sanctify exceptions with a precise list, but rather stop at:
>
> "During incubation, a podling's release package may not be perfect. It

...  package may not be fully in compliance with [ASF release
policy](https://www.apache.org/dev/release.html).

> will be up to mentors and IPMC members
> to define the appropriate leeway".

... as long as it is [legal](https://www.apache.org/legal/resolved.html).


+1 to a more abstract text - as long as the podling release is legally
sound (e.g. does not include material we can't distribute under ASF
license) we can still permit it, even if it's not according to policy.

However it would be a judgement per podling - if a podling has been
told for two releases for instance to fix their NOTICE, then a third
release might be downvoted (not blocked) for that reason. It could
also happen that an issue is not identified until later - so it's not
easy to write it down as strict rules - and I think we've the current
practice is about right. Some "just enough" formalizing of that
practice, as Roman proposes, will help keep it along those lines also
for the future.

-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

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

[VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

2016-12-27 Thread Dan Kirkwood 
Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating.  We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.0-RC5":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/

Build instructions are included in build/README.md file which is
included in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[  ] +1 Approve the release
[  ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

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

Omitting "-incubating" suffix in Maven artifact version attribute for FreeMarker

2016-12-27 Thread Daniel Dekany 
Hello,

The last release of Apache FreeMarker (incubating) has these Maven
coordinates:

org.freemarker
freemarker
2.3.25-incubating

The "-incubating" in the Maven version is confusing for the users, as
it looks as the version number of an unstable release, and it seems
that this causes many to stick to the last non-Apache release from 1.5
years ago. (See the "*" footnote if you want some more details.)

As far as I know there's no explicit requirement for having
"incubating" in the Maven artifact version number. So, I wonder, can
we just omit "-incubating" from the Maven artifact versions from now
on? In FreeMarker's case the Maven groupId doesn't contain org.apache
(I know, it should, but that's a different topic), so I guess there's
less danger of branding confusion here. Of course, the version number
would remain x.x.x-incubating in the file names of the releases
downloadable from apache.org and so on. Also, in case it bothers
anyone, the "name" element in the Maven POM could be changed from
"Apache FreeMarker" to "Apache FreeMarker (incubating)" (or just to
"FreeMarker").

*: For those not working in the Java ecosystem, know that many users
   will not go to the project home page nowadays to find the latest
   version, just look at the versions at the Maven Central. Without
   any place for explanation, "2.3.25-incubating" and such are often
   believed to be development versions. (I have seen a few user
   queries that indicated that too.) It certainly doesn't help either
   that http://mvnrepository.com automatically marks these incubating
   versions with red (~ alpha). Also, on the same place the last
   non-Apache release has almost 5x more usages than the last two
   "-incubating" releases together, which is suspicious. Spring has
   also stuck at that version for some reason.

-- 
Thanks,
 Daniel Dekany


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

[jira] [Commented] (INCUBATOR-139) Test ticket for Apache Incubator Logo Contest submissions

2016-12-27 Thread Roman Shaposhnik (JIRA) 

[ 
https://issues.apache.org/jira/browse/INCUBATOR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781763#comment-15781763
 ] 

Roman Shaposhnik commented on INCUBATOR-139:


[~johndament] & [~bdelacretaz] what's the latest on this? I've got a few 
designers itching to submit their entries.

> Test ticket for Apache Incubator Logo Contest submissions
> -
>
> Key: INCUBATOR-139
> URL: https://issues.apache.org/jira/browse/INCUBATOR-139
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
> Attachments: this-is-not-a-logo.jpg
>
>
> Just checking out if this allows new jira users to upload their logos. If it 
> does we'll update this description with the contest information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Re: Omitting "-incubating" suffix in Maven artifact version attribute for FreeMarker

2016-12-27 Thread Christopher 
I think it could also be confusing for users of the Maven version didn't
match the IPMC released version identifier.

If anything, it probably makes more sense to have the '-incubating' in the
groupId , since it's the endorsement of the foundation which is in the
interim state. The groupId typically contains the TLP name, which would be
incubator. So, org.apache.incubator? I would like that along with dropping
the incubating suffix on all artifact versions (Maven or not).

I think it's generally confusing for users to have the suffix present, and
redundant when the artifact readme, pom metadata, or other files explain
it's status more clearly. It also creates excessively long file names and
the naming convention conflicts with other post-version identifiers, such
as Maven classifiers and RPM release/arch info.

On Tue, Dec 27, 2016, 20:18 Daniel Dekany  wrote:

> Hello,
>
> The last release of Apache FreeMarker (incubating) has these Maven
> coordinates:
>
> org.freemarker
> freemarker
> 2.3.25-incubating
>
> The "-incubating" in the Maven version is confusing for the users, as
> it looks as the version number of an unstable release, and it seems
> that this causes many to stick to the last non-Apache release from 1.5
> years ago. (See the "*" footnote if you want some more details.)
>
> As far as I know there's no explicit requirement for having
> "incubating" in the Maven artifact version number. So, I wonder, can
> we just omit "-incubating" from the Maven artifact versions from now
> on? In FreeMarker's case the Maven groupId doesn't contain org.apache
> (I know, it should, but that's a different topic), so I guess there's
> less danger of branding confusion here. Of course, the version number
> would remain x.x.x-incubating in the file names of the releases
> downloadable from apache.org and so on. Also, in case it bothers
> anyone, the "name" element in the Maven POM could be changed from
> "Apache FreeMarker" to "Apache FreeMarker (incubating)" (or just to
> "FreeMarker").
>
> *: For those not working in the Java ecosystem, know that many users
>will not go to the project home page nowadays to find the latest
>version, just look at the versions at the Maven Central. Without
>any place for explanation, "2.3.25-incubating" and such are often
>believed to be development versions. (I have seen a few user
>queries that indicated that too.) It certainly doesn't help either
>that http://mvnrepository.com automatically marks these incubating
>versions with red (~ alpha). Also, on the same place the last
>non-Apache release has almost 5x more usages than the last two
>"-incubating" releases together, which is suspicious. Spring has
>also stuck at that version for some reason.
>
> --
> Thanks,
>  Daniel Dekany
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Omitting "-incubating" suffix in Maven artifact version attribute for FreeMarker

2016-12-27 Thread John D. Ament 
I personally have received negative feedback from both colleagues and
management on the use of projects with the name "incubating" in them,
putting them into the same category as alpha or beta software.

When Daniel brought this up on the freemarker list, I did give him my
support in the matter.  I've sent a few emails recently about updating
incubator policies and guides, to fix problems that have been identified.
As far as I'm concerned, what he's asking doesn't require any change - the
use of -incubating in the version # has been a self imposed rule, not a
policy the incubator has requested [1] (note the should).

As far as including it in the group ID, I would expect it to then look like
"org.apache.incubator.podling" but then we are mandating maven coordinates,
which thus far the ASF has not done [2].  I actually prefer the
non-mandated approach, since as you mention, all of the supporting
materials require the disclaimer.

The actual requirement, as I've understood it, is that the release artifact
(the source tarball) includes -incubating.  Not generated maven artifacts
(which are the output of that source tarball).

John

[1]:
http://incubator.apache.org/guides/release-java.html#best-practice-maven
[2]: http://www.apache.org/dev/repository-faq.html


On Tue, Dec 27, 2016 at 9:19 PM Christopher  wrote:

> I think it could also be confusing for users of the Maven version didn't
> match the IPMC released version identifier.
>
> If anything, it probably makes more sense to have the '-incubating' in the
> groupId , since it's the endorsement of the foundation which is in the
> interim state. The groupId typically contains the TLP name, which would be
> incubator. So, org.apache.incubator? I would like that along with dropping
> the incubating suffix on all artifact versions (Maven or not).
>
> I think it's generally confusing for users to have the suffix present, and
> redundant when the artifact readme, pom metadata, or other files explain
> it's status more clearly. It also creates excessively long file names and
> the naming convention conflicts with other post-version identifiers, such
> as Maven classifiers and RPM release/arch info.
>
> On Tue, Dec 27, 2016, 20:18 Daniel Dekany  wrote:
>
> > Hello,
> >
> > The last release of Apache FreeMarker (incubating) has these Maven
> > coordinates:
> >
> > org.freemarker
> > freemarker
> > 2.3.25-incubating
> >
> > The "-incubating" in the Maven version is confusing for the users, as
> > it looks as the version number of an unstable release, and it seems
> > that this causes many to stick to the last non-Apache release from 1.5
> > years ago. (See the "*" footnote if you want some more details.)
> >
> > As far as I know there's no explicit requirement for having
> > "incubating" in the Maven artifact version number. So, I wonder, can
> > we just omit "-incubating" from the Maven artifact versions from now
> > on? In FreeMarker's case the Maven groupId doesn't contain org.apache
> > (I know, it should, but that's a different topic), so I guess there's
> > less danger of branding confusion here. Of course, the version number
> > would remain x.x.x-incubating in the file names of the releases
> > downloadable from apache.org and so on. Also, in case it bothers
> > anyone, the "name" element in the Maven POM could be changed from
> > "Apache FreeMarker" to "Apache FreeMarker (incubating)" (or just to
> > "FreeMarker").
> >
> > *: For those not working in the Java ecosystem, know that many users
> >will not go to the project home page nowadays to find the latest
> >version, just look at the versions at the Maven Central. Without
> >any place for explanation, "2.3.25-incubating" and such are often
> >believed to be development versions. (I have seen a few user
> >queries that indicated that too.) It certainly doesn't help either
> >that http://mvnrepository.com automatically marks these incubating
> >versions with red (~ alpha). Also, on the same place the last
> >non-Apache release has almost 5x more usages than the last two
> >"-incubating" releases together, which is suspicious. Spring has
> >also stuck at that version for some reason.
> >
> > --
> > Thanks,
> >  Daniel Dekany
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

2016-12-27 Thread John D. Ament 
-1 to allow you to fix the critical issue now, and will review the release
more shortly.

Projects must not link to unreleased software.  See also:
http://www.apache.org/dev/release-distribution.html#unreleased

Please remove the download links to the unapproved 1.8.0 release.

John

On Tue, Dec 27, 2016 at 5:32 PM Dan Kirkwood  wrote:

> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a
> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> kindly request that the Incubator PMC members review and vote on this
> incubator release.
>
> The VOTE RESULT is here:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://trafficcontrol.incubator.apache.org/downloads/
>
> The git tag for the repository is "RELEASE-1.8.0-RC5":
>
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5
>
> The source distribution (also linked in the release notes) is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/
>
> Build instructions are included in build/README.md file which is
> included in the source artifact.
>
> Artifacts have been signed with the "dang...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
> Please review and vote:
>
> [  ] +1 Approve the release
> [  ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Dan
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

2016-12-27 Thread Jan van Doorn 
Hi John,

Are you referring to the link on 
http://trafficcontrol.apache.org/downloads/index.html 
  or something else? 

Rgds,
JvD

> On Dec 27, 2016, at 7:47 PM, John D. Ament  wrote:
> 
> -1 to allow you to fix the critical issue now, and will review the release
> more shortly.
> 
> Projects must not link to unreleased software.  See also:
> http://www.apache.org/dev/release-distribution.html#unreleased
> 
> Please remove the download links to the unapproved 1.8.0 release.
> 
> John
> 
> On Tue, Dec 27, 2016 at 5:32 PM Dan Kirkwood  wrote:
> 
>> Hello Incubator PMC,
>> 
>> The Apache Traffic Control community has voted on and approved a
>> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
>> kindly request that the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> The VOTE RESULT is here:
>> 
>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E
>> 
>> The draft release notes (along with links to artifacts,
>> signatures/checksums, and updated documentation) can be found here:
>> 
>> http://trafficcontrol.incubator.apache.org/downloads/
>> 
>> The git tag for the repository is "RELEASE-1.8.0-RC5":
>> 
>> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5
>> 
>> The source distribution (also linked in the release notes) is here:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/
>> 
>> Build instructions are included in build/README.md file which is
>> included in the source artifact.
>> 
>> Artifacts have been signed with the "dang...@apache.org" key listed in:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>> 
>> Please review and vote:
>> 
>> [  ] +1 Approve the release
>> [  ] -1 Don't approve the release (please provide specific comments)
>> 
>> This vote will be open for at least 72 hours.
>> 
>> Thanks,
>> 
>> - Dan
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>>

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

2016-12-27 Thread John D. Ament 
A few questions about the release contents:

- Have you contacted legal-discuss RE CC-SA 4.0 IPL?  Per [1] it is not 2.5
or 3.0 so it requires legal input.  Can you also point out which files are
covered under this? Listing "data" and "component" doesn't help me identify.
- There are no instructions that I could find in the root on how to build
the project.  Can you provide them?
- For "underscore" can you include the actual copy of the MIT license? E.g.
[2]
- Same for "datatables" [3]
- Same for jmenu, but i can't find a valid license to back up your claim
(also not available on the listed site?)
- Same for bootstrap, fontawesome, sorttable, jquery (just gave up at this
point)


[1]: https://www.apache.org/legal/resolved.html#cc-sa
[2]: https://github.com/jashkenas/underscore/blob/1.8.3/LICENSE
[3]: https://github.com/DataTables/DataTables/blob/master/license.txt


On Tue, Dec 27, 2016 at 9:47 PM John D. Ament  wrote:

> -1 to allow you to fix the critical issue now, and will review the release
> more shortly.
>
> Projects must not link to unreleased software.  See also:
> http://www.apache.org/dev/release-distribution.html#unreleased
>
> Please remove the download links to the unapproved 1.8.0 release.
>
> John
>
> On Tue, Dec 27, 2016 at 5:32 PM Dan Kirkwood  wrote:
>
> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a
> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> kindly request that the Incubator PMC members review and vote on this
> incubator release.
>
> The VOTE RESULT is here:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://trafficcontrol.incubator.apache.org/downloads/
>
> The git tag for the repository is "RELEASE-1.8.0-RC5":
>
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5
>
> The source distribution (also linked in the release notes) is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/
>
> Build instructions are included in build/README.md file which is
> included in the source artifact.
>
> Artifacts have been signed with the "dang...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
> Please review and vote:
>
> [  ] +1 Approve the release
> [  ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Dan
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

2016-12-27 Thread John D. Ament 
On Tue, Dec 27, 2016 at 9:58 PM Jan van Doorn  wrote:

> Hi John,
>
> Are you referring to the link on
> http://trafficcontrol.apache.org/downloads/index.html <
> http://trafficcontrol.apache.org/downloads/index.html>  or something else?
>

That's the one I saw.  If you know of others, would be good to clean up
there as well.


>
> Rgds,
> JvD
>
> > On Dec 27, 2016, at 7:47 PM, John D. Ament 
> wrote:
> >
> > -1 to allow you to fix the critical issue now, and will review the
> release
> > more shortly.
> >
> > Projects must not link to unreleased software.  See also:
> > http://www.apache.org/dev/release-distribution.html#unreleased
> >
> > Please remove the download links to the unapproved 1.8.0 release.
> >
> > John
> >
> > On Tue, Dec 27, 2016 at 5:32 PM Dan Kirkwood  wrote:
> >
> >> Hello Incubator PMC,
> >>
> >> The Apache Traffic Control community has voted on and approved a
> >> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> >> kindly request that the Incubator PMC members review and vote on this
> >> incubator release.
> >>
> >> The VOTE RESULT is here:
> >>
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E
> >>
> >> The draft release notes (along with links to artifacts,
> >> signatures/checksums, and updated documentation) can be found here:
> >>
> >> http://trafficcontrol.incubator.apache.org/downloads/
> >>
> >> The git tag for the repository is "RELEASE-1.8.0-RC5":
> >>
> >>
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5
> >>
> >> The source distribution (also linked in the release notes) is here:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/
> >>
> >> Build instructions are included in build/README.md file which is
> >> included in the source artifact.
> >>
> >> Artifacts have been signed with the "dang...@apache.org" key listed in:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
> >>
> >> Please review and vote:
> >>
> >> [  ] +1 Approve the release
> >> [  ] -1 Don't approve the release (please provide specific comments)
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> Thanks,
> >>
> >> - Dan
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>

Re: Omitting "-incubating" suffix in Maven artifact version attribute for FreeMarker

2016-12-27 Thread Christopher 
On Tue, Dec 27, 2016 at 9:43 PM John D. Ament  wrote:

> I personally have received negative feedback from both colleagues and
> management on the use of projects with the name "incubating" in them,
> putting them into the same category as alpha or beta software.
>
> When Daniel brought this up on the freemarker list, I did give him my
> support in the matter.  I've sent a few emails recently about updating
> incubator policies and guides, to fix problems that have been identified.
> As far as I'm concerned, what he's asking doesn't require any change - the
> use of -incubating in the version # has been a self imposed rule, not a
> policy the incubator has requested [1] (note the should).
>
> As far as including it in the group ID, I would expect it to then look like
> "org.apache.incubator.podling" but then we are mandating maven coordinates,
>

Yes, that's what I was thinking.


> which thus far the ASF has not done [2].  I actually prefer the
> non-mandated approach, since as you mention, all of the supporting
> materials require the disclaimer.
>
>
I agree that mandating coords isn't the right way to go, but it might be
okay to suggest coords. In any case, I'm not as much of a fan of this as I
was when I first thought of it earlier... it creates an unnecessary
transition pre-/post-graduation. And, it doesn't help with anything if the
IPMC continues to require the suffix in the release tarball and the release
tarball is built using maven-assembly-plugin (a sensible thing to do).


> The actual requirement, as I've understood it, is that the release artifact
> (the source tarball) includes -incubating.  Not generated maven artifacts
> (which are the output of that source tarball).
>
>
The one complication here is that the release artifact (source tarball) is
most easily created with a maven project by using the maven-assembly-plugin
with the source tarball assembly defined in the ASF-wide parent POM.
There's also value in treating the release artifact (source tarball) as any
other maven-produced artifact (both value in using Nexus to stage releases,
and value in deploying source release tarball to Maven central for archival
and possibly for use as a dependency).

It'd be far preferable, IMO, for IPMC to drop the suffix requirement
entirely, than for any maven-based project to produce the source-tarball
independently from the production of maven artifacts. Dropping the
requirement entirely, would make it easier to use automated Maven tooling
for releases. (This automation helps ensure consistent quality, and avoid
human-error and oversight in what could otherwise be very complicated
releasing.)


> John
>
> [1]:
> http://incubator.apache.org/guides/release-java.html#best-practice-maven
> [2]: http://www.apache.org/dev/repository-faq.html
>
>
> On Tue, Dec 27, 2016 at 9:19 PM Christopher  wrote:
>
> > I think it could also be confusing for users of the Maven version didn't
> > match the IPMC released version identifier.
> >
> > If anything, it probably makes more sense to have the '-incubating' in
> the
> > groupId , since it's the endorsement of the foundation which is in the
> > interim state. The groupId typically contains the TLP name, which would
> be
> > incubator. So, org.apache.incubator? I would like that along with
> dropping
> > the incubating suffix on all artifact versions (Maven or not).
> >
> > I think it's generally confusing for users to have the suffix present,
> and
> > redundant when the artifact readme, pom metadata, or other files explain
> > it's status more clearly. It also creates excessively long file names and
> > the naming convention conflicts with other post-version identifiers, such
> > as Maven classifiers and RPM release/arch info.
> >
> > On Tue, Dec 27, 2016, 20:18 Daniel Dekany  wrote:
> >
> > > Hello,
> > >
> > > The last release of Apache FreeMarker (incubating) has these Maven
> > > coordinates:
> > >
> > > org.freemarker
> > > freemarker
> > > 2.3.25-incubating
> > >
> > > The "-incubating" in the Maven version is confusing for the users, as
> > > it looks as the version number of an unstable release, and it seems
> > > that this causes many to stick to the last non-Apache release from 1.5
> > > years ago. (See the "*" footnote if you want some more details.)
> > >
> > > As far as I know there's no explicit requirement for having
> > > "incubating" in the Maven artifact version number. So, I wonder, can
> > > we just omit "-incubating" from the Maven artifact versions from now
> > > on? In FreeMarker's case the Maven groupId doesn't contain org.apache
> > > (I know, it should, but that's a different topic), so I guess there's
> > > less danger of branding confusion here. Of course, the version number
> > > would remain x.x.x-incubating in the file names of the releases
> > > downloadable from apache.org and so on. Also, in case it bothers
> > > anyone, the "name" element in the Maven POM could be changed from
> > > "Apache FreeMarker" to "Apache FreeMarke

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

2016-12-27 Thread Jan van Doorn 
I removed the link. 

We’ll review the other issues you mention tomorrow.

Thanks for your help!

Rgds,
JvD

> On Dec 27, 2016, at 8:04 PM, John D. Ament  wrote:
> 
> On Tue, Dec 27, 2016 at 9:58 PM Jan van Doorn  wrote:
> 
>> Hi John,
>> 
>> Are you referring to the link on
>> http://trafficcontrol.apache.org/downloads/index.html <
>> http://trafficcontrol.apache.org/downloads/index.html>  or something else?
>> 
> 
> That's the one I saw.  If you know of others, would be good to clean up
> there as well.
> 
> 
>> 
>> Rgds,
>> JvD
>> 
>>> On Dec 27, 2016, at 7:47 PM, John D. Ament 
>> wrote:
>>> 
>>> -1 to allow you to fix the critical issue now, and will review the
>> release
>>> more shortly.
>>> 
>>> Projects must not link to unreleased software.  See also:
>>> http://www.apache.org/dev/release-distribution.html#unreleased
>>> 
>>> Please remove the download links to the unapproved 1.8.0 release.
>>> 
>>> John
>>> 
>>> On Tue, Dec 27, 2016 at 5:32 PM Dan Kirkwood  wrote:
>>> 
 Hello Incubator PMC,
 
 The Apache Traffic Control community has voted on and approved a
 proposal to release Apache Traffic Control 1.8.0-incubating.  We now
 kindly request that the Incubator PMC members review and vote on this
 incubator release.
 
 The VOTE RESULT is here:
 
 
 
>> http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E
 
 The draft release notes (along with links to artifacts,
 signatures/checksums, and updated documentation) can be found here:
 
 http://trafficcontrol.incubator.apache.org/downloads/
 
 The git tag for the repository is "RELEASE-1.8.0-RC5":
 
 
>> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5
 
 The source distribution (also linked in the release notes) is here:
 
 
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/
 
 Build instructions are included in build/README.md file which is
 included in the source artifact.
 
 Artifacts have been signed with the "dang...@apache.org" key listed in:
 
 https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
 
 Please review and vote:
 
 [  ] +1 Approve the release
 [  ] -1 Don't approve the release (please provide specific comments)
 
 This vote will be open for at least 72 hours.
 
 Thanks,
 
 - Dan
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>> 
>> 


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