5 ms·

Why is it a big deal? It's been sitting for three years because it was just working and given it's minimal nature, there were not many things that should be ch

by gedrap 10y ago

Why is it a big deal? It's been sitting for three years because it was just working and given it's minimal nature, there were not many things that should be changed. So not much point to make a release.

rattray 10y ago
For one thing, it means contributors' work sat there for up to three years – not something that would make me want to contribute. For another, any bugfixes/improvements that had been requested by the community were inaccessible on a release branch, even after they were committed – this sounds extremely frustrating. Most libraries out there are "just working" – doesn't mean they can't ship improvements, and most do – typically no more irregularly than every 6mo.
- gkya 10y ago
  Sometimes sth. is done and no immediate improvements are needed. Furthermore, the repo is out there.
  - wpietri 10y ago
    >Sometimes sth. is done and no immediate improvements are needed. That's a very weird thing to say in response to somebody saying, "improvements were needed and made but not released". > Furthermore, the repo is out there. Now that's just ridiculous. If somebody wants to not have releases, that's fine. E.g., rbenv plugins just seem to be "pull latest from git". But if somebody is going to have releases, then it's absurd to say: "Hey, if you want this to actually work, don't use the release that all the docs tell you to use; instead build the thing we have explicitly not given to you." Having releases: good. Not ever having releases: good. Having them but not using them: worst of both worlds.
    - brbsix 10y ago
      It's actually pretty easy to install directly from the repo: pip install git+https://github.com/pallets/flask.git However as you mentioned, the documentation really needs to be updated to reflect this. It's frustrating to come across this sort of thing. I've even gone so far as forking packages and releasing latest on PyPi myself (so I can easily pull in the dependency from other packages).
    - gkya 10y ago
      A release is a logical point in a software projects history. Sometimes you have a bunch of stuff on the head waiting a release, but that point is not reached yet. The maturity of the features are not well tested, the API is not fixed, etc. Now IDK this specific case of Flask, but there is no one single release cadence that fits all, nor do the releases need be periodic.
      - wpietri 10y ago
        Yes, I think the problem here is that you're opining without understanding the specific case, a case that the rest of us are talking about. The general discussion of release philosophy could be interesting. If you would like to talk about that, you should start a new topic, or at the very least make it clear you're changing the topic. When you reply to somebody's specific statements with sweeping generalities, as you did here, it looks like contradiction.
gkya 10y ago
Out there is a certain "increasing version number fetishism".
- scrollaway 10y ago
  Clearly the only reason people care about this is because of the bigger version number. All the new features/fixes, contributions finally being released, the increase in development activity, it's all bullshit, people only care about the digits. Sigh. You're projecting.

by gedrap 10y ago

rattray 10y ago

For one thing, it means contributors' work sat there for up to three years – not something that would make me want to contribute. For another, any bugfixes/improvements that had been requested by the community were inaccessible on a release branch, even after they were committed – this sounds extremely frustrating. Most libraries out there are "just working" – doesn't mean they can't ship improvements, and most do – typically no more irregularly than every 6mo.

gkya 10y ago
Sometimes sth. is done and no immediate improvements are needed. Furthermore, the repo is out there.
- wpietri 10y ago
  >Sometimes sth. is done and no immediate improvements are needed. That's a very weird thing to say in response to somebody saying, "improvements were needed and made but not released". > Furthermore, the repo is out there. Now that's just ridiculous. If somebody wants to not have releases, that's fine. E.g., rbenv plugins just seem to be "pull latest from git". But if somebody is going to have releases, then it's absurd to say: "Hey, if you want this to actually work, don't use the release that all the docs tell you to use; instead build the thing we have explicitly not given to you." Having releases: good. Not ever having releases: good. Having them but not using them: worst of both worlds.
  - brbsix 10y ago
    It's actually pretty easy to install directly from the repo: pip install git+https://github.com/pallets/flask.git However as you mentioned, the documentation really needs to be updated to reflect this. It's frustrating to come across this sort of thing. I've even gone so far as forking packages and releasing latest on PyPi myself (so I can easily pull in the dependency from other packages).
  - gkya 10y ago
    A release is a logical point in a software projects history. Sometimes you have a bunch of stuff on the head waiting a release, but that point is not reached yet. The maturity of the features are not well tested, the API is not fixed, etc. Now IDK this specific case of Flask, but there is no one single release cadence that fits all, nor do the releases need be periodic.
    - wpietri 10y ago
      Yes, I think the problem here is that you're opining without understanding the specific case, a case that the rest of us are talking about. The general discussion of release philosophy could be interesting. If you would like to talk about that, you should start a new topic, or at the very least make it clear you're changing the topic. When you reply to somebody's specific statements with sweeping generalities, as you did here, it looks like contradiction.

gkya 10y ago

Out there is a certain "increasing version number fetishism".

scrollaway 10y ago
Clearly the only reason people care about this is because of the bigger version number. All the new features/fixes, contributions finally being released, the increase in development activity, it's all bullshit, people only care about the digits. Sigh. You're projecting.