For years I've been soldering with normal Sn60Pb40 solder wire. But now I try to switch to lead free solder. In many forums over the internet I found the Amasan BF32-3 solder wire. It's a Sn95Ag4Cu solder wire with 3.5% flux. 

So I tried it and was very disappointed. Nearly every solder joint was looking different. Some of them were (partially) shiny; some (the most) of them were dull. And the worst thing was, that even with additional flux, the solder didn't flow like the leaded. So there is no way, I could solder fine pith SMD stuff with it.

I’m using a JBC soldering iron station with a C245-907 2.2mm chisel tip and tried different temperatures starting with 290°C to 360°C. The best results I get with about 315°C, with 350°C I got the worst results. I used the Amtech NC-559 Flux – the original, not the fake from china. 

Some other guys told me, that maybe the solder wire is not the best. That's why I'm looking for other soldering wires. But there are so many on market. Some with copper, some are Sn96.5Ag3.5 like the Amtech ASN96A3.5-0.50.

So can someone tell me, with what type of solder wire or what product I can get nice shiny solder joints. And yes, I now that dull joints were not a sign for a bad or even cold joint.


Question: deployment taking longer time using changesets
Answer: Changeset deployment usually does not have SLA and what you have  experienced is an expected behavior. Deployment time will always vary and how long one deployment takes to complete does not become a benchmark on how long it'll take to complete another 

There are times when changeset deployment will hit a legitimate issue such as gack or a lock and when those occur, Salesforce support can definitely investigate and escalate to have the issue rectified. However in few cases the deployment doesn't hit any gack or lock.

If it took this long to complete may possibly be link to the the many post release patches Salesforce.com have been rolling out, as when a patch goes out active requests like changesets are temporary put on hold and resumed when ready, other possible causes of extended deployment time are size/types of component being deploy and how it affect/changes the org, heavy traffic on the instance or simply multiple deployment / validation holding up the total overall deployment process in the org. 

However we need to remember there are no SLA with changeset, but if you want to deploy quicker and have more control over their deployment, then IDE / ANT is the way to go.