Greetings,
Once all of aeolus* components are included in Fedora 16, how do folks
feel about re-purposing the existing fedorapeople repos under the theme
"aeolus-preview"? The frequency and methods of update wouldn't change,
but I suspect the use of the repo will alter after aeolus* is fully
included in Fedora. The preview repo would house, as the name suggests,
preview packages. Preview packages are mid-sprint updates (as bugs and
stories are addressed). Once the sprint finishes, packages could move
to the standard Fedora 'updates' repository, or just stay in
'preview' (whatever the team feels is appropriate).
My only comment is I don't think we'd want to update aeolus in
fedora with every sprint end. People running aeolus from fedora (vs.
from our upstream releases) shouldn't have to upgrade every 3 weeks
or so.
The virt folks use a similar mechanism for posting pre-release packages
for testing. From their wiki [1], these are the expected consumers of
the preview repo ...
1. Users who want things to stay stable and who aren't necessarily
expecting new features until they update to the next release of
Fedora - these are people with just the updates repo enabled
2. Same as (1) but who are willing to help out testing updates for
the whole distro in order to catch things before they hit the
people in category (1) - these people have the updates and
updates-testing repos enabled
3. Mostly the same as (1) or (2), but have a specific interest in
testing new [aeolus] features and are willing to deal with
[aeolus] regressions - these people enable the updates,
updates-testing and preview repos
4. People who are interested in helping with Fedora <next>
development in general, not just [aeolus] - these people run
rawhide
Thoughts/comments?
Thanks,
James
[1] https://fedoraproject.org/wiki/Virtualization_Preview_Repository
_______________________________________________
aeolus-devel mailing list
aeolus-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel