On Aug 22, 2013, at 9:42 AM, Dennis Gilmore <dennis@xxxxxxxx> wrote: > > some of the things I would like to work on include, fully automating > the release process, today i have to do mutliple things from multiple > locations to trigger off the different pieces of the release. write a > tool like mash for pulling together the Live Spins and Images trees. > run pungi and mash inside of koji so that all parts of the release > compose process are done as koji tasks and make greater transparency on > what Release Engineering do. > get time to update all the documentation, and list out all the thoughts > in my brain and try to build a community around release engineering so > I don't have to work 60-80 hours a week just to try and keep up. > > work on a composedb that gives easier insight into where things are in > the release cycles. where releases are in their cycle, i.e end of life, > stable or in development, for stable releases when updates where last > pushed, or if updates push is in progress, for in development, last > nightly compose, last milestone compose, and if things are in progress. > > ive probably missed a bunch of things here but thats a brief dump of > some of what ive been wanting to work on for ages and not had thetime > to do so. Sooo, is about one week enough time for all of this? Or other? Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
