Thanks for the merging howto, looks useful. At this point, only bug fixes should be added to the release branch. Adding new code could likely further the delay the release while we wait for the bugs to settle. Right now PDP is sensitive to changes, so it would be best to leave it like it is for this release.
The reason for the branch is to make it easier to make a stable release. It is only used during the final release cycle. Then it is back to "trunk" once the release is done. .hc On Jun 4, 2008, at 10:30 PM, Luke Iannini wrote: > Yo yves, > There is branches/pd-extended/v0-40 that produces the release, you'll > have to merge over any changes. > I wrote a guide here if you need it > http://puredata.info/docs/developer/MergingHowto > > Cheers > Luke > > On Wed, Jun 4, 2008 at 8:36 AM, ydegoyon <[EMAIL PROTECTED]> wrote: >> >> ola, >> >> sorry, why PiDiP version is 0.12.22 >> when i committed a 0.12.23 in the trunk? >> > >> isn't it produced from the trunk ? >> this is somewhat important for us >> to have the new pdp_v4l2 and pdp_ieee1394 >> for cameras >> >> thx, >> sevy >> >> Hans-Christoph Steiner wrote: >>> For this release, there has been a lot of work in making the GUI and >>> user experience much more fluid and easy. >>> >>> >> >> >> _______________________________________________ >> Pd-list@iem.at mailing list >> UNSUBSCRIBE and account-management -> http://lists.puredata.info/ >> listinfo/pd-list >> > > _______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> http://lists.puredata.info/ > listinfo/pd-list ------------------------------------------------------------------------ ---- http://at.or.at/hans/ _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
