Jesse Keating wrote:
On Friday 09 February 2007 10:15, Rahul Sundaram wrote:
When you are composing the spin and doing the release announcement, it is easy enough to just point out the major changes.
Say GNOME KDE and Kernel x.y. Important feature z etc.
I don't always know this information, and it's just as much of a pain in the ass for me to go looking for it as it is for you.
Which is why I said that individual developers need to be more proactive on passing on important upstream as well as Fedora specific changes. Any single person doing it is going to be painful.
Incorrect. Test1 serves as a somewhat stable starting point for fleshing out the features that are planned for the next release. Especially if we wind up doing hackfests just after Test1 continually. A lot of the features aren't really suitable for testing by anybody other than the developer, but they need something they can install with their changes that actually installs rather than the more often than not broken rawhide repo at this stage. Test1 provides them a platform to put their package on and continue to develop it. Often times the feature isn't baked enough so that anybody else looking at it would do any good.
I think we are aiming at a different audience for each of the test releases. We need to agree on and pass on that to the wider folks involved.
Rahul
On Fri, 2007-02-09 at 21:08 +0530, Rahul Sundaram wrote:
Which is why I said that individual developers need to be more proactive on passing on important upstream as well as Fedora specific changes. Any single person doing it is going to be painful.
+1
It is a SERIOUS problem that Fedora developers, for the most part, do not make any content changes in Docs/Beats/. The space has been there for months, they could be making continual notes in public about their section of the release, but they do not.
We are missing a big opportunity here. I think FDP is doing all it can to move this forward. I escalated the problem to the board.
When it is this easy[1] to file a release note, there is simply no excuse not to do it.
[1] http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process#submitting
I think we are aiming at a different audience for each of the test releases. We need to agree on and pass on that to the wider folks involved.
+1 ... about time we do that. Make it very clear in the announcement:
test1 -- for developers, use at your own risk, contains many half-baked items
test2 -- for early adopters, most things should work and we REALLY NEED YOUR HELP to find what is broken
test3 -- for beta users, this is the place where we MUST HAVE full community participation; otherwise, when it is released and doesn't work on our hardware, it is you who suffers the most.
Like that?
- Karsten
-
Karsten Wade -
Rahul Sundaram