Hi André and all, I agreed with your post link. It'is important trace and organize activities and in general there two types of process to handle:
1) use issue/project for single sabayon project that could be managemet with a release process. For example sabayon/molecules could have different phases and release: enhancement/bugfix, migration to mottainai, integration with genuinetools-img, etc. In this case is important trace and help users what activities are pending or related with next releases 2) use issue/project for major target as release sabayon 18.x that is related to different sabayon/project (fox example release trace testing , integration activities, documentation, bump packages required for release, major packages tree changes as migrate to python3.6, etc.). For this I agreed with idea proposed by Enlik for identify a project used for this scope directly on github. For this I propose something like Sabayon/releases or Sabayon/targets or any other nerd name :) My cent. geaaru On Wed, 2018-04-25 at 18:57 +0000, André Jaenisch wrote: > Hi, > > after reading https://opensource.com/article/18/4/keep-your-project-o > rganized-git-repo I remembered that we had the topic GitHub boards on > the list. > > What's our current status here? > > Cheers > > > Ryuno-Ki > > > > -------- Ursprüngliche Nachricht -------- > Von: "Sławomir Nizio" <slawomir.ni...@sabayon.org> > Gesendet: 13. März 2018 20:46:04 MEZ > An: devel@lists.sabayon.org > Betreff: Re: [sabayon-dev] RFC: using GitHub to track ISO releases > preparation > > OK, looks like the Kanban board is the pet we like. > > On Github, the board can be made of (classic) issues and notes. I > believe notes are enough as replies to this thread don't suggest we > need > anything special from issues. (Still, they can be mixed so there's > no… > issue.) > > Anyway, > shall I go and create a "project" for the great Sabayon <heck, how > will > it be called?> release that is in the works? > >
