Testing branch

Testing branch

Discuss the source code and development of Spring Engine in general from a technical point of view. Patches go here too.

Moderator: Moderators

Post Reply
User avatar
hoijui
Former Engine Dev
Posts: 4344
Joined: 22 Sep 2007, 09:51

Testing branch

Post by hoijui »

what i think of:
a git branch called testing (there may be better names). patches from people without commit rights first go here if it is unclear if they are good or need revising. same for stuff that may behave differently on different hardware/OSs, and the dev does not have the systems to test. also if the dev just want to test compile his stuff on a different OS, and has no cross-dev set up, and this way he can use buildbot. right now, i have a commit i am unsure about, and id like some of the other devs to revise before putting it into master, just to get it reverted or fixed multiple times.
in this branch, we could probably even permit forced pushes, and it would not matter much if stuff there does not compile.

of course i know, i am free to create such a branch, but it wont be very useful if i am the only one using it (though i might be the one where this still would give the greatest benefit ;-) ). it would work best if we generally use it, for commits that we are not sure about.

maybe (in addition) we could even open a second github account, fork spring there, and give push rights to anonymous, and advertise it a bit/make it official.
Auswaschbar
Spring Developer
Posts: 1254
Joined: 24 Jun 2007, 08:34

Re: Testing branch

Post by Auswaschbar »

hoijui wrote:maybe (in addition) we could even open a second github account, fork spring there, and give push rights to anonymous, and advertise it a bit/make it official.
Unnecessary since everyone can signup github for free and create his own fork.
User avatar
SpliFF
Posts: 1224
Joined: 28 Jul 2008, 06:51

Re: Testing branch

Post by SpliFF »

I haven't found github difficult to use for forks. Also it spreads the total storage for the project over several accounts which should help us avoid githubs storage limit (it looks quite low, about 300Mb per account; I'm already using 1/3rd of that).

If Spring devs wanted to track one of my 'testing' branches they just need to set their account to 'watch' that branch and your dashboard should then show all commits and comments.
Tobi
Spring Developer
Posts: 4598
Joined: 01 Jun 2005, 11:36

Re: Testing branch

Post by Tobi »

SpliFF wrote:I haven't found github difficult to use for forks. Also it spreads the total storage for the project over several accounts which should help us avoid githubs storage limit (it looks quite low, about 300Mb per account; I'm already using 1/3rd of that).
Actually every fork counts as a whole (as far as I have seen), probably the fact that git can be pretty efficient when dealing with forks on the same disk just allows them to "oversell" the disk space a lot.

And indeed the watch/follow feature on github works quite nicely, I personally try to watch every semi-active Spring fork I can find, and get all stuff that happens on them simply in the single RSS feed of my dashboard.

Anyway, personally I'd say, just create topic branches if you need them. I think a single test branch becomes too messy soon, in particular if multiple people happen to want to test something at the same time.

(Oh, and do clean them up once you are done with them. Remembers me I still need to finish the stuff in the losshare branch ;-))
Post Reply

Return to “Engine”