Ok. Thanks.
On 1 March 2014 02:20, Jeroen De Dauw wrote:
> Hey,
>
>> If no tags for dev versions exist, take latest released and hope for the
>> best. Good luck.
>
> If you want to use a dev version, then use the appropriate branch, such as
> master. "dev-master" as version constraint. Using tags
Hey,
> If no tags for dev versions exist, take latest released and hope for the
best. Good luck.
If you want to use a dev version, then use the appropriate branch, such as
master. "dev-master" as version constraint. Using tags in this context
makes little sense.
> Ensure all packages are set to
So does this sound about right:
https://www.mediawiki.org/wiki/User:F.trott/Patching_Composer-managed_extensions_on_GitHub
?
On 28 February 2014 22:55, Jeroen De Dauw wrote:
> Hey,
>
> It is pretty much the same as for Wikibase -
> https://www.mediawiki.org/wiki/Wikibase/Contribution_workflow
>
>
Hey,
It is pretty much the same as for Wikibase -
https://www.mediawiki.org/wiki/Wikibase/Contribution_workflow
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--
--
Flow-based real-
Hi,
when SRF was managed using WMFs repo and git, my workflow was
- git pull, if necessary
- git checkout -b foo
- hack away
- git commit -a
- git review
What is the recommended workflow now?
Cheers,
Stephan
--
Flow-bas
