[atomic-wg] Issue #263: open up read permission on our AMIs

2017-04-05 Thread Dusty Mabe
dustymabe added a new comment to an issue you are following: `` > My PR to libcloud to modify snapshot attribute was merged. So I will fix it > in fedimg too and do a release. yay! - can you modify existing images with the tool? `` To reply, visit the link below or just reply to this email htt

[atomic-wg] Issue #262: F26 Talking Points

2017-04-05 Thread Josh Berkus
jberkus added a new comment to an issue you are following: `` Yeah, we should definitely add something about System Containers. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list --

[atomic-wg] Issue #262: F26 Talking Points

2017-04-05 Thread Jason Brooks
jasonbrooks added a new comment to an issue you are following: `` These need some processing to suss out what's important, but f25 GA to current f26 is atomic 1.13.1 to 1.16.5: https://github.com/projectatomic/atomic/blob/master/CHANGELOG.md `` To reply, visit the link below or just reply to th

[atomic-wg] Issue #262: F26 Talking Points

2017-04-05 Thread Jason Brooks
jasonbrooks added a new comment to an issue you are following: `` With https://pagure.io/fedora-atomic/c/785b27dfeeeb6055af8b6581c247ca1412128dd6?branch=f25 did we actually start shipping more locales with atomic? That happened during 25 but after 25 first shipped. `` To reply, visit the link

Atomic WG Meeting Minutes 2017-04-05

2017-04-05 Thread Jason Brooks
#fedora-meeting-1: atomic_wg Meeting started by jbrooks at 17:01:22 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-05/atomic_wg.2017-04-05-17.01.log.html . Meeting summary ---

[atomic-wg] Issue #263: open up read permission on our AMIs

2017-04-05 Thread Sayan Chowdhury
sayanchowdhury added a new comment to an issue you are following: `` My PR to libcloud to modify snapshot attribute was merged. So I will fix it in fedimg too and do a release. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/263 __

[atomic-wg] Issue #263: open up read permission on our AMIs

2017-04-05 Thread Dusty Mabe
The issue: `open up read permission on our AMIs` of project: `atomic-wg` has been assigned to `sayanchowdhury` by dustymabe. https://pagure.io/atomic-wg/issue/263 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to c

[atomic-wg] Issue #264: 2WK Atomic Release Criteria

2017-04-05 Thread Sayan Chowdhury
sayanchowdhury added a new comment to an issue you are following: `` LGTM :thumbsup: `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/264 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscr

[atomic-wg] Issue #264: 2WK Atomic Release Criteria

2017-04-05 Thread Dusty Mabe
dustymabe added a new comment to an issue you are following: `` +1 from me `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/264 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an

Re: pagure notification outage

2017-04-05 Thread Dusty Mabe
On 04/05/2017 11:06 AM, Dusty Mabe wrote: > > Adding in fedora-devel > > On 04/05/2017 10:23 AM, Dusty Mabe wrote: >> >> I've identified that we have not been getting notifications from >> pagure for the past few days. I'm working with pingou to resolve this. > > We were not getting pagure not

[atomic-wg] Issue #253: lower case vs Initial Cap in Labels

2017-04-05 Thread Jason Brooks
jasonbrooks added a new comment to an issue you are following: `` > I'm ok with com.redhat.component for long and short term. However if we > decide we need a org.fedoraproject.component then can we just go with > com.redhat.component in the short term so that we don't block? +1 `` To reply, v

[atomic-wg] Issue #265: test issue

2017-04-05 Thread Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` test issue text - testing notifications `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/265 ___ cloud mailing lis

[atomic-wg] Issue #262: F26 Talking Points

2017-04-05 Thread Matthew Miller
mattdm added a new comment to an issue you are following: `` Can we combine 3 & 5 into one point? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org

[atomic-wg] Issue #262: F26 Talking Points

2017-04-05 Thread Josh Berkus
jberkus added a new comment to an issue you are following: `` Here's what I have per Dusty: 1. Switch to OverlayFS for default Docker FS. (but not one-big-volume for backwards compat). 2. Containerized Kubernetes as an option. 3. Rename media files (ISO, etc.) to match OStree release date. @dus

Re: pagure notification outage

2017-04-05 Thread Dusty Mabe
Adding in fedora-devel On 04/05/2017 10:23 AM, Dusty Mabe wrote: > > I've identified that we have not been getting notifications from > pagure for the past few days. I'm working with pingou to resolve this. We were not getting pagure notifications to our cloud mailing list. It turns out this i

pagure notification outage

2017-04-05 Thread Dusty Mabe
I've identified that we have not been getting notifications from pagure for the past few days. I'm working with pingou to resolve this. If you commented in the past few days and are looking for a response from me or someone else, please let us know via this list or in IRC. Dusty