| *** tpb has joined #litex | 00:00 | |
| *** HoloIRCUser has joined #litex | 00:15 | |
| mithro | FFY00: The best way to convince people to write tests is to make not having tests affect them :-) | 00:20 |
|---|---|---|
| FFY00 | the things is that most users won't write tests for you | 00:21 |
| FFY00 | *thing | 00:21 |
| FFY00 | if the tests are missing and you release manually you will still have the same issue | 00:22 |
| mithro | FFY00: That might be true for things like desktop window managers and stuff -- but for developer tools that is a lot more likely | 00:22 |
| FFY00 | well, it would still affect them | 00:22 |
| mithro | FFY00: And if releasing manually isn't giving you an advantage, then why do it? | 00:22 |
| FFY00 | at least in my projects I usually merge things gradually | 00:23 |
| FFY00 | and it doesn't make sense to make a release with an incomplete feature | 00:23 |
| FFY00 | don't know if that happens in litex | 00:23 |
| FFY00 | the point here is that tests can pass but you still have bugs | 00:24 |
| FFY00 | if you let the patches sit in master for a few days they will be tested by actual users | 00:25 |
| FFY00 | I don't see how that is a bad thing | 00:25 |
| mithro | FFY00: We only have a small number of users at the moment, the best way to get users to test things in a couple of days is to get them all using head -- splitting the community into people on head and people on a release means a bug is going to take much longer to be found | 00:26 |
| FFY00 | right, then use a slower release model | 00:27 |
| FFY00 | the users that want the new features will use head | 00:28 |
| FFY00 | the users that need reliability will use the release | 00:28 |
| FFY00 | you can also do release candidates | 00:30 |
| FFY00 | that's a good way to get users to test | 00:30 |
| FFY00 | they update to the release candidate to start adapting to the new changes and report bugs if there are any | 00:31 |
| *** gregdavill has quit IRC | 01:51 | |
| *** gregdavill has joined #litex | 01:51 | |
| *** Degi has quit IRC | 02:01 | |
| *** Degi has joined #litex | 02:03 | |
| *** futarisIRCcloud has quit IRC | 02:32 | |
| zyp | does litex even do releases? | 02:40 |
| *** tcal has quit IRC | 02:40 | |
| zyp | for my embedded projects I generally keep all dependencies as git submodules from the project repo, at which point it doesn't really matter whether a revision is tagged with a release number or not, I'll grab whatever works and have the features/fixes I need | 02:52 |
| zyp | automated tests are good to determine in advance what might work, version tagging doesn't really add anything for me on top of that | 02:53 |
| zyp | speaking of, does anybody use litex as a git submodule? I get the impression that it's expected to be installed in a virtualenv or something, which is not the way I would like to do it | 02:57 |
| zyp | there doesn't seem to be any problem using it as a submodule though, just pointing PYTHONPATH at it, so that's the approach I'm leaning towards, but it'd be useful to hear if anybody else did something similar | 02:59 |
| *** HoloIRCUser1 has joined #litex | 05:45 | |
| *** HoloIRCUser has quit IRC | 05:49 | |
| *** HoloIRCUser1 has quit IRC | 05:49 | |
| *** CarlFK has quit IRC | 06:24 | |
| *** CarlFK has joined #litex | 06:32 | |
| *** rohitksingh has quit IRC | 07:31 | |
| *** rohitksingh has joined #litex | 07:59 | |
| *** rohitksingh has quit IRC | 08:25 | |
| *** rohitksingh has joined #litex | 08:35 | |
| *** rohitksingh has quit IRC | 09:07 | |
| *** rohitksingh has joined #litex | 09:25 | |
| *** rohitksingh has quit IRC | 09:48 | |
| *** HoloIRCUser has joined #litex | 10:09 | |
| *** gregdavill has quit IRC | 11:47 | |
| *** _franck_ has quit IRC | 13:35 | |
| *** spacekookie has quit IRC | 15:38 | |
| *** spacekookie has joined #litex | 15:38 | |
| *** _franck_ has joined #litex | 15:44 | |
| *** HoloIRCUser1 has joined #litex | 18:26 | |
| *** HoloIRCUser has quit IRC | 18:30 | |
| FFY00 | zyp, not yet, that is the reason of the discussion | 18:39 |
| FFY00 | I was asking for releases | 18:39 |
| FFY00 | zyp, if that works for you, great | 18:40 |
| *** lolsborn has joined #litex | 18:40 | |
| FFY00 | but IMO litex tag commits that should be stable | 18:40 |
| *** lolsborn has quit IRC | 18:40 | |
| FFY00 | that way instead of pinning to a commit, you pin to a release | 18:41 |
| FFY00 | if need newer features you can still pin to a newer commit | 18:41 |
| FFY00 | *if you need | 18:41 |
| *** CarlFK has quit IRC | 19:36 | |
| *** rohitksingh has joined #litex | 20:44 | |
| *** tcal has joined #litex | 20:57 | |
| *** HoloIRCUser has joined #litex | 22:36 | |
| *** HoloIRCUser1 has quit IRC | 22:36 | |
| *** gregdavill has joined #litex | 22:53 | |
| *** y2kbugger has joined #litex | 23:26 | |
| *** y2kbugger_ has joined #litex | 23:34 | |
| *** y2kbugger_ has quit IRC | 23:35 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!