Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Geertjan Wielenga 
The thing is that a lot of the NetBeans infrastructure has built up and
expanded over the 20 years of its existence. The Apache incubator is going
to be a great moment in which to evaluate what we want to keep and what
should be discarded and how these various pieces fit into Apache's
structures. All software is kind of similar in these requirements, there's
not going to be anything that we can't solve in one way or another. Yes,
several questions remain and Daniel Gruno is now in direct contact with the
NetBeans build engineer and others from the NetBeans team knowledgeable in
this area.

Gj

On Sat, Sep 17, 2016 at 1:53 AM, David Nalley  wrote:

> On Fri, Sep 16, 2016 at 5:41 PM, Jochen Theodorou 
> wrote:
> > On 16.09.2016 00:36, Geertjan Wielenga wrote:
> > [...]
> >>
> >> Public servers:
> >> - www.netbeans.org: ...
> >> - hg.netbeans.org: ...
> >> - deadlock.netbeans.org: ...
> >> - bits.netbeans.org: ...
> >> - updates.netbeans.org: ...
> >> - statistics.netbeans.org: ...
> >> - plugins.netbeans.org: ...
> >> - forums.netbenas.org: ...
> >> - services.netbeans.org: ...
> >
> >
> > I am wondering... is having several subdomains a problem for infra?
> >
> > I did hear things in this direction, but since I was not directly
> involved I
> > may have missed the important detail. Maybe someone from infra reads this
> > and can answer?
> >
>
> No technical reason why we can't do this.
>
> --David
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread David Nalley 
On Fri, Sep 16, 2016 at 5:41 PM, Jochen Theodorou  wrote:
> On 16.09.2016 00:36, Geertjan Wielenga wrote:
> [...]
>>
>> Public servers:
>> - www.netbeans.org: ...
>> - hg.netbeans.org: ...
>> - deadlock.netbeans.org: ...
>> - bits.netbeans.org: ...
>> - updates.netbeans.org: ...
>> - statistics.netbeans.org: ...
>> - plugins.netbeans.org: ...
>> - forums.netbenas.org: ...
>> - services.netbeans.org: ...
>
>
> I am wondering... is having several subdomains a problem for infra?
>
> I did hear things in this direction, but since I was not directly involved I
> may have missed the important detail. Maybe someone from infra reads this
> and can answer?
>

No technical reason why we can't do this.

--David

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

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Geertjan Wielenga 
No one said we want to keep that many subdomains. We're simply listing our
current infrastructure at this point. I'd say we probably need a lot less
than we currently have.

Gj

On Fri, Sep 16, 2016 at 11:41 PM, Jochen Theodorou 
wrote:

> On 16.09.2016 00:36, Geertjan Wielenga wrote:
> [...]
>
>> Public servers:
>> - www.netbeans.org: ...
>> - hg.netbeans.org: ...
>> - deadlock.netbeans.org: ...
>> - bits.netbeans.org: ...
>> - updates.netbeans.org: ...
>> - statistics.netbeans.org: ...
>> - plugins.netbeans.org: ...
>> - forums.netbenas.org: ...
>> - services.netbeans.org: ...
>>
>
> I am wondering... is having several subdomains a problem for infra?
>
> I did hear things in this direction, but since I was not directly involved
> I may have missed the important detail. Maybe someone from infra reads this
> and can answer?
>
> bye Jochen
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Jochen Theodorou 

On 16.09.2016 00:36, Geertjan Wielenga wrote:
[...]

Public servers:
- www.netbeans.org: ...
- hg.netbeans.org: ...
- deadlock.netbeans.org: ...
- bits.netbeans.org: ...
- updates.netbeans.org: ...
- statistics.netbeans.org: ...
- plugins.netbeans.org: ...
- forums.netbenas.org: ...
- services.netbeans.org: ...


I am wondering... is having several subdomains a problem for infra?

I did hear things in this direction, but since I was not directly 
involved I may have missed the important detail. Maybe someone from 
infra reads this and can answer?


bye Jochen


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

Re: [VOTE] Release of Apache Tephra-0.9.0-incubating [rc1]

2016-09-16 Thread Alan Gates 
Forwarding my +1 from the vote on the dev list.

Alan.

> On Sep 15, 2016, at 22:44, Poorna Chandra  wrote:
> 
> Hi all,
> 
> This is a call for a vote on releasing Apache Tephra 0.9.0-incubating,
> release candidate 1. This is the second release of Tephra.
> 
> Apache Tephra community has voted and approved the release.
> 
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201609.mbox/%3CCAC9o21R4KR-e%3DmzCsefvokpQWykOXTTnWt%2BZwt0CjiZz1MsqAg%40mail.gmail.com%3E
> 
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201609.mbox/%3CCAC9o21Q9RJqDAo9n_AJWKaPm9_9iM4JoOL0bK9uh2thhS5Jn1g%40mail.gmail.com%3E
> 
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.0-incubating-rc1/src
> 
> The tag to be voted upon is v0.9.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.9.0-incubating
> 
> The release hash is db235cdfa0d40d4e31bcd19ab350e9961719c79e:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=db235cdfa0d40d4e31bcd19ab350e9961719c79e
> 
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1004
> 
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/poorna
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> 
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.0-incubating-rc1/CHANGES.txt
> 
> Please vote on releasing this package as Apache Tephra 0.9.0-incubating
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 Release this package as Apache Tephra 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> Poorna.


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

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Geertjan Wielenga 
Take note of the earlier points re parallel integration (
http://wiki.netbeans.org/HgParallelProjectIntegration), which is different
to the GitHub approach, which we are happy to adopt, so a lot of the
current complexities will not be applicable anymore.

On Fri, Sep 16, 2016 at 8:52 PM, Andrew Bayer 
wrote:

> On Thu, Sep 15, 2016 at 3:36 PM, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
> > - deadlock.netbeans.org: 6 VMs, used mainly for propagation of changes
> > between team repositories and to the releases repository, including jobs
> > for building community plugins (releases*-au) and jobs for prototype
> > projects.
> >
>
> I'm confused, I think - the team repositories are subsets of the releases
> repository?
>
> A.
>

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Geertjan Wielenga 
Commit Before Review - unless the change is an API change - then we use
review before integration and the review is done in bugzilla.

Committers never directly push to the cannonical repo master branch. That
branch is closed for integration. In Git terminology, each team (jet-main,
web-main, core-main, ergonomics) has it's own branch and only if all checks
pass is the branch merged into the master branch automatically.

Yes, before a doing a release there is a manual stabilisation phase.

Gerrit has never been used by the NetBeans team.

Thanks,

Geertjan

On Fri, Sep 16, 2016 at 8:51 AM, Mark Struberg 
wrote:

> That goes into a direction I was about to ask anyway, the development
> model:
>
> Is it CTR (commit-then-review) or RTC (review-then-commit).
>
> Means do committers directly push to the cannonical repo master branch and
> before doing a release there is a manual stabilisation phase? Or do you
> only apply finished features?
>
> Question is whether we need Gerrit or something similar. Or is plain GIT
> enough?
>
> LieGrue,
> strub
>
>
>
>
>
> On Friday, 16 September 2016, 7:01, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
>
> >
> >
> >Of the 32 repos in Mercurial, not all are active. We assume we'll have
> >Git-style development under Apache, with pull requests. That is, however,
> a
> >different working/infrastructure style than we have had in Oracle, with
> >parallel integration (http://wiki.netbeans.org/
> HgParallelProjectIntegration).
> >Thus, many of the repos are only there to participate in the parallel
> >integration (core-main, jet-main, web-main, etc.) We don't believe it is a
> >requirement to migrate all of those repos, probably we won't even need
> >them, when we analyze the infrastructure migration in detail during
> >incubation. However, the #1 requirement is for Apache NetBeans to be able
> >to produce daily/release builds and to upload them to netbeans.org or
> >another download area under Apache. We believe
> >http://hg.netbeans.org/releases/ should be enough for that.
> >
> >Thanks,
> >
> >Geertjan
> >
> >
> >On Fri, Sep 16, 2016 at 5:33 AM, Geertjan Wielenga <
> >geertjan.wiele...@googlemail.com> wrote:
> >
> >> Thanks. Contacting him.
> >>
> >> More info, this time statistics:
> >>
> >> Total Physical Source Lines of Code = 8,281,256
> >> Total Number of Files = 64927
> >>
> >> Thanks,
> >>
> >> Geertjan:
> >>
> >>
> >>
> >> On Fri, Sep 16, 2016 at 1:22 AM, David Nalley  wrote:
> >>
> >>> On Thu, Sep 15, 2016 at 6:36 PM, Geertjan Wielenga
> >>>  wrote:
> >>> > Notes on the NetBeans infrastructure from the NetBeans build
> engineer.
> >>> Who
> >>> > from Apache infra is going to do 1:1 discovery?
> >>>
> >>> Daniel Gruno will - feel free to reach out directly to him at
> >>> humbed...@apache.org
> >>>
> >>> In the meantime, this is a good but of information, Thanks!
> >>>
> >>> --David
> >>> >
> >>> > Public servers:
> >>> > - www.netbeans.org: The core of the netbeans.org project, as well as
> >>> user
> >>> > management, bugzilla, and mailing lists.
> >>> > - hg.netbeans.org: 1 VM with 32 Mercurial repositories. The main
> >>> > repositories are main-golden, main-silver, releases, and all team
> >>> > repositories (core-main, cnd-main, jet-main, profiler-main,
> ergonomics),
> >>> > localization repository (releases/l10n). Several of the repos are
> >>> inactive
> >>> > and don't need to be migrated. Repos are available via http/https.
> The
> >>> > server doesn’t have its own authentication mechanism. Authentication
> for
> >>> > pushes is realized via JSON request from www.netbeans.org. The
> special
> >>> > directory http://hg.netbeans.org/binaries/ on the server contains
> and
> >>> > provides 3rd party libraries.
> >>> > - deadlock.netbeans.org: 6 VMs, used mainly for propagation of
> changes
> >>> > between team repositories and to the releases repository, including
> jobs
> >>> > for building community plugins (releases*-au) and jobs for prototype
> >>> > projects.
> >>> > - bits.netbeans.org: 1 VM, which is the backup download server and
> is
> >>> the
> >>> > server for Javahelp and JNLP. The Nexus server runs there and it
> >>> provides
> >>> > NetBeans Maven artifacts.
> >>> > - downloads.oracle.com and updates.netbeans.org: The main download
> >>> server
> >>> > for installers and update centers. Bits are in fact published on
> Akami
> >>> > servers all over the world. The server is not under NetBeans team
> >>> control.
> >>> > We only upload data to a specific place and they are processed
> somehow
> >>> by
> >>> > Akami.
> >>> > - statistics.netbeans.org: A machine providing statistics on
> NetBeans
> >>> usage.
> >>> > - plugins.netbeans.org: The server for community plugins.
> >>> > - forums.netbenas.org: NetBeans forums.
> >>> > - services.netbeans.org: Services such as anti spam filters for
> >>> bugzilla
> >>> > are here, as well as weekly NetBeans

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Jim Jagielski 

> On Sep 14, 2016, at 5:39 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi Emmanuel,
> 
> On Wed, Sep 14, 2016 at 10:55 AM, Emmanuel Lecharny
>  wrote:
>> ...Better have a hard core set of mentors from the beginning than having a
>> bunch of people that will quit during incubation, IMHO...
> 
> Ok, ok, if you insist on being removed from the mentors list I guess
> we will reluctantly accept...but once again I don't think you are less
> hard core than the other mentors ;-)
> 

Agreed!!


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

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Andrew Bayer 
On Thu, Sep 15, 2016 at 3:36 PM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> - deadlock.netbeans.org: 6 VMs, used mainly for propagation of changes
> between team repositories and to the releases repository, including jobs
> for building community plugins (releases*-au) and jobs for prototype
> projects.
>

I'm confused, I think - the team repositories are subsets of the releases
repository?

A.

Re: ASF Android release policy

2016-09-16 Thread Ian Dunlop 
Hello,

Thanks for all the advice. I have created
https://issues.apache.org/jira/browse/INFRA-12614 to ask for an ASF Google
play account.

Cheers,

Ian

On 13 September 2016 at 16:01, David Nalley  wrote:

> On Tue, Sep 13, 2016 at 4:49 AM, Ian Dunlop  wrote:
> > Hello,
> >
> > In the Taverna Incubator project we have been developing an Android
> mobile
> > app which is almost ready for a first release. Are there any ASF
> procedures
> > and policies for doing an Android release? Can an ASF based Android app
> be
> > released into the Google play store (or others)?
> >
>
> We've signed up to be able to push IOS apps, so at least in principle
> nothing that prohibits that. I do not believe we've signed up for
> Google Play or Amazon stores, and we'd need to look at the T
> associated with that and look at the mechanics.
>
> --David
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Bertrand Delacretaz 
Hi,

On Fri, Sep 16, 2016 at 7:00 AM, Geertjan Wielenga
 wrote:
> ...the #1 requirement is for Apache NetBeans to be able
> to produce daily/release builds and to upload them to netbeans.org or
> another download area under Apache

Daily releases are problematic in Apache projects as the PMC needs to
approve releases, and in general those votes last at least 72 hours
due to our async collaboration model.

AFAIK Apache Cordova for example is making very frequent releases, it
might be interesting to find out how they enable that, in due time.

Nightly builds should not be announced outside of the project's
developers mailing lists, to mark a clear line between those and
official releases.

All those things can be discussed during incubation of course, just
wanted to mention them due to the above #1 requirement.

-Bertrand

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

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Bertrand Delacretaz 
On Fri, Sep 16, 2016 at 12:36 AM, Geertjan Wielenga
 wrote:
> ...Who from Apache infra is going to do 1:1 discovery?...

I don't know but please make sure the results are documented (as long
as it's nothing confidential) either on this list or as an appendix to
the wiki proposal.

One reason is to avoid having to repeat things later, and another is
to document the steps required to incubate such large established
projects as NetBeans here.

-Bertrand

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

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Bertrand Delacretaz 
On Thu, Sep 15, 2016 at 11:30 PM, Shane Curcuru  wrote:
> ...I really expect that the
> IPMC would allow a significantly longer discuss thread on such a large,
> complex, and long-historied project before voting...

I have no problems waiting a bit longer before voting, as long as an
active discussion is going on - as this is the case, we'll wait!

-Bertrand

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

Re: [DISCUSS] Apache NetBeans Incubator Proposal

2016-09-16 Thread Mark Struberg 
That goes into a direction I was about to ask anyway, the development model:

Is it CTR (commit-then-review) or RTC (review-then-commit). 

Means do committers directly push to the cannonical repo master branch and 
before doing a release there is a manual stabilisation phase? Or do you only 
apply finished features?

Question is whether we need Gerrit or something similar. Or is plain GIT enough?

LieGrue,
strub





On Friday, 16 September 2016, 7:01, Geertjan Wielenga 
 wrote:


>
>
>Of the 32 repos in Mercurial, not all are active. We assume we'll have
>Git-style development under Apache, with pull requests. That is, however, a
>different working/infrastructure style than we have had in Oracle, with
>parallel integration (http://wiki.netbeans.org/HgParallelProjectIntegration).
>Thus, many of the repos are only there to participate in the parallel
>integration (core-main, jet-main, web-main, etc.) We don't believe it is a
>requirement to migrate all of those repos, probably we won't even need
>them, when we analyze the infrastructure migration in detail during
>incubation. However, the #1 requirement is for Apache NetBeans to be able
>to produce daily/release builds and to upload them to netbeans.org or
>another download area under Apache. We believe
>http://hg.netbeans.org/releases/ should be enough for that.
>
>Thanks,
>
>Geertjan
>
>
>On Fri, Sep 16, 2016 at 5:33 AM, Geertjan Wielenga <
>geertjan.wiele...@googlemail.com> wrote:
>
>> Thanks. Contacting him.
>>
>> More info, this time statistics:
>>
>> Total Physical Source Lines of Code = 8,281,256
>> Total Number of Files = 64927
>>
>> Thanks,
>>
>> Geertjan:
>>
>>
>>
>> On Fri, Sep 16, 2016 at 1:22 AM, David Nalley  wrote:
>>
>>> On Thu, Sep 15, 2016 at 6:36 PM, Geertjan Wielenga
>>>  wrote:
>>> > Notes on the NetBeans infrastructure from the NetBeans build engineer.
>>> Who
>>> > from Apache infra is going to do 1:1 discovery?
>>>
>>> Daniel Gruno will - feel free to reach out directly to him at
>>> humbed...@apache.org
>>>
>>> In the meantime, this is a good but of information, Thanks!
>>>
>>> --David
>>> >
>>> > Public servers:
>>> > - www.netbeans.org: The core of the netbeans.org project, as well as
>>> user
>>> > management, bugzilla, and mailing lists.
>>> > - hg.netbeans.org: 1 VM with 32 Mercurial repositories. The main
>>> > repositories are main-golden, main-silver, releases, and all team
>>> > repositories (core-main, cnd-main, jet-main, profiler-main, ergonomics),
>>> > localization repository (releases/l10n). Several of the repos are
>>> inactive
>>> > and don't need to be migrated. Repos are available via http/https. The
>>> > server doesn’t have its own authentication mechanism. Authentication for
>>> > pushes is realized via JSON request from www.netbeans.org. The special
>>> > directory http://hg.netbeans.org/binaries/ on the server contains and
>>> > provides 3rd party libraries.
>>> > - deadlock.netbeans.org: 6 VMs, used mainly for propagation of changes
>>> > between team repositories and to the releases repository, including jobs
>>> > for building community plugins (releases*-au) and jobs for prototype
>>> > projects.
>>> > - bits.netbeans.org: 1 VM, which is the backup download server and is
>>> the
>>> > server for Javahelp and JNLP. The Nexus server runs there and it
>>> provides
>>> > NetBeans Maven artifacts.
>>> > - downloads.oracle.com and updates.netbeans.org: The main download
>>> server
>>> > for installers and update centers. Bits are in fact published on Akami
>>> > servers all over the world. The server is not under NetBeans team
>>> control.
>>> > We only upload data to a specific place and they are processed somehow
>>> by
>>> > Akami.
>>> > - statistics.netbeans.org: A machine providing statistics on NetBeans
>>> usage.
>>> > - plugins.netbeans.org: The server for community plugins.
>>> > - forums.netbenas.org: NetBeans forums.
>>> > - services.netbeans.org: Services such as anti spam filters for
>>> bugzilla
>>> > are here, as well as weekly NetBeans newsletter maintenance.
>>> >
>>> > Internal servers:
>>> > - nbbuilder: 5 VMs. The Hudson server with its slaves, where nightly
>>> builds
>>> > and release builds are run.
>>> > - nbbuilder2: 5 VMs. The Hudson server with its slaves, where Maven
>>> > repositories are generated.
>>> > - big-mac: Physical machine used for Mac OS X installers.
>>> > - nbstrorage: Internal storage for all NetBeans bits, access is allowed
>>> for
>>> > internal users only via HTTP.
>>> > - Oracle signing server: NetBeans build jobs using Oracle signing
>>> > infrastructure for signing installers and NBMs.
>>> >
>>> > Comments or follow up to the above?
>>> >
>>> > Thanks,
>>> >
>>> > Gj
>>> >
>>> >
>>> >
>>> > On Thu, Sep 15, 2016 at 11:38 PM, Shane Curcuru 
>>> > wrote:
>>> >
>>> >> Mitch Claborn wrote on 9/15/16 11:07 AM:
>>> >> > I'm very new in this type of thing. I have

Re: [VOTE] Release of Apache Tephra-0.9.0-incubating [rc1]

2016-09-16 Thread James Taylor 
Transferring my +1 from dev vote here.

On Thu, Sep 15, 2016 at 10:44 PM, Poorna Chandra  wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.9.0-incubating,
> release candidate 1. This is the second release of Tephra.
>
> Apache Tephra community has voted and approved the release.
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201609.mbox/%3CCAC9o21R4KR-e%3DmzCsefvokpQWykOXTTnWt%
> 2BZwt0CjiZz1MsqAg%40mail.gmail.com%3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201609.mbox/%3CCAC9o21Q9RJqDAo9n_AJWKaPm9_9iM4JoOL0bK9uh2thhS5Jn1g%
> 40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.
> 0-incubating-rc1/src
>
> The tag to be voted upon is v0.9.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.
> git;a=shortlog;h=refs/tags/v0.9.0-incubating
>
> The release hash is db235cdfa0d40d4e31bcd19ab350e9961719c79e:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=
> db235cdfa0d40d4e31bcd19ab350e9961719c79e
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1004
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/poorna
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.
> 0-incubating-rc1/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.9.0-incubating
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Poorna.
>