How This Works: We look at past #action items
from the last meeting for quick follow-up. If a task is completed,
we move on to the next one. If it isn't, we get an update and
re-action it if needed. If no status, we'll try to get a quick
update and move forward.(Rhea,
19:08:59)
IDEA: Single copr
repository with multiple packages following the dotnet-version
naming - e.g. dotnet-1.0 dotnet-1.1 which would always be the latest
(ie 1.0.4 / whatever)(Rhea,
19:18:34)
ACTION: Rhea issue to
dotnet/core-setup - Linux Packaging - what are we packaging, how do
we call it, how do we version it, what are dependences between, and
how can user combine versions/whatever at the same time(Rhea,
20:14:38)
=== [COMPLETE] Rhea rewrite the Idea #1 to
reflect recent findings ===(Rhea,
20:16:32)
dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/SIGs/DotNet ]
Rhea issue to dotnet/core-setup - Linux Packaging - what are we packaging, how do we call it, how do we version it, what are dependences between, and how can user combine versions/whatever at the same time
nmilosev create a ticket tracking source build for f26 (25)
Action items, by person
dotnet
dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/SIGs/DotNet ]
Rhea issue to dotnet/core-setup - Linux Packaging - what are we packaging, how do we call it, how do we version it, what are dependences between, and how can user combine versions/whatever at the same time
nmilosev
nmilosev create a ticket tracking source build for f26 (25)
Rhea
Rhea issue to dotnet/core-setup - Linux Packaging - what are we packaging, how do we call it, how do we version it, what are dependences between, and how can user combine versions/whatever at the same time