1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Versioning

Discussion in 'Building With Reaktor' started by Rolix, Feb 16, 2005.

Thread Status:
Not open for further replies.
  1. Rolix

    Rolix NI Product Owner

    Messages:
    116
    This has been asked before, but the solution presented then did not work, so please pardon me repeating the topic:
    1. How can I prevent version numbers from incrementing in "integer steps"? Earning my living as a programmer I'm used to a slightly different approach than this server enforces.
    2. How do I achieve that updates appear with their current upload date and not the one of version 1.0? Or was this only the case a week ago when the server did not work properly?
    3. will I be flamed and banned if I try myself using test uploads?

    Thanks in advance!
     
  2. Rameau

    Rameau NI Product Owner

    Messages:
    455
    1. Can't change that. You can incorporate some sort of version or revision number into the title of your ensemble.
    2. Unfortunately, the way it is set up now, version updates always appear with the date of the v 1 upload.
     
  3. Rolix

    Rolix NI Product Owner

    Messages:
    116
    Rameau, bad news but thanks for the reply!
     
  4. kid_sputnik

    kid_sputnik NI Product Owner

    Messages:
    3,552
    yeah i do agree with rolix, its kinda annoying that my latest UL upload is at version 3.1 when all i fixed was minor bugs (i forgot to wire something, and i forget to internally route something else). hardly a 3.1 release! (NI are you listening?)
     
  5. Rolix

    Rolix NI Product Owner

    Messages:
    116
    I wrote a complaint to the NI Website forum. Maybe you can join in, the more people complain the more NI must see that it is an important issue.
     
  6. Rameau

    Rameau NI Product Owner

    Messages:
    455
    I wouldn't want to write in with a complaint. I'd want to write in with a suggestion.

    I think something very cool and exciting is happening: Reaktor has been around long enough with the 4.1 version, which is a big step forward, that a community of developers has congealed and put together a growing knowledge base, together with a growing library. There's a positive feedback cycle: as more knowledge is gathered, it becomes easier for new people to join in and add; I hope the buzz about a manual rewrite is partly NI realizing that Reaktor is taking off in a new way, maybe and becoming more robust. In my view, half of what I pay for Reaktor is access to other developers through the library and this forum; and NI is getting some kind of pay or value by having a developer community.

    I think Rolix and db_Sputnik are right that the library should be changed: if NI wants serious developers in the library, then seemingly small things like control of version numbers, and version updates causing the upload date to be updated are important. They help developers manage their files and versioning; they give developer payback in having their work appear in the spotlight for a bit.

    But I think of this as a helpful suggestion for improving the product; maybe when they were putting up the library they weren't thinking of it from the developers point of view.

    I think we should make our views and suggestions known in a powerful and helpful way. I think in return, NI should acknowledge suggestions.
     
  7. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    so, what do we want.

    please clarify.

    ...we want to be able to edit the version number that is seen with
    the upload (this used to be the way it worked). yes?

    ...do we want updated ensembles to reappear in the "new"
    section. this would prevent loads of new uploads. as an example
    i uploaded a new version of FourTeche with many enhancements as a new .ens because if i loaded it as an update in the old version, most people would not see it. thus i have 2 versions where i would prefer one.

    ....other requests.


    ok, please be clear. i will collate the requests and email them to
    the relevant person.

    sowari
     
  8. Rolix

    Rolix NI Product Owner

    Messages:
    116
    Yes! If not feasable, give us at least a choice between a major update (increments by 1.0) and a minor update (increments by 0.1).

    Yes! That's where they should go, they're new, aren't they?

    Thanks alot!
     
  9. John Nowak

    John Nowak Account Suspended

    Messages:
    3,493
    The more "features" they add to that thing, the more I hate it.
     
  10. herw

    herw NI Product Owner

    Messages:
    6,421
    i vote for describing categories like
    'RECTANGLE.black.depressive.todaynot' ;-)

    herw.blue.moin-moin
     
  11. Rolix

    Rolix NI Product Owner

    Messages:
    116
    Reminds me of those to old guys in the muppet show...
     
  12. herw

    herw NI Product Owner

    Messages:
    6,421
    insider!
     
  13. Rameau

    Rameau NI Product Owner

    Messages:
    455
    I think this might do:

    When you click the update button, you get a choice of either major or minor update with NI's version number as major.minor.

    Whenever you update, the upload date changes. (Or: this happens on major updates.)

    Or:
    Editable version numbers.
     
  14. kid_sputnik

    kid_sputnik NI Product Owner

    Messages:
    3,552
    Rameu, i like your first idea the best... currently you can pick update or edit, i think they should make it update (+.1) or upgrade (+1.0), and you can choose which you prefer. if they must keep description updates as a +.1 update i guess i can live with that.
     
  15. Rolix

    Rolix NI Product Owner

    Messages:
    116
    Sowari, any news on that topic? Is NI considering our suggestions?
     
  16. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    i am emailing next monday 28th. i just wanted to make sure all the opinions were in. i don't want to bother the guy today just before a weekend ;-)

    sowari
     
  17. Rolix

    Rolix NI Product Owner

    Messages:
    116
    Ok, thanks! Don't think I'll have an update this weekend anyway.
     
Thread Status:
Not open for further replies.