On Saturday 03 January 2009 07:23:51 am Carlos E. R. wrote:
On Saturday, 2009-01-03 at 05:38 -0600, Rajko M. wrote:
Absolutely.
At worst, "zypper dup" could install a log or notes saying "don't test this", "known issues", etc.
Carlos,
See how long it takes to come from this: http://en.opensuse.org/Bugs to this http://en.opensuse.org/Bugs:Most_Annoying_Bugs ?
No factory section.
It is a wiki. You see article about Smolt. I liked idea and put article. Someone else added current workaround. I formatted and shaped that. Now, I hope that other will pick up and add more content, and that will bring more people using it, adding features and squashing bugs. If you miss Factory in most annoying bugs, make entry on wiki, update it every week, or month, with bugs that you care about, and let others do the same for their itch.
Is it something illogical in idea to look on the wiki for announcements? Second place: https://bugzilla.novell.com/query.cgi type in component name and you will get all related bugs.
Frankly, if I'm going to test a package included in factory, I assume it is ready for testing. I assume that it is thought to work, and that the devs wan us to test it now.
You had problem with kernel, and you know that you can test only the part of the kernel that you have hardware for test, so don't blame developers for broken drivers. The most that they can do is to write readme, or use wiki and list bugs there.
Thus, if I install factory, and think "hey, today I'm going to see how OOo works" - I'm not going to go search Bugzilla for all known issues, that's too long. However, in this case, the devs knew that OOo was not ready for testing...
So where they should put OOo? The only solution is to ship the older one, but do they have one that works with current environment.
Where else to publish information? Remember that we talk about test version and people that want to be testers, that must have above average to analyze situation and look for solution.
Yes, but I do not want to waste my time either.
If testing is for you waste of time, then it is time to take a rest and let other folks do it. I feel tired and I'm didn't take that much time testing last round, and I don't feel guilty at all.
While I agree that even Factory must have well known release day, as current way of changes that happen anytime leads nowhere, asking to announce problem in more places than it is already announced will not help.
Maybe. The wiki is a place, but an email here or a log file in the distro is probably even easier than writing up in the wiki.
Carlos, there are few mail lists that give you reports on bugs and package changes: opensuse-bugs Broadcasts all changes that are being made to bugs opensuse-commit Check in commit logs for Factory opensuse-features Broadcasts all changes that are being made to features opensuse-security-announce Announcements concerning security There few more related to YaST and zypper. For instance check this: http://lists.opensuse.org/cgi-bin/search.cgi?query=OpenOffice it is case sensitive, and there is link to Advanced Search, where you can limit number of results, by specifying for instance what mail list, or data range is your interest. As I said if all that is already provided is not enough, what else to do. Write it on default wall paper? -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org