On Mon, Jul 21, 2008 at 3:41 PM, Morgan Collett
<[EMAIL PROTECTED]> wrote:
> On Mon, Jul 21, 2008 at 11:52, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote:
>> On Mon, Jul 21, 2008 at 8:35 AM, Simon Schampijer <[EMAIL PROTECTED]> wrote:
>>> We have the 'package' option as well. I guess this is what
On Mon, Jul 21, 2008 at 08:35:10AM +0200, Simon Schampijer wrote:
>We have the 'package' option as well. I guess this is what needs to happen
>after
>checking into git. 'package' is then doing the tarball release and 'add to
>build'
>building in koji maybe?
Packaging is the production of rpms
On Mon, Jul 21, 2008 at 11:52, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 21, 2008 at 8:35 AM, Simon Schampijer <[EMAIL PROTECTED]> wrote:
>> We have the 'package' option as well. I guess this is what needs to happen
>> after checking into git. 'package' is then doing the tarball
On Mon, Jul 21, 2008 at 8:35 AM, Simon Schampijer <[EMAIL PROTECTED]> wrote:
> We have the 'package' option as well. I guess this is what needs to happen
> after checking into git. 'package' is then doing the tarball release and
> 'add to build' building in koji maybe?
I'm not sure what's the mean
Marco Pesenti Gritti wrote:
> Hello,
>
> I noticed several inconsistencies in the way we deal with tickets,
> which makes working with trac harder than it should be. Here is an
> attempt to describe the workflow from the Sugar point of view:
>
> 1 Developer looks for the first time at a ticket. I
Hello,
I noticed several inconsistencies in the way we deal with tickets,
which makes working with trac harder than it should be. Here is an
attempt to describe the workflow from the Sugar point of view:
1 Developer looks for the first time at a ticket. If the problem is
obvious, switch action to
6 matches
Mail list logo
