-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1 release date #3718
Comments
The beta was closed at the beginning of the month, it is true that by now they should release v1 (as they had planned), but don't excuse yourself with changing the code in a couple of months, remember that this always happens in other projects in terms of software maintenance (you are not the only one). Just wait until they release the version and in the meantime stick with 0.9.4 as we all do. We are looking forward to see what changes this version will bring, but we can only wait. Regards |
we are an enterprise organization - you have no idea what you are speaking on and frankly I didn't ask you about waiting I asked for a release date. we have large teams of people - you have no idea what the EOL/EOS date so your LTS strategy is flawed. its clear by your comment that you've not worked in an enterprise of any dynamic. |
End of Q1 Is what the maintainer said. This is probably more a question about whether the next major release is going to break most things or if it is mostly optional additional features. Maybe @jgthms can give an estimate about that so that you can decide now. |
Hey man, if the v1 is so urgent to your enterprise, then sponsor the project. This is a free/open source project. So your demands don't have a place here. And by the way, if your enterprise isnt capable to work with changelling projects, so your administration isnt right, because all the free/open source projects is changin constantly, you can work with stable releases and do a migration in a few months/years, or you can choose another framework. So, if you arent pay or sponsor the project, then take it easy and be patient. |
you going to commit resources for that? you going to pay for it? you
going to go and get blue dollars in the middle of q1? go do it houdini.
sorry - but that is the fact. we pass for now. it would just be nice for
the product owners to commit to a road map. this is standard industry best
practice. this is our road map - not loosely just throw out an arbitrary
date. just saying we run agile - so this kind of stuff, these kind of
replies are not helpful.
…On Thu, Feb 29, 2024 at 5:20 PM Mario ***@***.***> wrote:
Hey man, if the v1 is so urgent to your enterprise, then sponsor the
project. This is a free/open source project. So your demands don't have a
place here. And by the way, if your enterprise isnt capable to work with
changelling projects, so your administration isnt right, because all the
free/open source projects is changin constantly, you can work with stable
releases and do a migration in a few months/years, or you can choose
another framework.
So, if you arent pay or sponsor the project, then take it easy and be
patient.
—
Reply to this email directly, view it on GitHub
<#3718 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A52OXBBNKVM4SCEDUBBMOCLYV6UTFAVCNFSM6AAAAABD2YL6J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGA3DQNJRGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
how to create a project roadmap
https://www.teamwork.com/project-management-guide/project-roadmap/
open source or not - one person has to be the project manager and GSD.
It's not me though - sorry. I already work enough.
your response - read
https://www.reddit.com/r/programming/comments/17lemv5/open_source_is_struggling_and_its_not_big_tech/
On Thu, Feb 29, 2024 at 5:50 PM Christopher Burd ***@***.***>
wrote:
… you going to commit resources for that? you going to pay for it? you
going to go and get blue dollars in the middle of q1? go do it houdini.
sorry - but that is the fact. we pass for now. it would just be nice for
the product owners to commit to a road map. this is standard industry best
practice. this is our road map - not loosely just throw out an arbitrary
date. just saying we run agile - so this kind of stuff, these kind of
replies are not helpful.
On Thu, Feb 29, 2024 at 5:20 PM Mario ***@***.***> wrote:
> Hey man, if the v1 is so urgent to your enterprise, then sponsor the
> project. This is a free/open source project. So your demands don't have a
> place here. And by the way, if your enterprise isnt capable to work with
> changelling projects, so your administration isnt right, because all the
> free/open source projects is changin constantly, you can work with stable
> releases and do a migration in a few months/years, or you can choose
> another framework.
>
> So, if you arent pay or sponsor the project, then take it easy and be
> patient.
>
> —
> Reply to this email directly, view it on GitHub
> <#3718 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A52OXBBNKVM4SCEDUBBMOCLYV6UTFAVCNFSM6AAAAABD2YL6J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGA3DQNJRGQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
How ungrateful and unpleasant do you want to be? chrisburdusa: Yes. |
I am saddened about the tone of the OP. @chrisburdusa, if you have paying customers that wait for a deadline, why not choosing to rely on dependencies that for themselves deliver on a timeline for a price? There are plenty of commercial CSS frameworks readily available. Bulma however, is a free and open source project that some nice soul works on. It's great for all and noone is obliged to anything. That's how this works. Plus, with the MIT license, you can change as much as you want to your own benefit, no obligation to release. I have done some additions here, feel free to do as well: https://github.com/suterma/bulma-print |
loser
…On Fri, Mar 1, 2024 at 5:28 AM Patrick Bergner ***@***.***> wrote:
How ungrateful and unpleasant do you want to be? chrisburdusa: Yes.
—
Reply to this email directly, view it on GitHub
<#3718 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A52OXBALGU6HZIVDXSHHZJTYWBJ5LAVCNFSM6AAAAABD2YL6J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSHEZDSOBRGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm actually dying 🤣. How does someone who's familiar with github and programming in general interacted with open source this little? |
I interact often - I asked a question about a commit date and in typical incompetence standard, they couldn't answer it. My boss warned about trying open source - and he was right. Bulma will never step a foot inside JP Morgan Chase & Companies. Not ever breath the fucking air. |
Here is the thing regarding bulbs and similar products. You have to get a specialist or someone who knows the project in & out. It's not that it's not maintainable it supporyable it's just that people choose to be knowledgeable about it. Once someone knows then they become a specialist with the product which they can help support as independent contractors in those various organizations. Throughout that time they also provide contributions back to the project based on the contract they undertook or newfound experience from a project they participated in. People feel free upset sometimes regarding the flow of or organisation of open source projects but let's be honest, it's fueled by a different thought paradigm than other things. |
is that why those companies always produce trash products? I am always astounded at how AWFUL enterprise web applications are, like truly bad, so bad you really wonder at how its possible huge budgets can produce such awful UI and UX! Perhaps because they hire entitled pricks who think they know everything 😆 🤷♂️ well thanks for solving a mystery for me! |
Today? See -> https://github.com/jgthms/bulma/releases/tag/1.0.0 |
@chrisburdusa v1 just got released, so I guess this issue could be closed 😉 |
Yeah, I guess it could be closed and locked... Just to add something positive, I'll say that I've started using bulma 5 years ago, and loved it since. I love the new features of the v1, and I feel like I can safely say that most of us love what you did @jgthms and we are very grateful for your amazing work 🙏 |
the tickets closed move on - I was pissed off because 4 individuals prior
to posting anything jumped on my Linked in and I was called a f#cker, an
assh#le, a piece of sh#t, an incompetent, not a good software engineer, all
kinds of ridiculous shit. I am a real software engineer, I had an
internal project I wanted to use your css for. I pushed hard on it - when
it didn't happen, I looked bad. so I asked you to create a road map and
put some time into it, because I'm certain his other customers actually
want the same shit.
We might have even funded it if we got past POC, but we didn't.
So I apologize Bulma guy to you only. These people though; instead of
maybe learning about how larger companies work. They couldn't do that - it
was infantile, including all the responses post. I've ignored them all -
because I really don't have time for it in any sense of the word. I had a
right to be angry, that was not called for at all - so my response was
equal in kind.
…On Sat, Mar 16, 2024 at 1:00 PM William ***@***.***> wrote:
I'm actually dying 🤣. How does someone who's familiar with github and
programming in general interacted with open source this little?
I interact often - I asked a question about a commit date and in typical
incompetence standard, they couldn't answer it. My boss warned about trying
open source - and he was right.
Bulma will never step a foot inside JP Morgan Chase & Companies. Not ever
breath the fucking air.
is that why those companies always produce trash products? I am always
astounded at how AWFUL enterprise web applications are, like truly bad, so
bad you really wonder at how its possible huge budgets can produce such
awful UI and UX! Perhaps because they hire entitled pricks who think they
know everything 😆 🤷♂️ well thanks for solving a mystery for me!
—
Reply to this email directly, view it on GitHub
<#3718 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGP67XGNWSFA2XBVPAUFAHTYYR3C3AVCNFSM6AAAAABD2YL6J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGA2DMMJYGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
at this point - there's not been a release date, it would be helpful if your organization put a commit date on a road map and stuck to it. I can't move forward with a project using Bulma if I'm going to have to rewrite it in a month or two. Most clients don't want to pay for double work - and in my LTS I can't just be putting out products that will be retired in a month or two.
I find it almost negligence at this point to not be able to say when. this is a real issue - and it needs addressed, you closed beta for months now and should've had RC1 ready to go.
The text was updated successfully, but these errors were encountered: