OpenMW 0.27.0

Anything related to PR, release planning and any other non-technical idea how to move the project forward should be discussed here.
User avatar
psi29a
Posts: 4074
Joined: 29 Sep 2011, 10:13
Github profile: https://github.com/psi29a/
Contact:

Re: OpenMW 0.27.0

Post by psi29a » 22 Nov 2013, 17:09

No worries about the saucy ogre fix, it has been uploaded. :) cheers!

Saucy builds are now live!

User avatar
raevol
Posts: 2742
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: OpenMW 0.27.0

Post by raevol » 25 Nov 2013, 04:39

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. :(

User avatar
Greendogo
Posts: 1374
Joined: 26 Aug 2011, 02:04

Re: OpenMW 0.27.0

Post by Greendogo » 25 Nov 2013, 09:36

raevol wrote:Again I am really sorry. I wasn't expecting my life to fall over like this. :(
That doesn't sound good. I hope everything is ok, raevol!

User avatar
Zini
Posts: 5445
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.27.0

Post by Zini » 25 Nov 2013, 09:57

Um, what you linked there is for 0.26.0.

User avatar
scrawl
Posts: 2152
Joined: 18 Feb 2012, 11:51
Contact:

Re: OpenMW 0.27.0

Post by scrawl » 27 Nov 2013, 16:29

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...)

User avatar
psi29a
Posts: 4074
Joined: 29 Sep 2011, 10:13
Github profile: https://github.com/psi29a/
Contact:

Re: OpenMW 0.27.0

Post by psi29a » 27 Nov 2013, 16:42

What does it effect him and not others?

User avatar
Zini
Posts: 5445
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.27.0

Post by Zini » 27 Nov 2013, 17:39

All the 0.27.0 are already build, right? So there is no point in patching 0.27.0.

User avatar
scrawl
Posts: 2152
Joined: 18 Feb 2012, 11:51
Contact:

Re: OpenMW 0.27.0

Post by scrawl » 27 Nov 2013, 17:49

Zini wrote:All the 0.27.0 are already build, right? So there is no point in patching 0.27.0.
The point would be for distributions, e.g. the openmw package on the arch linux AUR.

User avatar
Zini
Posts: 5445
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.27.0

Post by Zini » 27 Nov 2013, 18:46

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.

User avatar
scrawl
Posts: 2152
Joined: 18 Feb 2012, 11:51
Contact:

Re: OpenMW 0.27.0

Post by scrawl » 27 Nov 2013, 19:44

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.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests