[Python.NET] Release plan

[davidacoder]

Oh yes, this would really only be feasible once things are on github, still
thought we might start talking about it now and get people's opinion on how
they would want things to be.

I think the brunt of the migration to github is done (fingers crossed) and
it is more about a decision at this point and then a few days of finalizing
things.

I think I am mainly fishing for opinions on what would still have to be done
to release a new version. I know minimally fix the bug that prevents it from
working on Win 8.1, but I am sure other people know other bugs as well.

Cheers,
David

> -----Original Message-----
> From: PythonDotNet [mailto:pythondotnet-
> bounces+davidacoder=hotmail.com at python.org] On Behalf Of Brad
> Friedman
> Sent: Wednesday, December 4, 2013 1:18 PM
> To: A list for users and developers of Python for .NET
> Subject: Re: [Python.NET] Release plan
> 
> It's not stable enough to do point release systems. No formal system for
> stable branch vs dev branch. No central design control. No branch or
release
> maintainers. Need to get people and time and responsibilities set before
you
> can do that. Best to focus on migration to github first. At least then you
have
> tools for branching and merging. Order can come later.
> 
> > On Dec 4, 2013, at 9:54 AM, davidacoder <davidacoder at hotmail.com>
> wrote:
> >
> > Hi everyone,
> >
> > I'm trying to understand what the "official" release history is right
now.
> > PythonNet 2.0 was never officially released, correct? Was the last
> > release
> > 2.0 beta?
> >
> > In any case, I think it would be great if we released an official 2.0
> > version, provided binaries for download etc.
> >
> > My gut sense is that there would be significant benefits of releasing
> > the current version + any major bug fixes as is, i.e. hold off from
> > adding any new features. The current version seems to be used by a
> > fair number of people and useful to them, and I think it would be good
> > to have something officially released as quickly as possible. But, I
> > don't know the codebase nor history well, so please chime in if you
> > think that is a silly suggestion.
> >
> > Version 2.1 then could incorporate the various work people have done
> > on forks of the project and maybe get setup.py to work on all
> > supported platforms. We could also clean up some of the old files,
> > docs etc for that release.
> >
> > In my mind such versions 2.0 and 2.1 could happen relatively quickly,
i.e.
> > don't be multi months projects but more like a few weeks at most. In
> > general I think once we get setup/deployment via pip running, it would
> > make sense to release new versions fairly frequently, even if they
> > only add a few new features.
> >
> > Any thoughts?
> >
> > Best,
> > David
> > _________________________________________________
> > Python.NET mailing list - PythonDotNet at python.org
> > https://mail.python.org/mailman/listinfo/pythondotnet
> _________________________________________________
> Python.NET mailing list - PythonDotNet at python.org
> https://mail.python.org/mailman/listinfo/pythondotnet