Direct upgrade (Dapper to Hardy) testing, can we help?

Asked by jefcanuk on 2008-02-02

I work at Free Geek http://www.freegeek.org in Portland, Or. We have a somewhat large base of Dapper users (a couple hundred or more) who, when the time comes, will want to upgrade to Hardy. Thus, the direct path upgrade is enticing for us. We also have a bunch of Dapper boxes and a huge volunteer base to help us test-upgrade them. My question is, how can we help? If we have bugs to file, against which packages should we file them? What kind of specific things can we do?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2008-02-02
Last reply:
2008-02-16
Joseph Price (pricechild) said : #1

According to https://wiki.ubuntu.com/HardyReleaseSchedule upgrade testing doesn't begin until February 14th at feature freeze.

I remember seeing the following call for testers: http://www.sourcecode.de/content/when-you-are-interested for quite a specific small set of packages.
I'm sure he'll still be interested if you can find any bugs with these, but as I said earlier, the real testing won't begin until feature freeze.

George Ganoe (geoganoe) said : #2

Now that the feature freeze date has past, I would be interested in knowing if the dapper -> hardy upgrade path is available, and what experience testers have had in using it.

Once it has been verified to work on some boxes, I would like to try it on mine using a copy of the hard disk that contains my production dapper environment.

Joseph Price (pricechild) said : #3

https://wiki.ubuntu.com/LTSUpgradesHowto is the wiki page set up to explain how to perform upgrades.

It links to http://ubuntuforums.org/showthread.php?p=4323348 which might be helpful to you.

Can you help with this problem?

Provide an answer of your own, or ask jefcanuk for more information if necessary.

To post a message you must log in.