Ticket #474 (closed task: fixed)

Opened 5 years ago

Last modified 14 months ago

Package Criteria 'upgradepath' not clear

Reported by: jlaska Owned by:
Priority: major Keywords: meeting
Cc: kparal Blocked By:


Proposal topic

The AutoQA team is automating the 'upgradepath' test of the https://fedoraproject.org/wiki/Package_update_acceptance_criteria. Kamil Paral has identified several situations where it isn't entirely clear how 'upgradepath' should be handled. In addition, Kamil has outlined several problems with different solutions.

The AutoQA team would like to raise awareness of the problems, and seek guidance on how to incorporate updates-testing when testing upgradepath.

To summarize...

  1. Testing the base + updates repos seems rather straightforward (and is the common repo configuration). This is already implemented with the current upgradepath test, and seems to be functioning properly
  2. How to include and test for updates-testing isn't clear, for the following reasons ...
    1. Problem #1: What is the desired repo set?
    2. Problem #2: Removing repositories (--disablerepo=updates-testing)
    3. Problem #3: Unpushing packages


For details, see https://fedorahosted.org/pipermail/autoqa-devel/2010-September/001189.html

Problem space

Reach consensus on how the updates-testing repository should be considered when validating a package for upgradepath


  • AutoQA team

Change History

comment:1 Changed 5 years ago by kevin

  • Resolution set to fixed
  • Status changed from new to closed

We agreed in the 2010-10-12 meeting that we should not consider updates-testing at this time. Just don't test for it at this point.

comment:2 Changed 14 months ago by tflink

Apologies for the ticket necro but I was about to link to this and found out that the link for details doesn't work. The following link is the same information referenced in the ticket description.


Note: See TracTickets for help on using tickets.