Jibble

Author Topic: Giving away the control on project  (Read 1403 times)

Giving away the control on project
« on: 01 May 2017, 20:50 »
So, I was not following the thread I myself started for a while, and I do not attend AGS chats (not even sure how many of them are). But from what I know from discussion on github, Alan decided to make next version of AGS stripped of legacy stuff (obsolete features, script commands, and so on).

There may be an argue on what should be considered obsolete and removed, but that's not the point of my post.
The point is that do not want to be the one who controls the project and determines its goals anymore. Putting this simply, I do not want to keep being responsible for this. Think what you want about it; but I am tired and full of doubts.

Currently, the list of repository management is as following:

Administrators (these can add/remove other people and do some highest administration tasks): JJS, me, Nick Sonneveld.
Committers (these can push changes to the code without having to make pull requests): me, Gurok, monkey0506, BigMC, tzachs.

I could add Alan to committers and let him do as he plans. I could also add anyone else, if that would be wanted.

For myself, I would like to retain release-3.4.1 branch, where I finish making AGS 3.4.1.

blur

    • blur worked on one or more games that won an AGS Award!
    •  
    • blur worked on one or more games that was nominated for an AGS Award!
Re: Giving away the control on project
« Reply #1 on: 04 May 2017, 23:37 »
Thanks for the heads-up!
So to get bug fixes and updates for AGS I would need to follow your "release-3.4.1" branch?
And to get the new AGS (that won't play the old games), I would follow the "master" branch?
I cannot see a "release-3.4.1" branch though:
Code: [Select]
$ git branch
  develop-3.3.1
  develop-3.3.5
  develop-3.4.0
* master
  release-3.3.4

Do I use the right repository URI?
Code: [Select]
$ git remote -v
origin  git://github.com/adventuregamestudio/ags.git (fetch)


???

Re: Giving away the control on project
« Reply #2 on: 05 May 2017, 00:15 »
"git branch" displays only local branches. You need to use "git branch -r" to make it list remote branches.

Also, I recommend two commands:
Code: Bash
  1. git fetch origin
  2. git remote prune origin
  3.  
They will bring remote information to actual state.