As the fedora.us Extras merger with
fedora.redhat.com draws nearer, I
believe we should move all discussion to fedora-devel-list(a)redhat.com
list rather than continue on fedora-devel(a)fedora.us. The old list has
served us well for the past year, but I believe it will help to focus
all efforts on the new list.
fedora-announce(a)fedora.us will continue to operate for announcements of
new fedora.us package releases. fedora.us will continue to accept FC1
and FC1.90 packages for Extras inclusion. Later fedora.us will go into
pure maintenance mode, existing only to support fedora.us Extras FC1 and
earlier, and some infrastructure for the Fedora Legacy project. The old
Extras will be maintained in bugzilla.fedora.us and
fedora-devel-list(a)redhat.com as long as the community developers still
care about those packages. 1.90 is only temporarily at fedora.us mainly
as a staging area for importing to
fedora.redhat.com Extras CVS when it
goes online.
http://advogato.org/person/wtogami/
I wrote some more notes and random other stuff in my new blog here.
The goal is for the FC1 to FC1.90 rebuilt packages, fixed packages, and
a few more inclusions for Extras are to be imported into the CVS server
when it goes online "soon". I do not know how soon.
Please do not wait for the CVS. Continue submitting stuff to
bugzilla.fedora.us. Fix and QA the packages already there. The stuff
already published at fedora.us stuff will probably be imported first,
and developer track records there taken into consideration for "who to
trust sooner" with CVS access to certain package ACL's. (Of course many
other well known developers in the community will be given access
quickly if they follow the legal forms and other requirements that will
posted when it goes live.)
It is my personal goal to have the CVS and new infrastructure being
built at
fedora.redhat.com to accelerate development and lower time
overhead, without lowering the bar of quality that fedora.us has
achieved during the past year. More and better tools will need to be
written for automated package tests, GPG signing/checking requirements,
and other stuff in order to make these otherwise boring matters of
procedure seemless and quick for developers.
https://bugzilla.redhat.com/bugzilla-devel/
While on that subject, I realized I forgot to mention this earlier. dkl
has setup a non-production Bugzilla here where we can test Bugzilla
concepts, and perhaps more importantly, safely test XML-RPC interfaces
of command-line tools like the stuff ESR was working on. I am
personally not fully convinced that such tools will be effective, but I
am interested to see working code prove the concept.
Otherwise... kill those FC2 bugs. The 2.6 GNOME and kernel will be HUGE
for us as a community in so many ways. With your help, let us make this
the most awesome release ever.
Warren "little more than a cheerleader" Togami