Scott McCarty wrote:
> Randy,
> I FINALLY had a chance to file this as a user story. Holy cow, you guys
> have 200 open stories :-) So, I thought I was busy, but I have no idea how
> you guys would ever have time to implement this ;-)
Hahaha, yeah we have a lot to do for sure. Thanks for
rom: "Randy Barlow" <rbar...@redhat.com>
> To: pulp-list@redhat.com
> Sent: Thursday, September 3, 2015 2:11:39 PM
> Subject: Re: [Pulp-list] Synchronize Git Repositories: Crazy?
>
> Scott McCarty wrote:
> > - Absolutely, is there a guide somewhere on how to star
On 4 September 2015 at 01:55, Randy Barlow wrote:
> +1 I think this is a great idea. I was thinking a bit about it, and it
> occurred to me that repo groups might be a nice data structure to do this
> with. We are hoping to move towards strongly typed repos, but nothing says
>
On Wed, Sep 2, 2015 at 4:27 PM, Scott McCarty wrote:
> All,
> I had an epiphany the other day, that I would love to be able to
> synchronize an entire stack:
>
> 1. RPM Content for OS
> 2. Puppet Modules to configure
> 3. Docker Images built from the above
> 4. RPM
On 09/03/2015 09:50 AM, Michael Hrivnak wrote:
On Wed, Sep 2, 2015 at 4:27 PM, Scott McCarty > wrote:
All,
I had an epiphany the other day, that I would love to be able
to synchronize an entire stack:
1. RPM Content for OS
Scott McCarty wrote:
> - Absolutely, is there a guide somewhere on how to start this off?
I don't believe we have any formal process documented for writing a
story, so I'll write some high level stuff here:
0) Use Redmine to file a new issue:
https://pulp.plan.io/projects/pulp/issues/new
1)
015 8:55 AM (GMT-08:00) To: pulp-list@redhat.com Subject: Re:
[Pulp-list] Synchronize Git Repositories: Crazy?
+1 I think this is a great idea. I was thinking a bit about it, and it
occurred to me that repo groups might be a nice data structure to do
this with. We are hoping to move towards st
All,
I had an epiphany the other day, that I would love to be able to
synchronize an entire stack:
1. RPM Content for OS
2. Puppet Modules to configure
3. Docker Images built from the above
4. RPM Content for Ruby Runtime
5. Gems for Ruby application
6. GIT repo for my code
I see Python