Time |
Nick |
Message |
00:04 |
|
hax404 joined #minetest-dev |
00:09 |
|
iqualfragile joined #minetest-dev |
00:29 |
pitriss |
I want to ask, is planned to allow more than circa 4k nodes? |
00:30 |
|
celeron55 joined #minetest-dev |
00:34 |
VanessaE |
yes |
00:34 |
VanessaE |
if the appropriate people will just fucking commit to it already :) |
00:35 |
VanessaE |
edit mapnode.h line 46 |
00:35 |
VanessaE |
I set mine to 0x7fff but I personally think a value of 0xc000 or so is appropriate. |
00:55 |
pitriss |
VanessaE: oh thanks:) |
00:56 |
pitriss |
VanessaE: btw it is server only setting, right? So it will be possible to connect with standard client too.. |
00:57 |
VanessaE |
tyes |
00:57 |
VanessaE |
yes |
00:57 |
VanessaE |
all modern clients can already handle it |
00:57 |
VanessaE |
anything pre-July 22 will not work though if you define more than 4k nodes. |
00:58 |
VanessaE |
(that includes 0.4.7-stable) |
01:00 |
|
zat1 joined #minetest-dev |
01:01 |
pitriss |
ok.. i don't really care about stable clients. so it is ok for me:) |
01:01 |
VanessaE |
ok :) |
01:26 |
|
NakedFury joined #minetest-dev |
04:12 |
|
Miner_48er joined #minetest-dev |
05:27 |
|
werwerwer_ joined #minetest-dev |
05:44 |
|
mrtux joined #minetest-dev |
05:47 |
|
werwerwer joined #minetest-dev |
05:54 |
|
nore joined #minetest-dev |
06:22 |
celeron55 |
they replied and seem to be eager to co-operate |
06:22 |
VanessaE |
who, the guy who did the android port? |
06:22 |
VanessaE |
sweet. |
06:25 |
celeron55 |
this is my reply-to-be http://pastebin.com/mWfT4zRq |
06:27 |
VanessaE |
seems okay |
06:28 |
celeron55 |
sent |
06:50 |
VanessaE |
bbl |
06:56 |
|
Gethiox joined #minetest-dev |
07:46 |
|
Calinou joined #minetest-dev |
07:51 |
|
Ritchie joined #minetest-dev |
08:01 |
|
darkrose joined #minetest-dev |
08:04 |
|
e1z0 joined #minetest-dev |
08:05 |
|
RealBadAngel joined #minetest-dev |
08:45 |
|
AllegedlyDead joined #minetest-dev |
09:28 |
|
LuxAtheris joined #minetest-dev |
09:36 |
|
proller joined #minetest-dev |
09:48 |
|
smoke_fumus joined #minetest-dev |
10:44 |
|
Ritchie joined #minetest-dev |
10:48 |
|
lanxu joined #minetest-dev |
11:01 |
|
iqualfragile joined #minetest-dev |
11:05 |
|
jojoa1997 joined #minetest-dev |
11:42 |
|
iqualfragile joined #minetest-dev |
11:57 |
|
Ritchie joined #minetest-dev |
12:20 |
|
hmmmm joined #minetest-dev |
13:18 |
|
iqualfragile joined #minetest-dev |
13:21 |
|
e1z0 joined #minetest-dev |
13:23 |
|
ImQ009 joined #minetest-dev |
13:27 |
|
NakedFury joined #minetest-dev |
13:39 |
|
Taoki joined #minetest-dev |
13:40 |
|
zat joined #minetest-dev |
13:47 |
|
Neological joined #minetest-dev |
14:04 |
|
AllegedlyDead joined #minetest-dev |
14:43 |
|
salamanderrake joined #minetest-dev |
15:58 |
|
Jordach joined #minetest-dev |
16:27 |
|
darkrose joined #minetest-dev |
16:28 |
|
iqualfragile joined #minetest-dev |
16:34 |
|
PilzAdam joined #minetest-dev |
17:00 |
|
Gethiox2 joined #minetest-dev |
17:08 |
|
iqualfragile joined #minetest-dev |
17:14 |
|
rubenwardy joined #minetest-dev |
17:28 |
|
ImQ009 joined #minetest-dev |
17:46 |
|
Calinou joined #minetest-dev |
17:48 |
|
iqualfragile joined #minetest-dev |
17:55 |
|
AllegedlyDead joined #minetest-dev |
18:24 |
|
ecube joined #minetest-dev |
18:42 |
|
sapier joined #minetest-dev |
18:46 |
|
proller joined #minetest-dev |
18:46 |
|
troller joined #minetest-dev |
18:47 |
sapier |
wow world isn't as bad as I usually assume it is :-) |
18:47 |
kaeza |
all you need is love ♥ |
18:56 |
|
Zeitgeist_ joined #minetest-dev |
18:56 |
celeron55 |
they haven't done anything yet |
18:56 |
celeron55 |
it's just kind words so far |
18:57 |
celeron55 |
anyone can say kind words |
18:58 |
sapier |
of course but I didn't even expect an answer so world is yet better than my expecataions :-) |
18:59 |
sapier |
https://github.com/minetest/minetest/pull/973 maybe this improves situation too ;-) |
19:03 |
thexyz |
are you talking about that android port? |
19:03 |
thexyz |
they put "We'll publish the modification part the minetest engine source code to github soon." in the first post |
19:05 |
celeron55 |
yeah, saw that |
19:11 |
|
Wuzzy joined #minetest-dev |
19:16 |
|
rubenwardy joined #minetest-dev |
19:29 |
|
iqualfragile joined #minetest-dev |
19:29 |
sapier |
any comments on 973? |
19:32 |
pitriss |
guys please when will be pushed patch which increases maximum of nodes? Will this happen before 0.4.8? |
19:34 |
VanessaE |
this needs to happen before 0.4.8 imho. one-line change that has been well-vetted on two of my servers. |
19:34 |
ShadowNinja |
sapier: Wouldn't it be better to use VERSION_PATCH, VERSION_EXTRA, and VERSION_STRING; rather than VERSION_PATCH and VERSION_PATCH_ORIG? |
19:55 |
ShadowNinja |
VanessaE: https://github.com/minetest/minetest/pull/975 |
19:56 |
sapier |
VERSION_EXTRA usually isn't a number |
19:56 |
VanessaE |
yup |
19:57 |
sapier |
but file version is required to be numeric that's why I had to add VERSION_PATCH_ORIG |
20:00 |
ShadowNinja |
sapier: Use VERSION_PATCH and don-t concatenate VERSION_EXTRA to the end of it. |
20:00 |
ShadowNinja |
s/-/'/ |
20:00 |
sapier |
that'd change current way of versioning minetest |
20:02 |
|
Ritchie joined #minetest-dev |
20:21 |
ShadowNinja |
Yes, but I think it would be a better way to do it. |
20:22 |
sapier |
I don't have a problem to do it that way if there's consens to do so |
20:23 |
ShadowNinja |
I also opened https://github.com/minetest/minetest/pull/974 *Waits a few months* |
20:24 |
sapier |
none seems to want to merge anything right now ... maybe we should start regular meetings to decide what to do with pull requests |
20:26 |
ShadowNinja |
Good idea. |
20:28 |
VanessaE |
ping a few random devs :) |
20:28 |
sapier |
how many core devs are available right now? plz say something like "HERE I AM" |
20:30 |
ShadowNinja |
Pilz|Adam is. (He signs off when he isn't) kahr| and hmmmn are also usually around about now. |
20:30 |
PilzAdam |
nice anti-ping |
20:30 |
PilzAdam |
I will go to sleep soon, though |
20:31 |
sapier |
still we should talk about some way to get those pull request queue fixed ... either by tagging them 0.4.9 or merge/refuse it |
20:33 |
VanessaE |
no joke there. |
20:33 |
VanessaE |
as we say here, shit or get off the pot. |
20:34 |
VanessaE |
(that goes as much for the folks who wrote patches that need rebasing or maintenance as for the folks who are capable of merging them) |
20:34 |
sapier |
imho even if a feature is nice and usefull it may be better to be moved to a later version in order to get a 0.4.8 released this year ;-P |
20:35 |
celeron55 |
here, but going to sleep soon and reading and watching things on the internet until then |
20:36 |
PilzAdam |
I guess Ill have time at the next weekend |
20:36 |
celeron55 |
i'm with sapier with that though; there's still a bunch of critical stuff that needs to be merged in order to not create compatibility brainhurt in the future ((some of) proller's stuff) |
20:37 |
celeron55 |
anything not within that criteria goes to 0.4.9 |
20:37 |
celeron55 |
(and other trivial-ish fixes) |
20:39 |
VanessaE |
mmh |
20:39 |
proller |
3 months for merging... |
20:40 |
proller |
1 month broken weather (and peoples use it on servers) |
20:40 |
VanessaE |
one would think that a "trivial-ish fix" would be quick to be merged in ... that's the sorta stuff you may as well just put in now. |
20:40 |
kahrl |
me, I'm peeking in occasionally but as I (believe I) said some time ago I have literally no time to code or look at patches |
20:40 |
kahrl |
I even got another job since then |
20:42 |
sapier |
kahrl you're not the only one here we only need two developers to sign a patch of I assume even without you there should be enough ppl to do that work |
20:43 |
kahrl |
yes but it seems most other devs are kinda busy as well |
20:43 |
VanessaE |
kahrl: s/busy/bored of engine development\?/ |
20:43 |
sapier |
maybe we should write a list first who is actually available atm? |
20:44 |
kahrl |
VanessaE: maybe ;) |
20:44 |
PilzAdam |
VanessaE, as for me I am busy |
20:45 |
sapier |
do we have a core developer list in wiki? :-) what about adding a table <developer> <state> <estimated time till state change> ;-) |
20:45 |
kahrl |
me being busy is crap because I can't finish the httpfetch or other stuff I have started |
20:45 |
kahrl |
but not much I can do :/ |
20:45 |
ShadowNinja |
sapier: https://github.com/minetest?tab=members |
20:45 |
sapier |
state beeing "available"|"partial available"|"rarely available" and "busy" ;-) |
20:46 |
sapier |
hmm ok I guess pa is most available of those |
20:46 |
sapier |
proller and sfan5 are quite active too |
20:46 |
ShadowNinja |
Most of them are "rarely available". |
20:47 |
sapier |
yes I'd at best give pa a partly available ;-) no offence pa ;-) |
20:47 |
ShadowNinja |
Of course it depends what you define those as. |
20:49 |
sfan5 |
sapier: I'm available |
20:50 |
sfan5 |
I'll have more time on the weekend after the next weekend+ |
20:50 |
sfan5 |
s/+// |
20:51 |
sapier |
so are you ready to do some sorting of pull requests? be prepared some ppl might not be pleased if their feature is moved to 0.4.9 |
21:00 |
sfan5 |
yes |
21:06 |
celeron55 |
adding or switching core developers is an option too, but i don't want to do that unnecessarily or in such a way that isn't likely to result in anything better |
21:15 |
VanessaE |
I just wanna be able to stop telling my users "get the latest git to use my servers", at least for a little while. |
21:15 |
VanessaE |
it would be nice to just say "get 0.4.8-stable". |
21:15 |
VanessaE |
(given how many people don't even know about git, let alone those who do and refuse it) |
21:30 |
sapier |
@ALL developers please rebase all pull requests until 1st november 2013 if you want them to have a chance to be merged in this weekends pull merge session ;-) |
21:32 |
|
Gethiox joined #minetest-dev |
21:37 |
nore |
sapier, I reckon mine are ok currently... |
21:39 |
sapier |
then you don't have to do anything of course |
21:42 |
VanessaE |
afaik the one I have pending against minetest_game is good |
21:42 |
sapier |
it's just a reminder it's useless to check pulls that don't even apply |
21:48 |
ShadowNinja |
Perhaps we should have a definite time between releases, rather than "Whenever it seems ready." |
21:48 |
sapier |
a time doesn't help if you find a blocker 1 day before release the release is gone anyway |
21:49 |
sapier |
imho a feature freeze is best to do |
21:51 |
ShadowNinja |
sapier: Yes, a feature freeze would happen before, and the release could alwas be delayed a bit. But that way we don't wait a month for a release and then wait half a year. |
21:52 |
VanessaE |
crap |
21:52 |
VanessaE |
oops |
21:52 |
sapier |
after feature freeze a release should happen within reasonable time ... agreed to that |
21:53 |
VanessaE |
I can agree - provided the feature freeze lasts long enough to actually get the good, hard bufixes inm |
21:53 |
VanessaE |
bugfixes* |
21:53 |
sapier |
I think about something like 2-4 weeks between ff and release |
21:54 |
ShadowNinja |
Alright, what should the spacing between releases be? |
21:54 |
sapier |
I'd not use a fixed raster for this |
21:55 |
sapier |
but maybe we could provide unstable weekly/monthly builds |
21:55 |
ShadowNinja |
0.4.7 -- authored 5 months ago. How about 3 months? |
21:55 |
VanessaE |
if I had to suggest, 2 to 3 months maximum |
21:56 |
sapier |
minetest development seems to be quite seasonal e.g. usually christmas time lots of new features get added |
22:00 |
sapier |
ok I guess I need to do some work for modstore at least version number of a mod needs to be shown prior download |
22:01 |
ShadowNinja |
Can a dev(sfan5?) go to https://github.com/minetest/minetest/pull/856 and check the merge status? (Unfourtunately GitHub doesn't show it to non-devs) |
22:14 |
sfan5 |
ShadowNinja: 'This pull request can be automatically merged.' |
22:15 |
ShadowNinja |
Thanks. :-) |
22:27 |
|
luizrpgluiz joined #minetest-dev |
23:40 |
|
sapier left #minetest-dev |