Re: [Rails-devel] 1862 development starting back up

[Stefan F. <ste...@we...>]

My approach is similar to Martins, for the same reasons (working on 
different machines):

So I use my "private" branches (all those prefixed with sfy_) in the 
rails repos mainly for backup and synch. However it also allows others 
to have a glance how things develop.

The "official" branches (for rails 2.0 currently only rails_2_develop) 
are updated as soon as I have finished a new feature and compiles and 
runs all automated tests without an error.

For bug-fixes I usually create only a short lived branch on my local 
machine and then merge it quickly into the official branches.

This would also be my recommendation for others:
Create "private" branches for new features and prefix them with your own 
initials and push them to the official repo early and often.

As soon as you have finished something and want to add it to the central 
development merge it into rails_2_develop. Make sure that all tests are 
running. If you are not comfortable to merge yourself into Rails 2 at 
the beginning, you can always ask for my help.

Stefan


On 04/30/2014 07:41 AM, Dr. Martin Brumm wrote:
> I tend to push small pieces because i work on different systems (private
> pc at home, Laptop abroad)
>
>
> Von Samsung Mobile gesendet
>
>
> -------- Ursprüngliche Nachricht --------
> Von: Michael Alexander
> Datum:30.04.2014 06:20 (GMT+01:00)
> An: "Development list for Rails: an 18xx game"
> Betreff: [Rails-devel] 1862 development starting back up
>
> At least for a little while, unless life decides to interfere again.  I
> have gone through the old mail notes, and it looks like where I should
> be basing things on rails_2_develop, is that correct?
>
> I have a tendency to want to push things back up to the repository on a
> pretty frequent basis.  Do we have a guideline for how often is
> reasonable?  Have other Rails developers generally been working
> privately on games and then pushing a large amount all at once?  Or is
> it usually small pieces at a time?
>
> Mike
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>