Spring RTS Engine

The server hosting springrts.com is migrating to a new server, so all services running on it will be offline for a while as database etc. has to be migrated. At the given time, the DNS-records will be updated, services set offline and the data migrated to the new server to be hopefully be back onlin...

yes, modtype 4 is unspported. i've created an issue:

https://github.com/spring/upq/issues/70

The old server will be switched of on April 30. 2021.

when the data is migrated, some AFAIK unused services will be not reenabled. The data will be migrated, but the services won't be activated:

- weblobby
- etherpad

"everything" wrt spring. I.e. https://liberapay.com/F-Droid-Data/income/

This would make it a bit more independant from individuals and hopefully easier to manage and more transparent.

the new server has more ram (16GB vs 10GB) and NVMe's: i don't know the exact date for the switch over, but i guess its till the end of april.

It will have a new ip: 78.46.21.29

As far as "main" spring is concerned probably yes, but within the community I'm at right now we have different planning horizon and roadmap items come and go in weeks. ok. so its sth. like "wait for BAR release(s)". Very likely i'll be busy in the next weeks with migrating sprin...

hm, so the roadmap is: "when its ready..." i guess its not useful for other projects to start migrating to sth. which isn't working: ideally a transition release can be skipped :-) Ideally I want something like "make portable" that would collect the files and prepare the builddir...

the frontend of springfiles.com wasn't maintained for a way to long time: it contained a lot of security holes, bugs, etc. Thanks to raaar it now has a new and very lightweight frontend. The old springfiles.com is still available at a new location and was made read only: it will be removed at some p...

side note: springrts.com very likely will migrate to a new and faster server soon: afaik 30 april. when this is done i plan to migrate springfiles.com to the same server: this should allow to give access to administrate it, so i'm hopefully not directly needed any more for updates of the springfiles...

without a release i don't see why should i spent any time on it. this is really needed for motivation and publicity: thats why i'm still waiting for an adjusted release roadmap for the transition changes. wrt merging: the github actions and the "transition" changes to the engine should be ...

i've switched springfiles.com to the new frontend, thanks a lot, raaar!

the old site is still available at https://springfiles.com/old/

i'm a bit out of ideas how to "migrate" the old page contents to the new page without spending a lot time into it: is it worth the trouble at all?

sorry, for the delay. its clean now!

The roadmap is rather trivial, I'm not even sure there is anything to document here. Anyway: no its not. what do you suggest to release as 106.0? it sounds like the "transition" branch. what will be 107.0? having a roadmap answers questions like this: https://github.com/spring/spring/pull...

can you please suggest a roadmap with details which branch will be merged where, and when a release should be made of what.

without a public plan i can't help.

wow, cool. as its already a huge improvement i've just dumped it live:

https://api.springfiles.com/

-> https://github.com/spring/upq/commit/f9 ... 2882fac0ae

thanks a lot already!

then we have a big problem. i always claimed that the "develop" branch will and should be continued and the maintenance branch beeing dropped: kloot has/had the same stance afaik. not sure how we can continue: suggestions welcome. suggest a roadmap please / correct the existing one. as i r...

i guess reviewing will be teamwork...

still the biggest issue is, that it is based on the maintenance branch.

the json replies lack some of the data that's on the springfiles entries, namely - thumbnail links (vs the big image links) - content description what you see on springfiles.com is close to completely unrelated to what you see on api.springfiles.com: the data is in a different database. creating a ...

P.S. I haven't been slacking either: https://github.com/beyond-all-reason/sp ... reason:BAR this seems to be based on the maintenance branch: how do we get this into the develop branch? it looks like the roadmap is wrong and 106.0 will be a continuation of the maintenance branch? if not, the develo...