Any specific reason for $subject? How is it possible that an older branch is more up to date than a more recent branch?
You can look at the "Up-To-Dateness"
- 18.06 last commit on Tue Dec 10
- 19.07 last commit on Fri Dec 13
- 18.06 = PKG_VERSION:=0.4.1.6
- 19.07 = PKG_VERSION:=0.4.0.5
The tor update was made in the commit
Sun May 5.
The tor update to
4.1.6 was made in commit
Thu Nov 14.
They use two different branches
19.07 is still some kind of release canidate? I think they do something like fixed releases and not like rolling releases, that they have to backport everything to have some kind of
stable system. It is the same problem that you have in Debian that you get outdated software. And the package feed is community maintained. Noone backported the stuff to
openwrt-19.07, probably people stick to
Actually, I believed that they were just updating the commit version of the upstream master regularly. I did not know, that they have to backport everything and do seperated branches. Thanks for your question! Know I now more about OpenWrt.
Please, feel free to make a
PR updating Tor to the latest version! I think this is very important. Otherwise, I will do it.
Please, do! I don't have the possibility to do it at the moment.
In any case, there should be some sort of criteria that wouldn't allow an older branch to be updated before a newer one… something akin to what happens with the Linux kernel (mainline and stable trees).
People tend to agree with you; or at least can identify with what you see as a drawback of this development method:
(There are other threads for version 17 as well.)
And I believe @jow has the most poignant quotes related to your concern:
Old branches only get selected backports. Otherwise they'd basically be
One thing to look at is the last common commit with
master to know how "up-to-date" a branch really is for most of its content. Another measure is the number of commits on
master that aren't on the branch in question.
jeff@deb-devel:~/devel/openwrt$ git log -1 --pretty="%cd" $(git merge-base openwrt/openwrt-18.06 openwrt/master) Tue May 15 12:42:40 2018 +0200 jeff@deb-devel:~/devel/openwrt$ git log --pretty=oneline openwrt/master ^openwrt/openwrt-18.06 | wc -l 4771
jeff@deb-devel:~/devel/openwrt$ git log -1 --pretty="%cd" $(git merge-base openwrt/openwrt-19.07 openwrt/master) Tue Jun 11 01:49:44 2019 +0200 jeff@deb-devel:~/devel/openwrt$ git log --pretty=oneline openwrt/master ^openwrt/openwrt-19.07 | wc -l 1484
Well, apparently the version bump author made a PR for getting the version bump in master, and then also for the old 18.06, but ignored the new stable 19.07 branch ( which was only 5 months old at that point...).
I will cherry-pick those.
No reason why 0.4.1.6 would not work in 19.07 as it works in master and 18.06 (and the history between master and 19.07 only differs by two simple commits).
cherry-picked. Buildbot should build them in the next 1-2 days.
Wonderful! Building a new image as I'm writing this. Thanks a lot for the quick turnaround, @hnyman.
Hi, just to clarify the reason why the version in 19.07 was older than in 18.06.
I cherrypicked changes from master to 18.06.
The main motivation was, that version in 18.06 (0.3.2.10) was EOL and tor started to remove relays with this version from tor network. (https://blog.torproject.org/removing-end-life-relays-network)
The version in 19.07 was still supported so I didn't update it.
My understanding was, that 19.07 is in feature freeze mode and it should only receive security and important bugfixes.
I'm not sure why that quote was attributed to me; but good information and welcome to the forum community.
Heh. It was probably quoted from your reply to my post.
Even Tor has different releases. Inception style... XD