cheers!Saucy builds are now live!
OpenMW 0.27.0
-
psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: OpenMW 0.27.0
No worries about the saucy ogre fix, it has been uploaded. cheers!
Saucy builds are now live!
cheers!Saucy builds are now live!
Re: OpenMW 0.27.0
Guys- guys. I'm really sorry. Things in my personal life have gotten crazy. I'm not sure when I am going to get the time to do the release. I know it sounds stupid, but honestly finding an hour of time to do the uploads is really hard for me right now. The announcement is finished, it just needs a once-over for the additions that have been discussed since, including the release video, and then needs to be ran through this: https://github.com/mickeylyle/openmwreleasescript
If someone wants to take this for me for this release (hopefully I'll be back to normal by next release) that would be great. Again I am really sorry. I wasn't expecting my life to fall over like this.
If someone wants to take this for me for this release (hopefully I'll be back to normal by next release) that would be great. Again I am really sorry. I wasn't expecting my life to fall over like this.
Re: OpenMW 0.27.0
That doesn't sound good. I hope everything is ok, raevol!raevol wrote:Again I am really sorry. I wasn't expecting my life to fall over like this.
Re: OpenMW 0.27.0
Um, what you linked there is for 0.26.0.
Re: OpenMW 0.27.0
There seems to be a build error in the 0.27 tag due to stdexcept not being included.
Maybe we should cherry-pick https://github.com/zinnschlag/openmw/co ... 643e6c94af into 0.27 branch and re-tag?
(When I made that commit, I didn't realise the contentmodel actually existed in the 0.27 branch...)
Maybe we should cherry-pick https://github.com/zinnschlag/openmw/co ... 643e6c94af into 0.27 branch and re-tag?
(When I made that commit, I didn't realise the contentmodel actually existed in the 0.27 branch...)
-
psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: OpenMW 0.27.0
What does it effect him and not others?
Re: OpenMW 0.27.0
All the 0.27.0 are already build, right? So there is no point in patching 0.27.0.
Re: OpenMW 0.27.0
The point would be for distributions, e.g. the openmw package on the arch linux AUR.Zini wrote:All the 0.27.0 are already build, right? So there is no point in patching 0.27.0.
Re: OpenMW 0.27.0
Easy enough to patch locally (within that distribution). I would prefer not to restart the release process now. We are already late. That might make it even later.
@BrotherBrick: Different compilers/compiler versions I guess.
@BrotherBrick: Different compilers/compiler versions I guess.
Re: OpenMW 0.27.0
Downstream patches should only be used for something specific to the distribution where possible, which this clearly isn't, as I also have the problem on Ubuntu (with a manually upgraded GCC).
I wasn't suggesting to restart the release process. Just a tiny fix to the git branch. The already made builds are obviously fine. Also, I see that there's no source archive uploaded yet, so it's not like we'd have to do a re-upload there either.
If you fear that doing a (even if extremely tiny) change to the branch would require adding a new (openmw-0.27.1) tag, then I don't see the point, because the release hasn't officially happened yet, so I see no problem with changing the existing tag.
I wasn't suggesting to restart the release process. Just a tiny fix to the git branch. The already made builds are obviously fine. Also, I see that there's no source archive uploaded yet, so it's not like we'd have to do a re-upload there either.
If you fear that doing a (even if extremely tiny) change to the branch would require adding a new (openmw-0.27.1) tag, then I don't see the point, because the release hasn't officially happened yet, so I see no problem with changing the existing tag.