|Hans-Christoph Steiner||Sep 13, 2011 9:06 am|
|Joe White||Sep 13, 2011 9:36 am|
|Hans-Christoph Steiner||Sep 13, 2011 11:38 am|
|Hans-Christoph Steiner||Sep 13, 2011 11:43 am|
|Joe White||Sep 14, 2011 6:22 am|
|Hans-Christoph Steiner||Sep 14, 2011 7:43 am|
|Hans-Christoph Steiner||Sep 14, 2011 8:50 am|
|Jonathan Wilkes||Sep 14, 2011 10:11 am|
|Joe White||Sep 15, 2011 5:31 am|
|Hans-Christoph Steiner||Sep 15, 2011 9:19 am|
|Jonathan Wilkes||Sep 15, 2011 9:47 am|
|Subject:||Re: [PD-dev] pd-extended 0.43 release push|
|From:||Joe White (whit...@gmail.com)|
|Date:||Sep 13, 2011 9:36:21 am|
Forgive me if this is not totally on topic but I had an idea a while ago a wondered what the feasibility of it was.
I don't really have a great knowledge of the Pd extended package but how possible would it be to have each library versioned (say on github) as individual repositories that then get pulled in the build. Maybe you could see when certain libraries have been changed and update them on your own machine. Along the idea of how macports works.
Again, apologies if this is a really stupid question.
On 13 September 2011 17:06, Hans-Christoph Steiner <ha...@at.or.at> wrote:
I was thinking that now would be a good time to start a release cycle for Pd-extended 0.43. There is a ton of really useful new stuff in the editor with the new gui, plugins, etc. So I'm thinking I'll delay some of the library work I've been doing, and revert to the 0.42.5 behavior of loading a bunch of libraries by default at startup. But I personally be dropping my support for a number of included libraries, but anyone is welcome to pick them up if they want to see them stay in Pd-extended. You can see the state of things here:
This can be a trial run of the new process of keeping things in Pd-extended. Basically, I need to reduce my maintenance load, I just can't keep up any more. So I am proposing that the new process for getting things into a Pd-extended release. First, the new release branch will be a copy of the previous release branch. Each library/doc has a maintainer, listed on the LibrariesInPdExtended page. It is that maintainer's job to update their libraries/docs into the pd-extended release branch, otherwise the version will be the same as the previous version. Each version of a library included in Pd-extended needs to a fully released version with a proper version number and a release posted on its own page in the http://puredata.info/downloads section, and ultimately uploaded to Debian/testing (I'm happy to sponsor people's packages for upload to Debian once they are ready). The full process is documented here:
Comments, feedback, concerns? I'd like to make this a much more open and participatory process.