Our company has a product line and most development happens on the trunk. We had 3 releases slotted back to back with the last one being an update to the first one. the first one is in 3rd party testing with the second in in house testing. The development of the third is completed but due to the amount of breaking changes was done on a separate branch of the first two. This code needs to be placed on nugget to prevent any checked in code from referencing the local developers computer. I don't want to make a nugget package for this branch as it will just die/get pruned when it goes into internal testing. I also don't want to override the current package as internal testing may require changes to be made, causing confusion in version numbers.
What is the best way to manage/publish branched DLLs using NuGet? should NuGet even be used?