KE7FNS wrote:Well, lets just take a second and follow the path and see how someone easily arrives at that conclusion though.
The pistar updates happen in the middle of the night for me. I don't have any indication that anything ever succeeded or failed (unless I decide to kick off an update manually). I have no indications that something new was added or what changes were recently made, or even as to why. To the end user there is no real noticeable difference.
Even when I come to the forum to look for update information, that information is completely absent. It should be at least mentioned somewhere, maybe in an announcements/recent updates/whats new area..
Addressing the above reply to my comments...
Sorry but I couldn't disagree with you more. ( And I don't mean that as a sign of disrespect. Personally I think both yourself and Torsen do a great job in answering Qs here on the forum, between you, you both seem to handle 98% of the questions asked her. And most all times you both give good balanced, correct answers ).
But really... you cannot argue that it's reasonable for someone to state the project has been abandoned, there have been no recent movement on the project, failure to produce new updates etc. etc. when that same person doesn't pertain the ability or knowledge to know or recognise when an update occures. It's just fueling more speculation and rumour.
although I will relent and say maybe it is a good thing they at least posted it here, if for nothing more than this thread / conversation with you guys.
Toshen: Pi-Star 4.0.x codeline went through a few release candidates, but never stabilized enough to become a regular release.
It wasn't so much that it didn't stabilise, more that Raspbian Buster became the recommended OS for 3B+ 3A+ pi's.
4.0 was built on raspbian stretch with a kernal hack written by Andy that made it work with the 3B+ 3A+ Buster made that hack irrelevant so work continued there..
and when following on up through pistar releases using different versions of the raspbian OS it isn't a simple pistar-update/ upgrade process Hence the need to reimage between 3.4 4.0 & 4.1
Jessy, Stretch, Buster. So 4.0 became 4.1
General reply comments...
re: flow of info. emmmm, not sure there... with all the distractions of everyday life, it's demand on a persons time, work, family, futhur education etc.
Time spent updating you all of progress made, intention, direction etc. is time stolen from development. I'd sooner work be done in features, updates, bug fixes etc. Then pushing out text about what changes were just made.
Ps. Personal standing.
Ive said it all along and still stick to what I believe. If pistar doesn't work for you, you have other options. ( I realise that isn't what you both are suggesting or saying above, so indulge me) but, if someone needs something more (or something less) go do it.. educate yourself. None of us wake up in the morning with instant knowledge, you learn. Learn to code, the mmdvm project is readily available and installs in practically every OS you need it to run with.
With the ability to learn, you can do what ever you need do to suit your particular use case. If someone needs a taylored install, learn how.
with a project like pistar it caters to everyone, yet no one in particular, the features you want to see aren't the features another wants to see, the time dedicated to a specific something will have no regard to someone who wants something else addressed. 4.1 is beta RC, we believe it's ready to go, but we have users who say it shouldn't be used as they have issues with it. Others reply it runs fine, but those with issue never provide enough info.
It's a two way thing development, a FB post shouting the update broke my repeater holds no info. It works fine when we revert to the old version. Ok but 500 others are using this release with no issue... So what do we do?
When pushed for info or specifics, most times we just get silence, a few specific pictures of the dashboard webpages or' I don't know anything about it, my friend set it up for us and now he's elsewhere... Were all using the same image, were all using the same foundation hardware. What makes yours or the 3 that are being reported as 'broken' different from the others ??? So you take a stab in the dark, an educated guess as to what it might be, sometimes it pays off, other times it just creates another problem.
And of course all this with out mention of changes in OS and it's dependencies, influences of software updates, firmware updates, many times that in itself makes it a rolling ball that ur trying to stay balance atop, making an ongoing progress report / update very difficult to maintain.
and finally we all know if we stated we just pushed an update that now shows the dashboards green bits to show blue, every man and his dog will blame those changes for his changes in BER, or higher packet loss, higher pi temps, broken audio, failure to login, even though nothing that would / could effect that changed. Sometimes there's a thing in providing to much info. but joking aside I do understand what ur asking for, just don't know how that can be accomplished without stealing time elsewhere.
Andrew M1DNS, (Mod)