Hi,
for those who weren't on IRC I asked whether we should add a donation list
Like Linux Mint is publishing to our site:
https://blog.linuxmint.com/?p=3555
Plus, whether it makes sense to track position in DistroWatch and Alexa (not
the Amazon product).
Cheers
Ryuno-Ki
-------- Ursprüngliche Nachricht --------
Von: Geaaru <gea...@sabayonlinux.org>
Gesendet: 4. Mai 2018 16:28:59 MESZ
An: sabayon-dev <devel@lists.sabayon.org>
Betreff: Re: [sabayon-dev] RFC: using GitHub to track ISO releases preparation
For me, let's go with Kanban board!
Try to push a first list about what we need for next release.
From my side I think to add in list these:
* release new entropy version
* to added gaming-live ISO (with last mesa, libdrm versions/master)
to push new users to sabayon
* Move iso creation inside Mottainai
* (maybe fwiu) move to py3.6
* enhancement of sark crc hashing algorithm and check (i'm
working on this) to avoid i/o intensive disk operations
and fix check on python packages
* (fwiu related tu Ryuno-Ki irc messages) something about
push donations
* push LXC/LXD 3.0 integration and add documentation on website
(this need some fix on kernel config to use all available
cgroup options and checkpoint restore)
* move to calamares
* (proposal) to have two different kernels.
hypothesis A: kernel desktop-oriented (current) +
kernel server-oriented (current+bpf+
hypothesis B: kernel stable (current) +
kernel staging (that permit to add new config
options with a staging test phases. I see
that to use bpf it is needed enable
some kernel hacking options that sometime
generate some kernel exception so try to
enable soon on stable tree could be hazard)
Are there any others things pending ?
WDYT ?
My cent.
G.
On Sat, 2018-04-28 at 13:56 +0000, Sławomir Nizio wrote:
> > I agreed with your post link. It'is important trace and organize
> > activities and in general there two types of process to handle:
>
> These can be valid ideas, but my mail will be about the board to
> track
> issues related to making a release which is my main concern.
>
> Everyone who expressed their opinions were positive. I saw that lack
> of
> something like this was causing confusion and possibly delays, and
> with
> one properly managed, release coordination will go more smoothly!
>
> The Kanban board for this can be created now or just before the new
> release.
>
> My view is that is should only track activities being done for a
> release, so that the scope, progress, etc. are visible in one place,
> by
> everyone.
>
> Wishlist/planning could be done as now (IRC/ML/whatever), or in a
> separate board. The idea is to have a very simple view with only
> stuff
> that matters most, without distractions.
>
> In any case, let me know if I should set up an empty board now, or
> we'll
> do it later as needed.
>
