My understanding of these matters is by no means authoritative, but I 
*think* the info I am giving you here is accurate.

On 4/27/2014 2:05 PM, Carl M Jacobson wrote:
> Is the MuseScore repository on GitHub updated continually, daily, Nightly of
> other?

It is updated whenever a pull request is merged - that's what the pull 
request process is for.  PR's tend to get processed in batches.  They 
may pile up for a few days, then a whole bunch will suddenly get merged; 
others might be merged at different points throughout the day.  
Basically, whenever lasconic or werner are in the mood to do some 
merging :-)

> Does my forked version update every time the MuseScore repository changes?

No.  When you fetch from the upstream to your local version, you can 
push to your fork on GitHub if you want to keep it in sync.  In 
practice, it's not necessary to do this - the process of pushing your 
own work to your fork also brings in the changes you have fetched.  Just 
follow the process outlined in the Git Workflow document and you will be 
fine.

> When I clone a version of the my repository on my machine is it a one time
> clone or a link to the forked repository?

One time thing.  You might want to read some Git documentation to get a 
feel for how it works, but basically, as described in the aforementioned 
document, you will update your local repo with changes from upstream by 
doing a periodic "fetch", and when you have changes you want to publish 
to your fork on GitHub, you do a "push".  When you are ready for someone 
to look at your code and decide whether to merge it into the main 
upstream repository, you do a pull request.

> Is there a way to automate the update of my cloned version to automatically
> receive any changes to the current MuseScore repository after each
> successful build?  Process would need to query me if attempting to overwrite
> code I have modified?

I wouldn't really recommend that; you never know what other effects 
there might be even when incorporating code you haven't actually 
modified.  Plus chances are those changes will force a full recompile, 
which can take an hour or more.  I like to get my code working with a 
*known* snapshot, then fetch and rebase when I'm done, as described in 
the Git Workflow document.  But you could presumably set up some sort of 
script to automate this is you really want.

> My goal initially will be to fix every bug or defect I get my hands on as
> quickly as possible. I would rather deal with last nights bugs then to spend
> time fixing bugs that were corrected the night before.

I would advise not touching bugs that were introduced the night before - 
whomever introduced them will be in a much better position to fix them.  
I'd suggest targeting the bugs that have been around a while and are in 
a relatively stable part of the code.


> Not yet highly experienced with GitHub, I am assuming like other SVN
> software it will notify me when my version is not in Sync with the MuseScore
> repository and give me the options to merge or not merge recent or open
> software changes.

Not sure what you mean by this.  Git doesn't proactively send out 
notifications if that's what you mean.  But you can subscribe to the 
commits feed on GitHub to find out when changes have been merged (as 
well as other activity).

> Lastly has anyone developed an install process for a MuseScore development
> environment that can:
>
> Can validate whether all dependencies for MuseScore development exist on a
> given OS and machine (processor)?
> Can automate and install a complete MuseScore development environment based
> on a given OS?

Interesting idea!  But I'm not aware of anything like that.

Marc


------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to