On Thu, 07 Apr 2011 13:36:05 +0800 He Rui <rhe@xxxxxxxxxx> wrote: > Greetings, > > I haven't received any update on this project since the ticket filed, > is it under progressing or is there anything we need help with? We > planed to set it up this month or next, so please keep an eye on it. I could probably help you guys out with this. ;) I guess the first step is to make sure to get the package into EPEL (which it looks like it's already under review). After thats done, we could look at testing it on a publictest instance. I'll add this information to the ticket as well, but do ping me when we are ready to do more planning. ;) > Many Thanks, > Hurry kevin -- > On Mon, 2011-03-28 at 15:14 -0400, James Laska wrote: > > On Tue, 2011-03-15 at 16:54 -0400, James Laska wrote: > > > Greetings, > > > > > > I am in search of sponsorship for hosting space to deploy a test > > > instance of nitrate [1]. Some of you may recall several years > > > back when we deployed an instance of Testopia. That exploration > > > was cut short when we discovered license incompatibilities > > > between testopia and Fedora. At that time, a small group of Red > > > Hat associates began creating a new Django-based test management > > > system to remove the components that had conflicting licenses. > > > That new system became nitrate [1]. > > > > > > The Fedora QA team would like to experiment/explore this newer > > > Django-based test management system. At the very least, I > > > believe we'll need a publicly accessible server where we can host > > > the nitrate instance and a mysql database for it. > > > > > > I filed ticket#2673 > > > (https://fedorahosted.org/fedora-infrastructure/ticket/2673) to > > > track this request. Please don't hesitate with any > > > questions/comments/concerns. > > > > Hurry (rhe), Danqing (dli) and myself will be able to assist with > > the draft RFR guidelines proposal at noted in ticket #2674. This > > includes ... > > > > 1. Applying rpm updates to the service (and to any underlying > > pieces of the application stack) if necessary. > > 2. Applying hotfixes via the puppet hotfix module if there's a > > securiry fix or bugfix that needs to go in and it's not > > worth spinning a new rpm. > > 3. Keeping up with upstream development > > 4. Answering questions about whether a yum update (to your app > > or to the underlying stack) might break your app. > > 5. Fixing things should an app start throwing errors in > > production for unknown reasons > > 6. Work on deployment problems > > > > Don't hesitate if there are any other concerns or questions on this > > pilot and RFR request. > > > > Thanks, > > James > > > > [1] https://fedorahosted.org/fedora-infrastructure/ticket/2674 > > _______________________________________________ > > infrastructure mailing list > > infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > > https://admin.fedoraproject.org/mailman/listinfo/infrastructure >
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
