Depends on how you want to organize the code. Today i create a git repo per
package ending up in appr. 5800 repos. It is ineffective to check out all
packages each time you want to build just one package. With individual repos i
assume using the issue/bug feature is good. If you using one repo with all rsel
specs in it i fear it will end up in a big mess.That said, i havent tried using
it this way - but i remember that browsing RepoForge's github repo (with all
specs in one repo) often crashed my browser :/
BR,Bjarne.
_____________________________
From: Gordan Bobic <[email protected]>
Sent: mandag, april 4, 2016 9:12 PM
Subject: Re: [RedSleeve-Users] missing bugs
To: <[email protected]>
Mantis is back up. I would still like to discuss any pros/cons of using
github's functionality for bug tracking since it looks like we will end
up using it for other things anyway.
On 04/04/16 13:53, Gordan Bobic wrote:
> On 2016-04-02 22:43, Gordan Bobic wrote:
>> On 02/04/16 22:29, Jacco Ligthart wrote:
>>> Hi Gordan,
>>>
>>> it seems that the mantis bugtracker is gone.
>>
>> Yes, as is the website. I haven't got them back up yet following the
>> migration. I'm working on it.
>
> I've been thinking about this - if we are going to move various things
> into git for Koji purposes, as Bjarne described, and if that ends up
> meaning we put it on github, how about we use github's "issues"
> functionality for bug tracking, as per what we had with Mantis before?
>
> Any objections from anyone?
>
> Gordan
> _______________________________________________
> users mailing list
> [email protected]
> https://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
