> If you have ever owned a vinyl copy (or certain CD copies) of Magical Mystery Tour, you’ll know that it comes with a 28-page booklet containing song lyrics, drawings by cartoonist Bob Gibson, and scenes from the Magical Mystery Tour movie.
> [..]
> Yes, you looked at that correctly. That is John Lennon, dressed as an Italian waiter, literally shoveling buckets of spaghetti on this woman’s plate. You’re probably gonna want some context…
(Edit: and if I only scrolled further I see someone else already posted that link)
Funnily enough, I recognize this image from The Beatles' "Magical Mystery Tour" soundtrack liner notes (the image itself is from the movie). Why it's included in this article is lost on me.
We "Feature branch." With a twist on some of the busier repositories. We have a repository per application. We use Subversion (VisualSVN the Windows port)
1. Branch current live revision from Release to branches/ticket-ref (Our Release is what others may call main, trunk or master)
2. Work on feature.
3. Code review.
4. Merge to Release, CI (Jenkins) picks up change and builds NuGet package(s) pushes them to Octopus Deploy
5. Deploy into Test environment
6. QA pass/reject
7. If reject go back to 2.
8. If pass Deploy to production (single click in Octopus Deploy)
9. The twist for busy repositories with lots of changes: Cherry-pick merge to a Stable branch, which CI builds and pushes to Octopus Deploy Live channel
10. Deploy to production
Biggest issue we have is concurrent features x y z all being worked on, x y z are all deployed in test environment, y is passed by QA but can't be deployed because that versioned package also contains x which is rejected, so has to wait until x is fixed, which will then of course contain z. This is only really a problem when we want to get an emergency hotfix w into production. Right now we have to revert x y z from the Release branch, merge w build and deploy then put x y z back in.
This has taken 2 years to perfect so far. Changes we are considering:
a) Jenkins plugin that automatically creates a build configuration the moment you create a feature branch in SVN, this way we can keep x y z in separate versioned packages (I personally feel this is not true "integration" because you are keeping things separate.
b) Feature switches. So if y is good but x and z are not ready we just deploy with those features switched off.
We deploy on Tuesday/Wednesday/Thursday most weeks, never Friday - Monday.
The cheap imported rape seed oil blamed for the Spanish epidemic was probably a cover-up, it was actually pesticides being used in the cultivation of tomatoes. ( Posted earlier today here on HN: https://www.theguardian.com/education/2001/aug/25/research.h...)
A lot of conspirative theories arose of course, but the oficial version was that some oil destined to industrial uses was imported from French to Spain and sold door-to-door as edible oil by some unscrupulous sellers.
The case was not repeated since that, so tomato pesticides aren't really a strong candidate. A lot of the tomatoes eaten in Germany, Holland and other European countries are from Spain (and pass strict quality tests in those countries) and nobody developped the same symptoms ever. Tomato production created a new type of spanish landscape in fact, that we call "the sea of plastic".
In my family we use exclusively olive oil for all. In any case, I will love to taste the sazanqua oil, that is the equivalent to an olive tree for japanese and is reputed also as excelent. Have somebody tried it?
