On 04/25/2017 10:23 PM, Pierre-Yves Chibon wrote:
(adding the releng list on CC, please keep the reply on the infra list)
Hi Everyone,
Following up on the thread about pagure on the top of dist-git started a
few days ago Ralph Bean, Matthew Prahl and I had a quick meeting just a few
minutes
On 04/25/2017 01:54 PM, Jason L Tibbitts III wrote:
>> "KF" == Kevin Fenzi writes:
>
> [Using foo-owner@fp.o as the default owner for bugs]
> KF> But also disadvantages of people liking to see a name they can point
> KF> to about the package or know who is cc'ed on the bug.
My vote is that the default assignee be the owner of the Pagure repo. Since the
package email aliases will contain all users that have commit access on the
Pagure repo, it'll be too noisy.
___
infrastructure mailing list --
> "KF" == Kevin Fenzi writes:
[Using foo-owner@fp.o as the default owner for bugs]
KF> But also disadvantages of people liking to see a name they can point
KF> to about the package or know who is cc'ed on the bug.
For years I've wondered why we don't do that, honestly. But
On Tue, Apr 25, 2017 at 01:36:50PM -0600, Kevin Fenzi wrote:
> On 04/25/2017 08:23 AM, Pierre-Yves Chibon wrote:
> ...snip...
> > Now going through each of the requirements listed above
> > - Store point of contact for a package (default assignee on bugzilla)
> > - we could use the first
On 04/25/2017 08:23 AM, Pierre-Yves Chibon wrote:
...snip...
> Now going through each of the requirements listed above
> - Store point of contact for a package (default assignee on bugzilla)
> - we could use the first committer, alphabetically
> - we could use the 'owner', but we need pagure
On Tue, Apr 25, 2017 at 02:31:19PM -0400, Randy Barlow wrote:
> On Tue, 2017-04-25 at 16:23 +0200, Pierre-Yves Chibon wrote:
> > - Store point of contact for a package (default assignee on bugzilla)
> > - we could use the first committer, alphabetically
> > - we could use the 'owner', but we
On Tue, Apr 25, 2017 at 08:25:03PM +0200, Mikolaj Izdebski wrote:
> My experience shows that there are lots of packages without active
> maintainers, which are kept alive only by provenpackagers. Koschei is
> especially useful for this kind of packages as it allows others (usually
> SIGs or
On 04/25/2017 08:16 PM, Ralph Bean wrote:
> On Tue, Apr 25, 2017 at 07:59:46PM +0200, Mikolaj Izdebski wrote:
>> On 04/25/2017 07:48 PM, Ralph Bean wrote:
>>> On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote:
On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote:
> - Store
On Tue, Apr 25, 2017 at 07:59:46PM +0200, Mikolaj Izdebski wrote:
> On 04/25/2017 07:48 PM, Ralph Bean wrote:
> > On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote:
> >> On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote:
> >>> - Store koshei integration flag
> >>> - store this in a
On Tue, Apr 25, 2017 at 07:56:06PM +0200, Michael Šimáček wrote:
>
>
> On 2017-04-25 19:48, Ralph Bean wrote:
> >On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote:
> >>On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote:
> >>>- Store koshei integration flag
> >>> - store this in a
On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote:
> On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote:
> > - Store koshei integration flag
> > - store this in a yaml/toml file in the dist-git repo
> > - let the consumers
> > - do an http request to retrieve the file
> >
On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote:
> - Store koshei integration flag
> - store this in a yaml/toml file in the dist-git repo
> - let the consumers
> - do an http request to retrieve the file
> - listen to fedmsg to catch changes to this file (and update a local
>
(adding the releng list on CC, please keep the reply on the infra list)
Hi Everyone,
Following up on the thread about pagure on the top of dist-git started a
few days ago Ralph Bean, Matthew Prahl and I had a quick meeting just a few
minutes ago about the future of pkgdb.
Most of the content
On Tue, Apr 25, 2017 at 08:52:06AM -0400, Paul W. Frields wrote:
> On Sat, Apr 22, 2017 at 07:42:18AM -0600, Kevin Fenzi wrote:
> [...snip...]
> > So, IMHO, some action items we might consider:
> >
> > * Create a batcave02.rdu that has all our repos, ansible keys and dns
> > keys. We can then use
Just making sure the whole original message made it to rel-eng list.
Reply-to is set to infra@ so we can keep discussion in one place.
On Thu, Apr 20, 2017 at 12:08:35PM -0500, Dennis Gilmore wrote:
> Can you please report this to releng also?
>
> Dennis
>
>
> El jue, 20-04-2017 a las 15:45
On Sat, Apr 22, 2017 at 07:42:18AM -0600, Kevin Fenzi wrote:
[...snip...]
> So, IMHO, some action items we might consider:
>
> * Create a batcave02.rdu that has all our repos, ansible keys and dns
> keys. We can then use this to push things out if needed. It shouldn't be
> too hard to pull from
Reply-to is set to infra@ so we can keep discussion in one place.
On Thu, Apr 20, 2017 at 12:08:35PM -0500, Dennis Gilmore wrote:
> Can you please report this to releng also?
>
> Dennis
>
>
> El jue, 20-04-2017 a las 15:45 +0200, Pierre-Yves Chibon escribió:
> > Good Morning Everyone,
> >
> >
Good Morning Everyone,
Yesterday I prepared and tagged a 2.6.1 release but I messed up with the git
history, so I ended up creating a new release 2.6.2 today.
Here are their corresponding changelogs:
* Tue Apr 25 2017 Pierre-Yves Chibon - 2.6.2-1
- Update to 2.6.2
- Fix git
19 matches
Mail list logo