Re: Tying Dockerhub into development and release management

[Ross Gardler]

These would not be official releases. One or more of your community can create 
Docker builds from apache released source. Ideally the build files will be part 
of the ASF project.

Dockerhub has GitHub integration, so all it takes is for someone in the 
community to create the account and connect it to the repo.

Get Outlook for Android


From: lewis john mcgibbney 
Sent: Sunday, February 3, 2019 10:00:39 AM
To: general@incubator.apache.org
Cc: d...@sdap.apache.org
Subject: Tying Dockerhub into development and release management

Hi general@,
Over at the SDAP podling we are currently involved in a bit of a situation
regarding the use of Dockerhub in our development and release management.
The primary mechanism for the deployment of SDAP’s NEXUS component is
Docker. It is therefore necessary for us to have available Docker images
which can be consumed by people trying to consume and deploy the SDAP
software.
The issue we have run into however is that the availability of Docker
images in Dockerhub appears to be in violation of Apache release policy. Is
this true for all images e.g. tagged and version controlled, hosted within
Dockerhub or is it acceptable for us to publish version controlled images
in Dockerhub?
Can anyone share experiences facilitating the use of Dockerhub throughout
development cycles and for staging release candidates which include Docker
artifacts?
Thank you
--
https://eur02.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache.org%2F~lewismc%2Fdata=02%7C01%7C%7C6d9017f7dbc04dc1824c08d68a018b3a%7C84df9e7fe9f640afb435%7C1%7C0%7C636848136560161169sdata=d52cOLjekmHhjncZcdI8pMnKhlXmcdxuIOaSmBFf%2F%2Bk%3Dreserved=0
https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpeople.apache.org%2Fkeys%2Fcommitter%2Flewismcdata=02%7C01%7C%7C6d9017f7dbc04dc1824c08d68a018b3a%7C84df9e7fe9f640afb435%7C1%7C0%7C636848136560161169sdata=t4CngAQFIONjFr078NHVXCXsyOk1dmKQucQvwdp2F8M%3Dreserved=0

Re: Tying Dockerhub into development and release management

[Justin Mclean]

Hi,

> The issue we have run into however is that the availability of Docker
> images in Dockerhub appears to be in violation of Apache release policy. Is
> this true for all images e.g. tagged and version controlled, hosted within
> Dockerhub or is it acceptable for us to publish version controlled images
> in Dockerhub?

If they consist of code from a voted on release then that’s fine. This has been 
discussed a bit recently,  see these two legal JIRAs [1][2]. In short “It is 
appropriate to distribute official releases through downstream channels, but 
inappropriate to distribute unreleased materials through them.”

However I assume you asking about what to do with release candidates, my guess 
is to make sure they are not the default latest release and come up with a 
tagging scheme.

Thanks,
Justin

1. https://issues.apache.org/jira/browse/LEGAL-270
2. https://issues.apache.org/jira/browse/LEGAL-427




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

Tying Dockerhub into development and release management

[lewis john mcgibbney]

Hi general@,
Over at the SDAP podling we are currently involved in a bit of a situation
regarding the use of Dockerhub in our development and release management.
The primary mechanism for the deployment of SDAP’s NEXUS component is
Docker. It is therefore necessary for us to have available Docker images
which can be consumed by people trying to consume and deploy the SDAP
software.
The issue we have run into however is that the availability of Docker
images in Dockerhub appears to be in violation of Apache release policy. Is
this true for all images e.g. tagged and version controlled, hosted within
Dockerhub or is it acceptable for us to publish version controlled images
in Dockerhub?
Can anyone share experiences facilitating the use of Dockerhub throughout
development cycles and for staging release candidates which include Docker
artifacts?
Thank you
-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [VOTE] Release Apache PLC4X (Incubating) 0.3.0 [RC2]

[Christofer Dutz]

Also carrying over my +1 vote from the list.

Chris

Am 31.01.19, 12:24 schrieb "Julian Feinauer" :

Hello all,


This is a call for vote to release Apache PLC4X (Incubating) version 0.3.0.


The Apache PLC4X community has voted on and approved a proposal to release

Apache PLC4X (Incubating) version 0.3.0.


We now kindly request the Incubator PMC members review and vote on this

incubator release.


Apache PLC4X (incubating) is a set of libraries for communicating with

industrial programmable logic controllers (PLCs) using a variety of

protocols but with a shared API.


PLC4X community vote and result thread:

Result: 
https://lists.apache.org/thread.html/5ee3372ca4c2fd83952ec0e36e93a8bbcf5a8ecde72f75b324b60a5b@%3Cdev.plc4x.apache.org%3E

Vote: 
https://lists.apache.org/thread.html/eacbccd9b7f540a3bacff2eaf7420751252067977bcfab1679f8fb35@%3Cdev.plc4x.apache.org%3E


The release candidates (RC2):

https://dist.apache.org/repos/dist/dev/incubator/plc4x/0.3.0


Git tag for the release (RC2):

https://github.com/apache/incubator-plc4x/tree/release/0.3.0


Hash for the release tag:

ed21ab16d54601c01f7d97805aa1dd8d87a148e0


Release Notes:

https://github.com/apache/incubator-plc4x/blob/release/0.3.0/RELEASE_NOTES


The artifacts have been signed with Key : C336E0143A553B89, which can be

found in the keys file:

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


Look at here for how to verify this release candidate:


https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release


The vote will be open for at least 72 hours or until necessary number of

votes are reached.


Please vote accordingly:

[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove with the reason


Julian

Apache PLC4X

Re: Request for write access for wiki

[Julian Feinauer]

Indeed, strange, but nonetheless, thank you Justin!

Am 03.02.19, 12:02 schrieb "Justin Mclean" :

Hi,

> I request write access tot he incubator wiki to submit the Report for 
Edgent.
> My username is “jfeinauer”.

Looks like you already have permission.

Thanks,
Justin
-
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: Request for write access for wiki

[Justin Mclean]

Hi,

> I request write access tot he incubator wiki to submit the Report for Edgent.
> My username is “jfeinauer”.

Looks like you already have permission.

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

Request for write access for wiki

[Julian Feinauer]

Hi all,

I request write access tot he incubator wiki to submit the Report for Edgent.
My username is “jfeinauer”.

Thanks!
Julian

Re: [VOTE] Release Apache PLC4X (Incubating) 0.3.0 [RC2]

[Julian Feinauer]

Hi Justin,

thanks for your remark.
I had some issues initially but the key got found by cdutz and others.

I'll try to publish the key again to the server.

Julian

Am 03.02.19, 10:26 schrieb "Justin Mclean" :

Hi,

While you key is in the KEY file it looks like you KEY is not published:
gpg: assuming signed data in 
'apache-plc4x-incubating-0.3.0-source-release.zip'
gpg: Signature made Mon 28 Jan 08:57:37 2019 AEDT
gpg:using RSA key ADBD428CB5BF6C9FFC77B907C336E0143A553B89
gpg: requesting key C336E0143A553B89 from hkps server 
hkps.pool.sks-keyservers.net
gpg: Can't check signature: No public key

(not an issue but though I’d mention it)

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

Re: [VOTE] Release Apache PLC4X (Incubating) 0.3.0 [RC2]

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- incubating in name
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE  and NOTICE good
- no unexpected binary files
- all source files have ASF headers
- can compile from source

Thanks,
Justin


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

Re: [VOTE] Release Apache PLC4X (Incubating) 0.3.0 [RC2]

[Justin Mclean]

Hi,

While you key is in the KEY file it looks like you KEY is not published:
gpg: assuming signed data in 'apache-plc4x-incubating-0.3.0-source-release.zip'
gpg: Signature made Mon 28 Jan 08:57:37 2019 AEDT
gpg:using RSA key ADBD428CB5BF6C9FFC77B907C336E0143A553B89
gpg: requesting key C336E0143A553B89 from hkps server 
hkps.pool.sks-keyservers.net
gpg: Can't check signature: No public key

(not an issue but though I’d mention it)

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

Re: [VOTE] Release Apache PLC4X (Incubating) 0.3.0 [RC2]

[Stefan Bodewig]

repeating my +1 vote from the dev list

Stefan

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