Release 6.1.5
zenopopovici opened this issue · comments
Guys please push a new release ... this should take minutes. Or revert to 6.1.2.
The current "stable" release breaks all projects that auto-update to it. This generates a lot of pain for everyone using jeet.
This does not just take minutes.
It would work way faster if people would cooperate with us to help that issues are fixed, because we do not want to push another broken release.
You could go ahead and try the current master branch of the repository with your workflow and look if everything is working fine again. I just want to get sure that the old behaviour is restored, but we have the new changes in so we can progress again and add more features/fixes onward.
It would take minutes if you were using a develop branch. And only merge stuff into master once they are properly tested. (Like using GitFlow approach: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)
I'm pretty sure we can switch to another branching model with absolutely no issues. (PR's would just need to be re-done (we only have 5).
It doesn't make sense to keep a broken release for 3 months and wait until everything is fixed to make a new release (things are never 100% done). You should be able to release hotfixes and patches as soon as they are available.
I'm grateful for your hard work guys, but we should find a solution to this issue. It only damages Jeet's reputation and creates a lot of headaches where it shouldn't.
The problem is, which kind of started this all, was over a year worth of unreleased changes that basically changed the entire API, and they, slipped into one fix-release, which then followed up another one (6.1.4), which also isn't really working (but better than 6.1.3, which is abysmal).
The current master reflects fixes that should work, and I've gotten some feedback on it, which is great, but the provided feedback is simply not enough for me to just push out another release.
And of course, the branching model etc. pp. can be switched, and I'm pretty sure we will, but the first step to that is fixing the current master and bringing out a working release. After that, for Jeet 7 and following, I'll even try to look into properly testing the outputs, so we can get sure that it's working fine at any time possible.
It's not really waiting to be fixed, I'm waiting for it to be tested in somewhat stable workflows, mostly in Stylus, as the Stylus users have most issues with it right now (and I have virtually no experience with it, I'm more on the SCSS-side of things). I can test single functions with made up files really quickly, but that does not guarantee that it will work in a huge project, where ever that might be.
Understood. Will be testing the master in the coming month to see if there are issues.
@pixeldesu What is more simple to downgrade master branch to 6.1.2 or whatever is working now and move HEAD from it to DEVELOP branch?
@zenopopovici @alex-shamshurin
I opened #504 as a discussion for a revert and bringing back features from 6.1.2, leave a reaction or comment for feedback!
Will be closing this issue in the meantime.