Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Happy Thanksgiving! Thank you for waiting for this new release of avatar items! We have new pets, new computers, new eye wear, some fun shirts and a special treat for our #1 ranter @linuxxx. The required ++ pts for these are a little higher than normal to reward the dedicated people who have helped support and build this community over the last few years. Thank you all!
33 -
Alright fuck it, let's release this fucker!
https://lynkz.me is the main domain. The interface is *usable* and nothing more than that. I'll invest more time in that soon but for now, hey, it works.
Api is located at https://api.lynkz.me.
Documentation for this (literally some echoes to the screen but it contains the needed information for now) is at that api url.
Found a bug or a security vulnerability? Please let me know!
Yeah I use mariadb but sql injection is luckily not possible due to quite some sanitization ;)
WARNING: if you make a shortened url and forget the delete key, you won't be able to delete it.
Let's see how this goes 😅111 -
Spent most of the day debugging issues with a new release. Logging tool was saying we were getting HTTP 400’s and 500’s from the backend. Couldn’t figure it out.
Eventually found the backend sometimes sends down successful responses but with statusCode 500 for no reason what so ever. Got so annoyed ... but said the 400’s must be us so can’t blame them for everything.
Turns out backend also sometimes does the opposite. Sends down errors with HTTP 200’s. A junior app Dev was apparently so annoyed that backend wouldn’t fix it, that he wrote code to parse the response, if it contained an error, re-wrote the statusCode to 400 and then passed the response up to the next layer. He never documented it before he left.
Saving the best part for last. Backend says their code is fine, it must be one of the other layers (load balancers, proxies etc) managed by one of the other teams in the company ... we didn’t contact any of these teams, no no no, that would require effort. No we’ve just blamed them privately and that’s that.
#successfulRelease4 -
I might start naming our release tags as Kraken-x.x
That way on launch day I can legit order the team to RELEASE THE KRAKEN.2 -
Never, ever, ever, release on a Friday. But.....
if you do.
Add this step as part of your production push process.
2 -
A client obsessed with *security* won’t give us access to the server that hosts the website we built.
Code release involves building templates, compressing the changed files into a zip folder, and emailing them to the client with instructions on where the changed files go8 -
The "new guy" just merged master into a release branch.
The build server started bumping versions on the release branch and build "corrupted" installers.
Another developer had to spend a whole day trying to remove all the invalid commits.14 -
I am puching myself over this one.. This made it into the official release. And this is one of the public screen shots that I saved to my phone from my devBlog.
How did I not see this??
.. "SizeTest" ..
21 -
Don't you love it when there is a new minor release or a critical dependency and it breaks backwards compatibility without mentioning any of it in the changelog or docs?
I absolutely love it! ❤️❤️❤️❤️❤️
I certainly did not waste 3 hours of my life to find it. No i didn't. -
One of the better filler release notes I guess. Not as good as Slack or Discord but still better than Google.
1 -
“In order to release on production you merge on production”
Makes sense.
“In order to release on staging you merge on release”
Wait, what?
“The CI for the staging release is called release to production”
What? No, stop!
“You also need to create a tag called pre-production-deployment, so that staging can work”
STOP FFS
“It’s very easy, you just need to read the documentation!”
How do people do not realise they are spitting out bs?3 -
Oh, well, of course ...
I thoroughly enjoy that both Google apps have different bullet point styles.
1 -
Backend: Sorry the fix we had isn't going to work. Turns out app is sending an "undelivered" status after you call the API where you claimed we had an issue. This is in fact the cause, please address it.
Me: We do not have an "undelivered" status anywhere in our codebase. We do not do this.
Backend: *CC product* turns out this issue is only affecting 0.1% of users, its very minimal. Lets push ahead with the release.
Product: Ok, lets go live.
Me: ... ... ... we all just gonna ignore that "undelivered" bullshit? ... ok ... very stable release, here we go.3 -
Boss came to me earlier
Boss: There's a critical issue with this release version for this project. Make sure it doesn't get deployed to our test/live environments!
Me: ...
Me: ...
Me: Err, that release went live 3 months ago... -
Me: "I've just released a new app"
Everyone I know: "I've got a great idea for an app.... I'll give you 10%"
Every. Single. Time. -
That moment when you had a good weekend and it is Monday again.
You log in to your work PC and see 15 emails... There goes my Monday again.
And 12 of those turn out to be congratulations on the recent release 😥3 -
Getting tired of certain co-workers under-delivering. They commit an entire release to one feature and my team plans our release expecting we'll be able to use his changes by the end and then on the last day of development he decides more testing is needed and it won't be finished until next release. Come on, man!
-
My raspberry Pi finally arrived ☺️! Now i just have to set it up... Any advice on what linux distro i should put on it? (i will use it as a NAS, torrent server and pi hole)
7 -
You know it's going to be an interesting day when you see a release note containing "migration" and "cross your fingers" in the same sentence 😅2
-
Worst dev disaster
I was responsible for allowing users to purchase a six month premium plan in our app for free.
Only way we got to know about this was that a customer himself emailed us saying we are allowing users to get premium access for free.
Thankfully he emailed us within a day of the release and we didn't incur massive losses.5 -
To all of you that is saying Friday release is horrible, you have no idea how bad Monday release is :(2
-
When you don't want to explain what you've done with application's code base so you play the "algorithm" card.
Boss: tell me about the new release.
Me: updated the search algorithms boss.
Boss: cool. Release!
Me: 😎 -
Laying in bed with a huge headache while the alpha release is at Sunday (own company) and the main feature isn't even written yet 😫 fml hard.5
-
Want to travel to the future? Release on a Friday. You'll be experiencing your weekend as if it were Monday.1
-
I'm actually a Dev, mostly just a shell scripter who needs to support 500 servers which run our applications. I install the new versions and check whatever is wrong if there are customer issues.
One release weekend everything went wrong, Development had to make new builds on the fly with hardly any time for testing.
It took 18 hours with no break.
It was extremely hard to concentrate, but being in the Skype group with everyone and finally getting everything fixed was quite rewarding.
Everyone just opened a beer and we stayed on the call for about 30 more minutes just to relax.
I like our Dev team way better than I like my actual colleagues, who merely mess things up and call me for the smallest thing without even thinking.4 -
I'm pretty stoked on the future release of SemicolonJS... It will change webDev as we know it. 😎
http://semicolonjs.com
@dfox, @trogus when is the release?8 -
Finally we release November release in December. All developers united against sneaky bugs.
God bless (drawing by me)
2 -
I spent two days in a row fixing chairs at work because our whole dev team was waiting for issues (which means helping QA team and playtesters testing the whole game).
Just when everyone left and Im standing up to go as well a playtester comes up with a release breaking bug in the handwriting recognition code...
Since this game is build for a charity which will release it in a country at war we cant push the release date.
Guess who is making overtime trying to fix this bug?3 -
How the fuck does someone releases a new version of a package without testing one of the core features of that package?
Spent fucking hours, hitting my head on the wall, only to realize that the latest build they have released has a bug. This is not acceptable :@2 -
Dat moment when your contact person phones you and ask If you delete the whole Release Folder...
YEAH SURE I WAS IT BECAUSE I LIKE TO WORK ON WEEKEND
Fyi: FTP with one user for everyone - harhar stupid bricks -
The company bought an iPad so I can test my work on a real device, but I can’t use it because the latest iPadOS beta release isn’t compatible with the latest Xcode 11 beta release 😒2
-
me 2 weeks ago: "can we talk about the release?"
pm: *proceeds to circlejerk about story points for an hour every day*
pm today: "why is our release late?"
dear management, go fuck yourselves. seriously, go fuck yourselves7 -
For fucks sake...
If it is a new feature, out of scope for the next release ...
It is OUT OF SCOPE FOR THE NEXT RELEASE, MKAY?????4 -
That moment when you need badly to go to the toilet and your boss stops you to have a long discussion7
-
So a few weeks ago, our PO really scolded my team for not letting him in on our release planning meeting. His rant went on for about 30 minutes, just one long monologue about why he should be invited in the future.
Apparently he wanted to know details since there were some important fixes in the release, which I suppose is fair (though the rant is really not necessary).
Fastforward 2 weeks, we invite him again. He accepts, but never shows up. We decide to start the planning anyway, since we don't want the release branch blocked because someone didn't show up.
Immediately after the meeting, we write him with the new release plan. And he starts ranting again about "planning without him" -.- ..
1) Stop yelling at the team you're supposed to work with. Talk with the team about it - I'm sure they'll listen.
2) If you demand being in meetings, show up - or at least decline in advance.
3) You have no right to rant about "not being part of the planning" when you were literally invited for a planning meeting 2 weeks in advance. No meetings were overlapping, so there's literally no excuse..1 -
Mhm yes, release 1.0.0
Hello World now has auto-centered text,
a feature Ｅｖｅｒｙｏｎｅ including
your { user.pet.type } has been asking for,
management assures me.1 -
oh microsoft...
you used to put the artifacts in
bin/Release/net6.0/publish
now you just put them in
bin/Release/net6.0
fucking garbage thanks for the heads up
it's golang from here on out
go run main.go && echo 'byebye fucksticks'4 -
I'm not going outside until like 3 months after they lift the restrictions. I'll let y'all deal with the bugs and crashes and resurgences. I'm not really an early adopter. I'm gonna wait until they release outside 4.2 the stable patch1
-
> In an online team meeting where our manager is telling us to wrap up the final bugs and get the release out as soon as possible so we can enjoy Christmas and the last week of the year stress free
> Opens LinkedIn while in the meeting since all my discussion points are done
> First post on my feed
> mfw
5 -
No! I don’t have any problems that you are deprecating various libs that I used in my software. Just don’t fucking insist that your code is production ready and stable and backward compatible. Please
-
Flutter 1.0 is announced and they even planned to make Flutter for the web in the form of Hummingbird. Exciting times.5
-
When someone asks you to test something before pushing a release...releases anyway and tells you any fixes can just go in the next minor release 😫4
-
YOOO Product owner if you don't specify which freaking page something doesn't work I CANNOT DO ANYTHING FOR YOU!!!!2
-
A client asks me to produce a Release note when publishing a new version, which is more than fair ask, I shall deliver.
Then he asks me questions on the version's feature which are clearly described in the release note, with examples, showing he did not bother to read it..............
...
2 -
The best?
I managed to release the new version of the best selling main product of my company.
The worst?
At the release it had critical bugs I didn’t find during the tests. -
Going to release the biggest feature I have implemented for Product I work on. Change in more than 150 files and it is very very critical.
Wish me luck..3 -
Ok, time to start working on things
*Twenty One Pilots casually release 2 new songs, a music video, album release date, tour dates*
Fuck that let's just fanboy all day3 -
Man I am tired of my company's dogshit software release process.
We have to commit to fucking estimates for 6 months (2 quarters), SQA shadowing dev by 2 weeks, and freaking estimates and work done at the end are not even close. And then we call it a minor release. These shitty estimates are based on requirements that basically say "we want feature x, plz make it work". It's some fucked up agilefall garbage that does not work for shit.
We rush like motherfuckers during the final weeks because estimates are bullshit but we are still expected to be done with every story points which somehow are days instead of other better metrics.
I swear this fucking bullshit has been designed by the board so they could plan their money entries based on the software release.
The only reason this company actually still holds itself up is because the engineers are good at their job.
Go fuck yourself high management. -
"We are releasing today" - sentence my project/tech manager keep saying for a week now. Of course, we changed few core components during the week - because, why not - and nothing works now.
-
My first packages, uploaded to nuget!
A simple neural network library, written in C# (.Net Standard)
Here's a link:
https://nuget.org/profiles/Mitiko233 -
Who thought that "IP" was a good replacement for ifconfig... I don't care how great it is, you can't Google for "release DHCP IP" and get instructions like you could for "release DHCP ifconfig"1
-
For some reason github is returning 503 on our build servers randomly. And I need to checkout several repositories to build everything successfully. Builds are automatic and I don't want to maintain local mirror. And we wanted to release tomorrow (but were smart enough to promise this week). And on top of everything build takes six hours and sometime fails randomly even without github. But I'm still optimistic - it's Monday after all. We still have enough time to make it in time for Friday release :-)5
-
Today is release day
Today is also the day we add couple of features for the release that will take a week to implement
Life is just won-fuck-erful -
Ran an app release yesterday, adding some new stuff and fixing a few bugs. Was scared this morning because APM didn't have any errors and the app was already in use by half of the userbase.
Turns out it's the most stable release so far! Day's all good again :D -
Why they are keep assigning tasks (new features as minor fix) till release date. And want me to complete it a week before release date.
HOW?2 -
when the release date is may 31 and the client thought it's a good idea to request a bunch of new features and changes in friday afternoon :)
Tomorrow is gonna be a fun birthday... -
After many months of hard work we are finally near to release the new website. It feels amazing and is such a relief. Some days it seemed like everything was against me but it's in times like these I am so glad to be a developer.2
-
Planned release today, one of my co-worker's laptop's hard drive died in the morning.
And you guys say Satan is not real :/1 -
okay, this is fucking ridiculous. my bank released an update of their pushTAN app and I just had to call their service center to learn how to interact with the "new" UI to release an order.
quiz: how do i release an order in the UI shown in the screenshot?
(auftrag freigeben = release order, ablehnen = decline)
19 -
I am the old famous kiddy here, who just came back days before school exam starts^^
Just to say, I want to ask you all, is it ethical(?) to release a hacking/cheating creation tool for games for educational™ purposes?
I have been making a cheat creation tool called Mysterium, but I am not sure where to use it. I made cheats for some big title games, and reported them to the developers, patched, and got some in game items in return....
Long story short, is it okay to release to the public, or should i release this product to game developers?
Sincerely,
A kid who made cheats since he can't play games well and wanted to get some free items4 -
Release on Monday === almost 10h of code today... Though it's just an internal release, so not that serious really. Though it's be fun to have something we've been working on for half a year working decently the first time people actually get to try it... Well, well...
-
Company i applied for told me how they are planning to release a new project on friday.
... Decided for a different company -
HIT THAT MOTHER!)#%Y!)!!! BREAKPOINT!!
...
...
...
...
God damn it, it's in Release configuration again.2 -
So as expected, due to the rush of the submission on Friday, the app was rejected.
I'm fairly certain they never got past the first screen or two.
We have some things to fix, and some things to tackle properly now, which is quite nice, however the current main issue numero uno is that an Apple developer account can take up to 10 days to be created, and Go Live is next Monday.
I wonder who will get the blame for not taking on the "Investigate the iTunes release process" ticket that was in Jira, assigned to someone for ~4 months. -
Deployed to production on Sat evening while drunk, surprisingly everything went smoothly. I think this was the first and last time I'll be releasing like this, lol.
Similar stupid experiences anyone?3 -
To all guys who write shitty code:
if (false)
I just found that when compiling for Release mode in Visual Studio the JIT compiler eliminates this:
Dead code elimination - A statement like if (false) { /.../ } gets completely eliminated.
And a lot of other similar stuff2 -
I've been compiling the project for about 5 hours now, still no successful build due to bad tests generating intermittent test failures...
All I wanted to do was to release the web project to the customer not fucking wrestle Cthulhu!
The worst part is that the release is set up so that you need to release the entire project internally before you can release one part.
-
Saturday and a new VSCode Insiders release?
Normally there is no new release on the weekend. Well done Microsoft, except for the fact that I now have the following message in the terminal: "your 131072x1 screen size is bogus. expect trouble" :)
Otherwise, the performance of the current release (code-insiders_1.17.0-1506717283) is way better than the previous one.4 -
So, I'm on holiday for a week from Friday. Woo! The plan is to head to a cottage in the middle of nowhere with the wife and the dog and chill the fuck out for a while.
Just found out from my boss that, due to some fucking colossal mismanagement, I have to support a huge release for an architecture rebuild project from 10pm til 8am on Sunday night. While I'm on holiday. In the middle of nowhere.
FML2 -
probably when 8 hours before rushed release i pushed my part of the codebase into the wrong branch which fucked up everyone else's rushed release of different parts of that codebase and now a colleague had to spend several hours unfucking the repo on top of finishing the rushed release of his part of the codebase.
oh and in the end my code didn't even work as it was supposed to.7 -
What the Fuck!!!!!
Within next 3 days my Release date was set. I was to join a new company. My current fucking manager screwed things by postponing my release date because the new replacement they hired had not totally understood the project. Well, who the fuck told you to hire literally few days away from my release. My manager expects that the new resource learn everything I know. Fuck off man, I cannot spoon feed a person on everything.1 -
Finally end of the week. All that is left is a little polishing over the weekend for Monday release. Like get the lastest code from all the developers, put it together and hope it somehow works and fix whatever doesn't :-/
-
I had a great dream last night of finally finishing a project I've been working on for too long and pushing to prod. I awoke to find magic doesn't exist and I still have to complete it. Saddest morning in a while.
-
my first ever release
https://github.com/dextel2/...
please, give your thoughts, and it would mean a lot if you run it locally :)26 -
So my company is preparing to do a deployment now... It's Friday 4pm...
And it's just yesterday that the build system was upgraded to a way newer version...
Luckily I'm not responsible of things go sideways 😅2 -
So we develop several apps for Android.
And since the whole company is full of .Net developers we´re using Xamarin.
That piece of software alone is worth more than one rant.
But today someone called and said he updated to the latest version he got from our server.
But now one of the menu points in the settings menu is opening the wrong mask.
I´m like ... what? Who fucked that one up now. Ok...
I look at the code and, I didn´t expect it to be honest, but it looks alright.
The menu point has the correct id. The function "OnOptionsItemSelected" looks for the correct id and opens the correct activity.
Just to be sure I also check the activity.
Everything good.
So I start up an emulator. Deploy the app in debug. Works correctly.
Create a self signed apk and install it on the emulator. Works.
Repeat the same with a tablet and my personal phone. It works.
Then I install the apk from the server and would you look at that.
It opens the wrong mask.
So it seems only if the app is compiled on the release server it shows that strange behaviour.
And for the love of my 1080ti I can´t figure out what causes it...
Thank you Xamarin! -
So we pushed some quick fixes management required to the system before going home to sleep. We warned them that we don’t have much time to check and test them. Because ordinarily such fixes go fine, they insisted.
What do you know, while we slept some smartasses within users drained our system money through the new hole we did not notice.
Manager responsible for this just gone dark, never ever picked up his phone. Just disappeared.
We don’t do such fixes anymore 🤗2 -
Is it just me or is what susspose to be the tech giants, making more and more n00b mistakes lately... Apple's latest update "best release of iOS yet" bricks the phone, Samsung phones are blowing up...
Things are continously prematurely released to try and beat everybody in the market place which just leads to unimpressive and dangerous product releases.3 -
The story of a normal release:
- tool gets tested "intensely" by 3 ppl quite a long time - everything works
- a major 2 days reserved as maintenance window for even more testing
- release starts
- first the admin panel of the server suddenly is not accessible anymore
- after some problems the tool is deployed
- suddenly servers are down and not pingable anymore - off on off on (provider has major problems .. good job)
- ppl start testing
- testers report lots and lots of new bugs - seems like the testing wasn't that intense after all...
- people start coming with lots of new requirements (oh we need to import those excels.. excels don't match our internal stuff.. )
- confusion over confusion
- getting pissed of a lot...
- quit caring and focus on another project
- profit
Fuck my life -
So, today we had our first production release of our web app. Last week we changed a big part of our UI. This week we changed the design, rewrote the complete API documentation, implemented mobile support. While the release the administration center of our cloud was unreachable. Shortly after the release we made a bug fix and deployed it directly to production.
So today was a very normal prod release 😂1 -
(defn rant []
(go
(let [feature-pool (atom [:ui-fixes])]
(loop []
(<! wait-for-release-week)
(->>
shit-load-of-features
(reset! feature-pool)
develop-features
ask-for-feature-status
deploy-in-last-minute
find-a-bug-and-rollback release
(recur))))
(rant)13 -
is it necessary to have cherry picking a part of git branching/release process?
we have 3 branches : develop, release and master.
currently every dev works on feature as follows : they make a branch out of develop, write code, raise pr against develop, get it reviewed and merge back to develop. later the release feature list is generated, and we cherry pick all the release related commits to release branch, and make a prod build out of release branch. finally, the code is moved to master and rags are generated accordingly.
so the major issue with this process is feature blocking. as of now, i have identified 4 scenarios where a feature should not be released :
1. parallel team blocker : say i created a feature x for android that is supposed to go in release 1.2.1 . i got it merged to develop and it will be cherry picked to release on relase day. but on release day it is observed that feature x was not completed by the ios dev and therefore we cannot ship it for android alone.
2. backend blocker : same as above scenario, but instead of ios, this time its the backend which hasn't beem created for the feature x
3. qa blocker : when we create a feature and merge it to develop, we keep on giving builds from develop branch adter every few days. however it could be possible that qa are not able to test it all and on release day, will declare thaf these features cannot be tested and should not be moved to release
4. pm blocker: basically a pm will add all the tickets for sprint in the jira board. but which tickets should be released are decided at the very late days of sprint. so a lot of tasks get merged to develop which are not supposed to go.
so there's the problem. cherry picking is being a major part of release process and i am not liking it. we do squash and merges, so cherry picking is relatively easy, but it still feels a lot riskier.
for 1 and 2 , we sometimes do mute releases : put code in release but comment out all the activation code blocks . but if something is not qa tested or rejected by pm, we can't do a mute release.
what do you folks suggest?9 -
Release Notes:
This change *shouldn’t* break anything. Please keep your eyes open for strangeness.
Every. Release. Ever. -
!Worst, being put on the project a day before release
!Best, finding and fixing all the data model issues before release, so that the next time I have to pull stats about the system, everything actually makes sense, as all foreign keys and indexes would be explicitly defined for once.5 -
So remember when we said 1.1 would be the last release, and then we said that 1.2 would be the absolute last we promise this time release?
Well buckle up buckaroos because 1.3 will be the last release. -
Client: $importantThing is a go live feature now.
Me: Okay, but it would considerably postpone the release date.
Client: Oh well, then maybe after release. However, do $lessImportantThing for go live, no matter how long it takes. -
The icing on this app release cake was piped this morning.
The clients released the app into the wild, without our knowledge, despite some rather large, glaring issues that are present.
As to why they thought it was a good idea, who knows?1 -
Life lesson learned:
Despite good intentions, don't overengineer the front-end, when time is heavily constrained and the release is scheduled and is communicated to media outlets immediately after.
A broken release just makes the client send around multiple emails per minute with tens of people in CC.
Shit happens... at least it was a bargain for them. -
Aaarrgghhh! That piece of crap build system we use is acting again. Nobody touched it, nobody had time to replace it with something reasonable and now it starts not building as far as I can tell random parts of system. I guess it can sense we wanted to release :-/ So no time for any nice project and back to kicking its shit together :-(2
-
Every time we have a release, "Release Engineering" stops building our test environments from master. I've been preaching Continuous Deployment for months and here we are with the most broken system. The build actually builds all test environments AND prod from the same branch because "it's easier" for "Release Engineering". So now I have to wait for the code freeze on release and hope RE doesn't fuck up and deploy an untested branch to prod... AND hope we're given enough time to test and debug the next release since we can't right now...1
-
Hi! I want to switch to linux but i never used it before and i want advice from you guys about the OS (what distro should i use and how to get started).15
-
I come to check in to the office during my vacation to see how the project is going. I find a colleague from a vendor explaining it all to business and pushing over CSS changes to the next release. Current release is MVP1 and is set to release 3 months for now. *facepalm*2
-
They had a meeting without me for a production release that was happening tomorrow. Rescheduled the release on my wife's birthday without asking anyone. This was the response when I let this known "Happy Birthday honey, you get a night without me."1
-
You know what I hate? The periods close to a new release. It's that annoying time that managers start heaving impatiently to developers: "Push out new hotfixes! Push out new hotfixes!". Fuck you, man. Don't stress a developer. Kthx. If you think developing is so easy, come do it yourself, you IT-ignorant buffoon.1
-
Currently in our 4th cycle of manual regression testing for a release and still finding bugs. Automated tests? What are those? That sounds an awful lot like it would take time to implement. Time that could be spent fixing the bugs and getting the release out the door.
When release dates take priority over quality.... -
Test the project pre-release -> everything works well
Release the project -> new bugs comes out, features are not working anymore, some files are corrupted, your PC is ready to explode and a black hole is going to destroy everything1 -
Someone else updated a firmware and noticed that its worse than the older? The worst ia when you try to fix it and it broke another thing.
Too many bugs in a release (yes, a "verified" release)3 -
Month 4 of a new role and a release. Its a monolith which we will be splitting to micro services, but we need to release a version first. Every day there is new errors. 1,000 LINE if statement. How the hell have they been able to release the previous erll version.3
-
The fucking release process. We release weekly which is stressful for both Devs and QA’s. Everything should be committed/promoted in our DVCS by Thursday and should be verified beforehand. The problem is, QA’s doesn’t take development builds, they only want to take whats fucking next in release. In other words WE. FUCKING. RELEASE. UNTESTED. SOFTWARE.
Man, BA’s have it easy on our team.1 -
New version release Saturday morning. We have 3 hours window I plan to do it in 15 minutes and don’t loose weekend.
Wish me luck.6 -
Today I released the next versions two of my company's Android projects. Today was a good day.
Also, releasing on a Friday afternoon FTW! (they are beta releases, so I'm good).1 -
Sad because I was performing an extensive code integration of a release from an external source and then an employee from another building integrated another release before me
Now I need to request a new release with the bug fixes and it will take various days, maybe weeks (and if another release is integrated before, the cycle restarts).
I might be able to integrate by the end of the next year. Who knows. -
The wonderful feeling when project was finally relesed and deployed, you have no chance for any more last minute fixes and you can finally merge into master and break everything :-)
-
Today is release day!
Got a whole set of new features to deploy on production!
Also, internet at the office has been dead since 6am.
I'll take a coffee break. -
A client just replied to a two month old email telling him that the next release will contain a fix for a bug asking whether this release will fix that bug... Mkay then...
-
So here it is. Apple release, second round.
This time, uploads to AppStoreConnect took 3 hours and 40 minutes. Submission of the app was at 0.04, just after the planned launch day. Android submission tomorrow.
Tomorrow, and Friday are public holidays.
I'll have to work those, at best being able to not work on the weekend. The client has already told me he's calling me tomorrow morning to talk about things.
I don't want praise, but I'd like him to respect that while I may just be a lowly developer, I would like to have a life.
When are the happy times coming? -
My first production support release is next week and its from midnight till 5am and be at work at 8:00am. If something goes wrong with any of the other developers from our team goes wrong I have to figure it out. And this image is exactly how I picture it goes, if any tickets fail. (🤘🏽 bring it on! )
-
Hey guys, i made a program years back and just refactored the thing and gave it a nice GUI. I made it mostly so I can use it in my daily life which I do but now I might release it as open source and give it to some friends. But I’m facing A problem i never faced before...giving it a name. Need some help 😂
Basically, i have tons of series, so i created it to maintain a nice naming convention for the videos but obviously can work for any file list.
- it renames them in a couple of different ways (replacing string occurrences in the file names, appending - prepending strings, completely renaming it alphanumerically. Anyway I use those features most (OCD i know)
- it also grabs subtitles for movies and series (parses its way through subscene and yifisubtitles until it gets to download the zip file and extracts it for me) .
- It also plays random episodes for me when im confused what to rewatch ( just opens a random file in a directory u point it to)
So any name suggestions ?1 -
Release build fails. Bad test was commented out on development branch but merged into release branch.
-
4 hours to a major release, decided to remove a web service from the app, instead do whatever that service was supposed to do in a DB query, as just realized that the foresaid service will be called only once to fix some data discrepancy !!!
-
currently setting up a repo for a git release branching demo because despite the fact we have a model in place, it was completely ignored when it came to release time with changes being pushed straight to the main develop branch *sighs*
-
When you click on a link in google and get taken to "wwwqa.companyname.com". I think they're really really confident in their QA environments ;)
-
Yesterday I installed linageos without gapps and wondered if there is an official release of the devrant apk without Google store. I acquired my copy from apkpure
-
I got a release date for TechWiz.
My plan is to get it recorded and edited all next week, and have it published on the 20th of this month.
I will release episode third Friday of each month. So, be ready! -
Doing production release on Wednesday is kind of pointless. Someone is going to override the world a day after due to Last Thrusdayism - https://letmegooglethat.com//...1
-
Release team was recently disbanded, they handed off release management to the Dev scrum masters. The other day we had a weekly release for a product that uses a network service that is shared with other products. The devs didn’t know how to set up the build correctly. They had a purge setting on that removed the network service for products that weren’t being touched in the release. The end result was that the other products were inaccessible for an hour and a half! They eventually found their mistake, but we were lucky that it was outside of core business hours.
These devs need to learn how to work the build tools! Or maybe we should rethink getting rid of the release team. -
Two architectures to support, on one everything went smoothly, other one I spend since Monday till yesterday 2am to make it work. Now time for half-day meeting and if it compiles in the meantime, I can release today before leaving work. Sounds like a solid plan, Friday afternoon release. What could go wrong? And I hoped it will work nicelly on Monday, latest Tuesday.
-
#Suphle Rant 5: Xavi
When I first detailed what it was I was working on to my brother and its expected impact on the industry, I must have done so with an enormous amount of enthusiasm that he impatiently began to request when the dream will be realised. He didn't give a shit about specifics of where I was on the timeline. He kept repeating the same question. Exasperated with the futility of my explanations, I replied that I'd be done by November as this was far beyond my estimated completion date
Every milestone (e.g. my birthday) I've expected it to be ready at has come and gone, including the unrealistic November. My present state of mind is far from the optimistic pioneer I was then. I'm just going with the flow and won't be surprised if it's not officially released by the end of the year
This gonna be me in 2072, convincing anyone who cares to listen that I'm fleshing out the docs and that the reason the release date keeps getting pushed back is because nobody has shown interest in either using or contributing to it
-
I just commented a test so the PR passes and the feature reaches next release; I can't fix it (Damn react testing library tests)
but after that, the linter failed for the same PR, so I just fixed it and did a git push -f
I guess once you cross the line you cannot come back
feel my pain1 -
Some of my first thoughts on the new 16.3 release of React...
New Context API:
- I’m glad they made the context API less scary, but as a redux user I will still be staying away from using context as a best practise.
Strict Mode:
- I like this a lot. React allows for great freedom in how you do things, but also offers the freedom to write some shit code that in the end does the job. A way to enforce best practises in JSX is good in my eyes.
New lifecycle methods:
- meh. Life moves on
https://medium.com/@baphemot/... -
collAnon.app v2.0.21, my long running PWA/WebApp about private discussions and confrontations, is finally out with many theme and UI improvements, better forms and a lot of bug fixing ¯\_(ツ)_/¯
I'm really happy of this release of mine that I wanted to share it here.
It's also mostly self hosted with a third party, GDPR compliant, CDN (I did learn many things integrating Blazor WASM with a CDN)
8 -
Release was supposed to start at 10 am, its now 11am but our release document is being debated heavily. The outage is scheduled to last until 2 and we thought we'd be tight for time when starting at 10 FML to right now..
-
Finally after 3 fucking months, 15-20 fucking meetings, I got sign off for a feature release. The development took 3 weeks and was completed in March end.
I know being a financial institution and feature was regarding system handling funds, business guys need to worry a bit as any mistake in code can mess up the funds disbursal. But fuckers took 3 months to give sign off.
However, it's finally released and I can relax for now. #peace -
Release is out now!!!
Just seven month after first beta! I'm so fond of those customer change requests. Now I'm back in the predictable world... -
I have a git feature branch with my commits but also have merged the changes from the main branch to resolve merge conflicts before PR.
But now need to create a special release with just my changes.
So I think have to cherry pick all my commits on my branch some the last Release. How can I do that?
Develop (others) + Feature => Develop
Want to create new branch
Last Release + Feature (but only my commits since last Release)3 -
I was asked to make release branches which will change my gitflow. Am I understanding it correctly now? Fix me if I'm wrong
So I do my fixes in develop, once Im done I squash merge them into 1 commit. Then I make a release branch from develop, if everything is fine I release it. After release I merge back release branch to master and thats it?3 -
What's your routine for versioning pre-releases?
While working on a big change, like "milestone 2.0", how do you, while working on it, version it before the main release? To keep it being 2.0.0 on release and not for example 2.130.0 (since it was "2.130.0-pre" just before release)?
Or is it my fantasy that when released to public it "should" always be *.0.0?1 -
Honest question - when a company offers has an open source software product (in the name of transparency and whatnot), but offers it as a binary release as well for non-developers, what guarantee do you have that the release was *really* compiled from the source they provide?
Top Tags
Weekly Rant
View