I just thought that we could use a "to do" system
- what is planned (in important and/or dependency sequence)
- what is the implementation phase, what is this state
- what is already being tested , how can it be tested
- what is done
Like a post-it wall (for example):
to do | doing | testing | done
-------------------------------------------------------------------------------------
*libpng bump | *new hompage | *kde4bump |*gnomebump
*kde5 | *pacman-g2 | *kernelbump | *blabla
*kernel bump | | |*blabla
*Fw 2.0 | | |
I like the trello, but It is just an idea, as the whole "to do" system.
Trello is spectacular post-it wall, so everyone could see what is happening
around Frugalware. The newbies, who is awakening from coma :)
I think that it would be transparent. In the "done" column will remove
tickets, after stable release.
2013/12/31 Miklos Vajna <[email protected]>
> Hi,
>
> On Tue, Dec 31, 2013 at 11:37:15AM +0100, Róbert Bagdán <
> [email protected]> wrote:
> > What is your opinion?
>
> If you have a set of questions, shoot, and we'll be happy to answer. If
> nobody knows the answer, James is the man to came up with something.
>
> Other than that, the usual practice is that each feature simply affects
> a set of packages and each package has a maintainer, so what happens is
> simply a decision of each package maintainer. The big picture is usually
> just a list of incompatible changes filling up docs/upgrade.txt for each
> release, and ideally you don't really notice the rest. :-)
>
> Or is there something in particular you're interested in?
>
> Miklos
>
--
( : kikadf : )
_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel
