SMFArcade.info > News & Announcements

Changes to development

<< < (3/3)

Skhilled:
Now to see if it get implemented and how long before another upgrade.

fwitt:
I think it will take more than just the one minor bug fix to trigger the next upgrade.

I picked something simple to do as I was running through githubs tutorial.

Skhilled:
Yeah, I know. ;)

Hopefully, it will get things rolling.

fwitt:

--- Quote from: fwitt on August 24, 2011, 02:14:34 PM ---Made my first attempt at a bug fix https://github.com/nikop/SMF-Arcade/pull/1

fixes the bug on issue tracker http://smfarcade.info/forum/index.php?issue=479.0

simple small change to see if I have worked out how to use github correctly

--- End quote ---

Niko pulled it into the main repository the day after i posted it, i didn't pick up on the change till today. I also changed the wrong branch meant to fix it in 2.5 but fixed it in the development (2.6) branch and cant currently spot how to push it to the 2.5 branch or indeed make changes to the 2.5 branch. So obviously missed something somewhere.

fwitt:
finally found time to work out what I did wrong last time and have pushed to correct branch this time.

think I now have the (basic) idea of how github works.

If Underdog doesn't object I'm going to test this new found knowledge by trying to create a branch to match his unofficial version and see if I can push the bug fixes from that into the main branches.

Once I have the bug fixes into 2.5 I'll put it out to the beta team. New features are better going into the development (2.6) branch of code.

If anyone can think of any other bugfixes that need to go into the 2.5 code point me to either the post or the issue tracker for the relevant item in the issue tracker. Bugs that someone has a solution for first as that should make the merges easier to do that way round.

Navigation

[0] Message Index

[*] Previous page