Closed knight-of-ni closed 8 years ago
Is it worth announcing and releasing the updated website, along with a blog post to match?
http://zoneminder.github.io is the current dev snapshot of the website.
On January 1, 2016 11:08:34 AM MST, Pliable Pixels notifications@github.com wrote:
I don't think there is a workaround. We should probably move to git subtree instead - that should take care of this problem.
Reply to this email directly or view it on GitHub: https://github.com/ZoneMinder/ZoneMinder/issues/1115#issuecomment-168324349
Sent from my Android device with K-9 Mail. Please excuse my brevity.
@kylejohnson Sounds fine to me. Feel fee to edit the release notes and add your comments.
@kylejohnson - absolutely. Better to start soon and iterate quick. Keeps the tempo going! The image should be removed (not licensed) and the Jumbotron reverted to black on grey. I'll do a PR later tonight if you don't already do it.
@kylejohnson - https://github.com/ZoneMinder/zoneminder.github.io/pull/5
@knnniggett I saved it as a draft as the other option looked like it would do a new release, you should see the PR's listed, and can publish. I changed headings to ## so I could use ### for a subheading that was in the log. Also my PR for the changelog can be merged in to include it all in CHANGELOG.md
Merged #1172 . Sorry, I didn't notice that pr was directed at me.
I just discovered that, when you save a (pre)release as a Draft, rather than Publish it, The Public cannot see either the modified version or even the original unedited (pre)release. It seems to just completely disappear off the Releases page.
I am going to create Release Candidate 2 in a day or so as there are already some changes we need to add to the 1.29 branch.
In order to update the tag and commit hash, it looks like I've got to delete and then recreate the entire pre-release. Following that, feel free to modify the Changelog only if you want to. I don't think it needs to be 100% perfect.
The other option made it sound like I was doing another release, but I guess it just republishes that existing one. I will update my PR on github-changelog-generator so you can also grab that and run it, they wanted me to fix some formatting but I haven't had time. But also happy to run everyday and put in a PR on CHANGELOG.md, then you just grab what you want when ready to release. I suspect it might keep 1.29.0rc1, then 1.29.0rc2 etc, then 1.29.0, won't know until we release them. Bit of a chicken or egg problem with Changelogs as updating them is also a PR.
bundle exec github_changelog_generator -t [InsertToken] -o ../CHANGELOG.md --no-issues --release-branch master ZoneMinder/ZoneMinder
I've merged #1222 into the 1.29.0 branch, and will test one more time, hopefully this evening. Assuming I don't run into any new issues, I will create Release Candidate 2.
Do you want me to do a PR for not showing the server column on the console for the non-multi-server case? I kinda think I should.
Yeah, that's probably a good idea.
Now that 44f3b99 hides the server column when not using mutliserver, are we ready for RC2?
I am.
Please be advised though that once 1.29 is out, I have a ton of stuff to merge for 1.29.1. And stuff for 1.30. It will be interesting to see how people react to the multi-server stuff.
BTW thanks for doing the multi-server documentation. You guys probably did a better job of it than I would have anyways.
Yeah, that's why I'm pushing hard to get 1.29.0 out the door. It is holding us up. @SteveGilvarry has a bunch of stuff too, including his video branch.
@connortechnology After building and testing from the latest 1.29.0 branch, I seem to re running into a new issue with Multi-server. I was able to duplicate, and solve on my own system the issue described in the forum about the zm processes running on the wrong machine.
However, once I got past that I noticed that all the camera links in the web console were all pointing towards the local host machine, rather than the name or ip of the server the camera was hosted on. Can't help but wonder if commit cb7acb3 had anything to do with that.
UPDATE: Nope, reversing cb7acb3 did not make any difference
You say all the web links? Only the actual live steam link should point to the recorder. Everything else should stay on whatever server you are hitting. I'm planning long term to make it so that a recording server doesn't even need Apache at all. Just a persistent zms r something like that.
If I open my browser to zm server A, and I hover over the link to a open a monitor for a camera that is mapped to server B, the link contains server A's hostname, rather than server B. So naturally when I click the link to open the monitor, I don't get a stream because the link is pointing to the wrong server. The backend is working, because I see "Capturing at x.xx fps".
The monitor view should be hosted on server A, but the img element in that view should point to server B, no?
On January 30, 2016 4:15:43 PM MST, Andrew Bauer notifications@github.com wrote:
If I open my browser to zm server A, and I hover over the link to a open a monitor for a camera that is mapped to server B, the link contains server A's hostname, rather than server B. So naturally when I click the link to open the monitor, I don't get a stream because the link is pointing to the wrong server. The backend is working, because I see "Capturing at x.xx fps".
Reply to this email directly or view it on GitHub: https://github.com/ZoneMinder/ZoneMinder/issues/1115#issuecomment-177327440
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Well, that's not how I remember it working the last time I tested multiserver. I guess I'll have to take another look.
It has never worked that way. It stays on the same server as much as possible. Only live streaming data hits the recording server.
My servers are all pretty stressed, so i actually use a non-recording server to access the ui.
Yeah, I think I need to start over and try again because none of camera streams display the live stream anymore. The backend works. Just not the frontend.
I'd like to propose inclusion of this PR: https://github.com/ZoneMinder/ZoneMinder/pull/1254 --> so zmNinja for android doesn't keep streaming data in the background once 1.29 hits mainstream
Propose it all you want. It's already merged.
heh, so that's what I asked on IRC - I was given to understand merged doesn't necessarily mean included in 1.29. If it will be, thanks!
Merged into the master branch does not necessarily mean merged into the release-1.29.0 branch. This statement is true.
Closing. We're done! woo hoo!
Good job on managing the release process, rc worked very well. On Thu, 4 Feb 2016 at 1:47 PM, Andrew Bauer notifications@github.com wrote:
Closing. We're done! woo hoo!
— Reply to this email directly or view it on GitHub https://github.com/ZoneMinder/ZoneMinder/issues/1115#issuecomment-179588337 .
congratulations to the entire team!
Gentlemen,
First of all, thank you very much for all that you do for ZM. I have been using it since 1.24 with great success in multiple locations. It has become easier & easier to maintain & better every version.
I know this is probably forum questions but I have 2 questions that I wanted the development team to see.
All in all a terrific job & you should all be congratulated.
Thank you.
Andrew Peykar
You can send money directly to me. :)
Alternatively, go to bountysource https://www.bountysource.com/teams/zoneminder
The stable zoneminder PPA should already have packages for 1.29, I put them up yesterday.
Perhaps we should have a ZM bitcoin address... I'm happy to hold the wallet...
I'm glad our policy of package based installation, over from-source builds, is having the intended effect on our end-users. I still shudder when I think about how the forums used to be years ago.... Most of the topics being posted were build problems, and those same problems would repeat with each upgrade of ZoneMinder or the underlying OS. That left little time to make progress on anything else.
Lately, we have been talking about the future of ZoneMinder. In order to get the project to make real progress, we need to grow it into something more than a free-time hobby, but of course that requires money. That in turn requires a source of revenue.
One thing we have discussed to help make that happen is to find a commercial entity out there who would be willing to be a showcase for the ZoneMinder product. Additionally, we are looking for customers interested in a support plan. @apbb2 If you are interested in either of these, then please contact us.
I am interested in both possibly showcasing & helping out monetarily (somewhat, I only have so much in my budget). Contact me off list so we can discuss if you like.
Isaac, any chance for an upgrade using 12.04 or is it not supported? That’s why I did not see the upgrade as all my current units are on 12.04
Thanks.
Andrew Peykar
Put $200 in BountySource. Thanks again for all your hard work guys.
Thanks @apbb2 That's much appreciated.
@onlyjob FYI 1.29 is released, just in case you were not aware. https://github.com/ZoneMinder/ZoneMinder/releases Note don't use Source Code links in github due to missing submodules. ZoneMinder-1.29.0.tar.gz link instead
Thanks, @SteveGilvarry. I'll be working on 1.29.0 soon...
Supersedes #549
This is my attempt to document what we need to complete before we release:
@knnniggett
zms is causing memory corruption in some of my test environments. I've spent quite a bit of time on this. I identified the line of code causing the crash but have so far not been able to determine why. Will create an issue and document what I've done and get others to look at it. #1153 fixed by #1168Assist @SteveGilvarry with #1167 as neededRemove absolute URL's as identified in #1042. Open PR #1121libvlc segmentation fault #1179Multi-Server Documentation #1211@connortechnology
Finish multiserver #1040Multi-Server Documentation #1211@pliablepixels
Confirm we've reached a good stopping point for development of the APIKeep all his cool new ideas to himself until after we release, so our heads don't explode. :-)API Security #1196@kylejohnson
Fix #1085 . Sounds like we just need to add an index.#1120 Update the url zmupdate.pl uses@SteveGilvarry
#1167libvlc segmentation fault #1179Multi-Server Documentation #1211Anything not mentioned here means we do not plan to include it in the next release, so please comment if I am missing something.
Once these items are completed, I plan to immediately create a draft release for beta test. We've changed quite a bit this round, and I expect there to be issues we have not discovered yet.