Jump to content

Planned Disruption - Migration to git and Gitea


Itms
 Share

Recommended Posts

9 minutes ago, Lion.Kanzen said:

Yes, I see that the folder has the pyrogenesis executable.

But how do I know if it's recent?

 

It's updated every day :) so modification date should be today if your svn is up to date. Also you can launch it and see the version in the main menu

Link to comment
Share on other sites

36 minutes ago, Stan` said:

It's updated every day :) so modification date should be today if your svn is up to date. Also you can launch it and see the version in the main menu

What time  zone ( hour) does the system use to update?

Yesterday I made the first update 

Link to comment
Share on other sites

1 hour ago, Stan` said:

Image above is the git repo not the SVN one. But it's the same for changes. You can see them on clicking on the button that says "commits"

If that is what I understand, it is the same for the changes, and so it has been with the other services.

 

1 hour ago, Stan` said:

2AM GMT+1 (so 16hours ago)

8 PM in my Time zone. Sounds like it makes sense.

If I update and there are many changes before the auto-build, Should I have errors or a crash?

It sounds logical to me. The difference is that before updating I looked at the automatic build changes.

By the way, I'm on my cell phone, where should I see the auto-build changes?

Screenshot_20241017-115431.thumb.jpg.2b8ee79daf0adfa4a1a459637e614d81.jpg

Link to comment
Share on other sites

  • 2 weeks later...
38 minutes ago, Gurken Khan said:

Can "Development" in the site menu now go to gitea?

Can https://gitea.wildfiregames.com/  get "FAQ" and "wiki" links real biggly and obvious?

I feel lost with this new site.

Before it was easy to search in the trac, now I don't know how it is organized.

It's going to take me a while to find everything.

  • Like 1
Link to comment
Share on other sites

Ok the place you most often want to be is the repository home.

Near the top you can see “issues” which is where all the tickets are that were formerly on trac.

you can also click commits where you can see a big list of all the commits. Searching commits here is a lot better than in phab.

in order to make a pull request you first make a “fork”. You can do this by simply clicking the fork button and filling in the prompts if you’re signed in.

then over on your fork 0ad/My_username, you should make a branch named after what you want to change.

then add some changes to this branch (either directly online, or by cloning the repo, committing changes, and pushing them)

then you can make a new pull request based off of this branch by clicking a new pull request and setting the target repository to 0ad/0ad
Alternatively, you get a prompt to make a new pull request when you return to 0ad/0ad, and I prefer this way as there are less clicks.

  • Thanks 1
Link to comment
Share on other sites

5 hours ago, Gurken Khan said:

Can "Development" in the site menu now go to gitea?

That works for me? Changed it recently Ah you mean the forums? Fixed.

5 hours ago, Gurken Khan said:

Can https://gitea.wildfiregames.com/  get "FAQ" and "wiki" links real biggly and obvious?

Edit: Could the redirection on https://trac.wildfiregames.com/log/ps go to the gitea version?

Pinging @Itms as I cannot do that.

  • Thanks 1
Link to comment
Share on other sites

7 hours ago, Gurken Khan said:

Can https://gitea.wildfiregames.com/  get "FAQ" and "wiki" links real biggly and obvious?

What about now?

On 12/10/2024 at 9:23 AM, Itms said:

However, I could definitely add a "Main repository" button in that top bar. I can even make it a 0ad-wheel-logo instead of a text button.

Finally gotten around to doing that too.

 

7 hours ago, Gurken Khan said:

Could the redirection on https://trac.wildfiregames.com/log/ps go to the gitea version?

I have many improvements to perform on this redirection tool, I will look into them ASAP.

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...

We have seen much activity on the new platform since August :) That makes me happy, proud of the migration, and grateful for the contributions :give_heart2:

Now the pull requests have accumulated and we need some common rules to be efficient in reviewing. Of course, new PRs get more attention, and it's natural that some big/involved PRs spend more time in the review queue.

The situation on Phabricator ended up unmanageable but I believe it had a lot to do with the UI. On Gitea it is immediately obvious how large the review queue is and what needs to be looked at. The only thing I think is missing is an equivalent of the "Changes Planned" status, i.e., the PR is not going to be abandoned, but the author is going to change things, and thus a final review is not wanted for now. This would allow team members to focus on ready-to-commit work that is sitting at the bottom of the pile.

I propose to use the WIP: prefix for that situation. The PR is modified to WIP again when the author is still heavily modifying their proposal, or when a decision cannot be made right now. This doesn't prevent the CI to run, checks to pass, etc. On the other hand, at a glance, developers can see which older PRs need some final review. The community can also see where contributions are needed and what is the load status of the review queue.

Would that sound good? Pinging the contributors with open PRs. If I start to set some PRs back to WIP, I wouldn't want contributors to think this is a rebuttal, but just some housekeeping.
@paczek@Vantha@abian@real_tabasco_sauce

  • Like 5
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...