Re: [python-control-developers] [python-control-announce] Python-control development environment shifted to github

[Richard M. <mu...@cd...>]

I agree that we should think about pushing 0.6.5 out to SourceForge and then we can put that on PyPI as well.  

I also like the idea of usign the standard GitHub workflow, with new features done in a branch and then a pull request that gets handled by someone other than that branch developer (so that two sets of eyes have a look at it).  

How about something like this:

* We work on releasing 0.6.5 that fixes up a few critical issues (we can flag those in github), but otherwise goes out soon (next few weeks).  Version 0.6.5 would then get pushed out to SourceForge and PyPI as an official release, with e-mail to python-control-announce.

* We shift to a branch-based workflow where future changes are done on a branch and generate a pull request to this list when ready to be incorporated.  Anyone who is interested can comment on the pull request and someone other than the developer eventually does the merge (we can assign someone as part of the pull request process).

* While I agree that the master branch should always be deployable, not sure yet whether we should generate a new release (on SourceForge and PyPI) every time someone adds a feature.  We could do that at a slower pace and just push out things at the level of "0.7" when we think we have collected enough changes to make a difference.

I suggest we try to close on this by 1 Dec (Mon) AoE and then see if there is a consensus on how to move forward.

-richard

> On 27 Nov 2014, at 7:58 , Clancy Rowley <cwr...@Pr...> wrote:
> 
> Or another option would be to add a new release to the sourceforge site.  This might be better, since I think a number of small things have been fixed (e.g. dare) in the release that is on github, so reverting to the previous version would break these again.
> 
> Also, it may be worth discussing what the project's "workflow" should be, now that we have moved to github.  For instance, we could agree to use the "GitHub Flow" workflow discussed here:
> 	https://guides.github.com/introduction/flow/index.html
> in which we develop new features on side branches, and the master branch is always deployable.  This might be nice, as it would be clear what the "current version" is (it is always the master branch).
> 
> But there are other possible workflows one could use too, for instance as discussed on the bitbucket site:
> 	https://www.atlassian.com/git/tutorials/comparing-workflows
> 
> -clancy
> 
>> On Nov 26, 2014, at 8:08 PM, Scott C. Livingston <sli...@cd...> wrote:
>> 
>> Furthermore, the release on PyPI should *not* be 0.6.5.  It appears
>> that this was done by someone uploading the tip of master.  Relevant
>> discussion appears on issue #19
>> (https://github.com/python-control/python-control/issues/19#issuecomment-51902320),
>> in particular @jgoppert wrote "I went ahead and uploaded it to pypi
>> since there is no significant difference from what was up there
>> currently."  I could not tell from from the context what is being
>> referred to by "it".
>> 
>> Unless I am missing something, the best course of action is for
>> someone with admin capabilities to remove 0.6.5 and 0.6.6 and upload
>> 0.6d.  The goal is to have the current release as available from PyPI
>> be the same as that available from
>> http://sourceforge.net/projects/python-control/files/
>> 
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
>> _______________________________________________
>> python-control-developers mailing list
>> pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-control-developers
> 
> 
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> python-control-developers mailing list
> pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-control-developers