Re: [Qutecsound-devel] [Qutecsound-users] [CsoundQt/CsoundQt] Release v0.10.0 - 0.10
Brought to you by:
mantaraya36
Menu
▾
▴
Re: [Qutecsound-devel] [Qutecsound-users] [CsoundQt/CsoundQt] Release v0.10.0 - 0.10
|
From: Tarmo J. <trm...@gm...> - 2020-07-02 21:17:17
|
Hi, OK, my proposal: I suggest more conservative way still - to delete the tag v0.10 and change it to v0.9.8.1, v0.9.8-1 or something, upload the binaries there, so people get the latest fixes. This is the most important. Then let's wait for more feedback and issue reports (we should benefit from feedback of many people - there were a lot of changes in the code, it is impossible to test everything by just couple of us). and release 1.0.0 after some time. Again - I believe it is not the number that matters, but this seems most logical to me. tarmo Kontakt joachim heintz (<jh...@jo...>) kirjutas kuupäeval N, 2. juuli 2020 kell 22:36: > yes it IS a big step, and i would consider this as birthday present to me > =) > (no my birthday is not today) > > thanks - > j > > > On 02/07/2020 20:57, Eduardo Moguillansky wrote: > > They say that while they talk to you through their macos 10.14 driven > > laptop... Anyway, these differences are meaningless to me and since > > there was a great effort to bring csoundqt forward we might make an > > exception and make the jump to 1.0.0 and start the proposed scheme from > > there, meaning: look, this is now usable, mature, etc. Even if it's > not... > > > > so, I go either way, but I would like to decide this since I need the > > new version to be downloadable now. > > > > --- > > eduardo > > > > On 02.07.20 20:48, joachim heintz wrote: > >> perhaps i have to represent the unreasonable part here: > >> i don't agree. > >> > >> i had a talk today with some students. to all this 0.10 number > >> appeared strange, and looked like many steps back (we did not count > >> 0.09. before as csound does). > >> > >> joachim > >> > >> > >> On 02/07/2020 20:38, Tarmo Johannes wrote: > >>> I agree. > >>> Tarmo > >>> > >>> N, 2. juuli 2020 21:30 Eduardo Moguillansky > >>> <edu...@gm... > >>> <mailto:edu...@gm...>> kirjutas: > >>> > >>> To go forward I would propose the following scheme: > >>> > >>> Major release, when major things happen: switching from qt5 to qt6, > >>> switching from csound6 to csound7, switching from a certain file > >>> format to another, etc. Most importantly, there is no backwards > >>> compatibility between major versions. > >>> > >>> Minor release for things that add core functionality, new widgets, > >>> etc. A .csd which worked in a previous version might need to be > >>> adapted, but there is certain respect for backward compatibility. > >>> > >>> Patch: these are bug fixes. If you are happy with how the program > >>> runs, you don't need to update. > >>> > >>> I would propose to start that scheme now. This is a minor release, > >>> in the sense that there is backwards comptability. So we use the > >>> next number in minor releases: 10 (these are numbers and not > digits) > >>> > >>> In order to not mess up more with the git history I would just > >>> release the bug fixes we have until now as 0.10.0 and upload the > >>> builds (I got to build the mac version correctly!) and any other > bug > >>> fixes will go as 0.10.1, 0.10.2, etc. Whenever the dark look > >>> redesign is ready that might be 0.11.0. > >>> > >>> eduardo > >>> > >>> > >>> On 02.07.20 20:02, Tarmo Johannes wrote: > >>>> Hi! > >>>> > >>>> There is also software that never goes above 0.x.y. Still, I > >>>> agree, would be good to change it. > >>>> > >>>> The current 0.9.8 introduced a lot of changes, I think it is good > >>>> to keep that in use for couple of months, do only bug fixes or > >>>> other minor changes to the code (and use other branches and > >>>> alternative builds for bigger things, if necessary) and then > >>>> release it as 1.0.0 when the current base seems well tested and > >>>> users happy. > >>>> > >>>> tarmo > >>>> > >>>> tarmo > >>>> Yes, it would be logical. > >>>> > >>>> Kontakt joachim heintz (<jh...@jo... > >>>> <mailto:jh...@jo...>>) kirjutas kuupäeval N, 2. juuli > 2020 > >>>> kell 12:08: > >>>> > >>>> hi tarmo - > >>>> > >>>> thanks for explaining. my surprise is simple: for my > >>>> everyday's > >>>> understanding, after 0.9 the 1.0 should follow. i understand > >>>> what you > >>>> and eduardo mean, but the zero in first place after more than > >>>> ten years > >>>> CsoundQt is strange for me. > >>>> > >>>> (Cabbage is now at 2.3.0 and is not older; Blue is at 2.8.0.) > >>>> > >>>> as this release is a major one, perhaps you and eduardo can > >>>> consider to > >>>> make now the step to 1.0.0. more intuitive for me (and i > >>>> assume for > >>>> some others), and more appropriate for the developement > >>>> state of > >>>> csoundqt, in my opinion. > >>>> > >>>> cheers - > >>>> joachim > >>>> > >>>> > >>>> On 01/07/2020 20:08, Tarmo Johannes wrote: > >>>> > Hi, > >>>> > > >>>> > Let's discuss the version policy a bit. > >>>> > I continued what Andrés Cabrera started (that does not seem > >>>> most > >>>> > logical to me nowadays) - > >>>> > the version tags in git history are: > >>>> > > >>>> > 0.7.0 > >>>> > 0.7.0-beta > >>>> > 0.7.1 > >>>> > 0.7.2 > >>>> > 0.7.3 > >>>> > 0.7.4 > >>>> > 0.8.0 > >>>> > 0.8.0-win > >>>> > 0.8.1 > >>>> > 0.8.2 > >>>> > 0.8.3 > >>>> > 0.9.0 > >>>> > 0.9.1 > >>>> > 0.9.2 > >>>> > 0.9.2.1 > >>>> > 0.9.2.2 > >>>> > 0.9.3 > >>>> > 0.9.3-beta > >>>> > 0.9.4 > >>>> > 0.9.4-beta > >>>> > 0.9.4-rc1 > >>>> > 0.9.5 > >>>> > 0.9.5-beta > >>>> > 0.9.6-rc1 > >>>> > 0.9.6-rc2 > >>>> > 0.9.7 > >>>> > 0.9.7-rc1 > >>>> > 0.9.8-beta > >>>> > 0.9.8-rc1 > >>>> > 0.9.8-rc3 > >>>> > v0.9.8 > >>>> > > >>>> > so far the the version has start always with 0 (as usually > >>>> in beta > >>>> > releases), minor version showed bing changes in API (as > >>>> like for > >>>> > support from Csound5 to Csound6 0.8->0.9) patch version > >>>> important new > >>>> > features or bug fixes. The small bug fixes were marked > >>>> sometimes with .1 > >>>> > or .2, sometimes I have uploaded builds with -1 or -2 in the > >>>> end. Not a > >>>> > very good and clear system. > >>>> > > >>>> > If we follow the old logic, the recent small fixes should > >>>> give an extra > >>>> > number to v0.9.8 since there were no significant new > >>>> implementations > >>>> > thus perhaps v0.9.8.1 or v0.9.8-1. v0.10 is OK for me, but > >>>> what is the > >>>> > new logic after that? > >>>> > > >>>> > Of course it would be better to use the major version, minor > >>>> version and > >>>> > patch version as usually, thus let's say we had 1.0.0 > >>>> released and this > >>>> > fix release would be now 1.0.1; when we will have something > >>>> new added, > >>>> > it would make 1.1.0, when we get to Csound7 support > >>>> (perhaps) it would > >>>> > make 2.0.0 etc > >>>> > > >>>> > But where to make the break to 1.0.0? After some patch > >>>> versions of the > >>>> > current until everybody seems happy? > >>>> > > >>>> > Anyway, it is just a number. > >>>> > > >>>> > Eduardo, whatever the number is, I guess I should make new > >>>> Mac, Windows > >>>> > and AppImage builds from develop and add them to 0.10? > >>>> > > >>>> > tarmo > >>>> > > >>>> > Kontakt joachim heintz (<jh...@jo... > >>>> <mailto:jh...@jo...> > >>>> > <mailto:jh...@jo... <mailto:jh...@jo...>>>) > >>>> kirjutas kuupäeval K, 1. juuli 2020 kell > >>>> > 16:14: > >>>> > > >>>> > why not 1.0.0?!? > >>>> > do you want to keep the 0.xx forever? > >>>> > > >>>> > cheers - > >>>> > joachim > >>>> > > >>>> > > >>>> > > >>>> > On 01/07/2020 14:22, Eduardo Moguillansky wrote: > >>>> > > > >>>> > > 0.10 > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> > >>>> > > > >>>> > > Repository: CsoundQt/CsoundQt > >>>> > <https://github.com/CsoundQt/CsoundQt> · > >>>> > > Tag: v0.10.0 > >>>> <https://github.com/CsoundQt/CsoundQt/tree/v0.10.0> · > >>>> > > Commit: e2576c5 > >>>> > > > >>>> > > >>>> < > https://github.com/CsoundQt/CsoundQt/commit/e2576c53d5acb6c678f857d88ee2582442459fd5> > > >>>> > >>>> > > >>>> > > · Released by: gesellkammer > >>>> <https://github.com/gesellkammer> > >>>> > > > >>>> > > > >>>> > > Changes since 0.9.8 > >>>> > > > >>>> > > > >>>> > > Bugs fixed > >>>> > > > >>>> > > * toolbar in mac fixed > >>>> > > * graph widget for tables now initializes correctly > >>>> and follows > >>>> > > negative indexes (to set the table number) as it > >>>> should > >>>> > > * table plot widget was upside down, now fixed > >>>> > > * Graph widget example fixed > >>>> > > > >>>> > > — > >>>> > > > >>>> > > This release has 2 assets: > >>>> > > > >>>> > > * Source code (zip) > >>>> > > * Source code (tar.gz) > >>>> > > > >>>> > > Visit the release page > >>>> > > > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> to > >>>> > download > >>>> > > them. > >>>> > > > >>>> > > — > >>>> > > You are receiving this because you are watching this > >>>> repository. > >>>> > > View it on GitHub > >>>> > > > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> or > >>>> > > unsubscribe > >>>> > > > >>>> > > >>>> < > https://github.com/CsoundQt/CsoundQt/unsubscribe_via_email/AAQYHKWDLXF645EPEIWT623RZMS75ANCNFSM4ANME2IQ> > > >>>> > >>>> > > >>>> > > from all notifications for this repository. > >>>> > > > >>>> > > >>>> > > >>>> > _______________________________________________ > >>>> > Qutecsound-devel mailing list > >>>> > Qut...@li... > >>>> <mailto:Qut...@li...> > >>>> > <mailto:Qut...@li... > >>>> <mailto:Qut...@li...>> > >>>> > > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > >>>> > > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Qutecsound-users mailing list > >>>> Qut...@li... > >>>> <mailto:Qut...@li...> > >>>> https://lists.sourceforge.net/lists/listinfo/qutecsound-users > >>> > |
