From nl at nachtgeist.net Sat Mar 12 07:37:05 2016 From: nl at nachtgeist.net (Daniel Reichelt) Date: Sat, 12 Mar 2016 13:37:05 +0100 Subject: [Unison-hackers] Debian stretch and Unison release Message-ID: <56E40D71.5030204@nachtgeist.net> (Sorry for double-posting, I confused the -hackers ML address) Hi Benjamin, hi St?phane, plenty of time to go, but I was wondering what your plans are for the next Unison release. I'm asking because I'd love to see a current version being included in the next Debian stable release. The schedule according to [1] is: [2016-Nov-05] Transition freeze [2017-Jan-05] Soft freeze (no new packages, no re-entry, normal migrations) [2017-Feb-05] Full freeze Thanks Daniel [1] https://release.debian.org/ From bcpierce at cis.upenn.edu Wed Mar 16 21:27:37 2016 From: bcpierce at cis.upenn.edu (Benjamin C. Pierce) Date: Wed, 16 Mar 2016 21:27:37 -0400 Subject: [Unison-hackers] Debian stretch and Unison release In-Reply-To: <56E40D71.5030204@nachtgeist.net> References: <56E40D71.5030204@nachtgeist.net> Message-ID: Hi Daniel, 2.48 is the latest stable release. The development trunk is at 2.49, with no huge changes but a few things that would probably be nice to push out into the world (e.g., a preference to treat whole directories atomically). We should probably plan a beta-release over the summer and push it to stable in the fall. The only downside, of course, is that 2.49 will be incompatible with 2.48. (In the longer run, this is something we should really consider fixing. It would not be trivial, since the assumption that both sides have the same sets of preferences is built into the code pretty deeply, but perhaps there is something simple one could do that would work pretty well ? e.g., perhaps some preferences could be marked as affecting only the client, not the server, and differences in these would not cause version incompatibility.) Best, - Benjamin > On Mar 12, 2016, at 7:37 AM, Daniel Reichelt wrote: > > (Sorry for double-posting, I confused the -hackers ML address) > > > Hi Benjamin, hi St?phane, > > plenty of time to go, but I was wondering what your plans are for the > next Unison release. I'm asking because I'd love to see a current > version being included in the next Debian stable release. > > > The schedule according to [1] is: > > [2016-Nov-05] Transition freeze > [2017-Jan-05] Soft freeze (no new packages, no re-entry, normal migrations) > [2017-Feb-05] Full freeze > > > > Thanks > Daniel > > > [1] https://release.debian.org/ > _______________________________________________ > Unison-hackers mailing list > Unison-hackers at lists.seas.upenn.edu > http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers From bcpierce at cis.upenn.edu Sat Mar 26 17:54:12 2016 From: bcpierce at cis.upenn.edu (Benjamin C. Pierce) Date: Sat, 26 Mar 2016 17:54:12 -0400 Subject: [Unison-hackers] Unison repo now live on Github Message-ID: <2B72B7E5-83F5-46BC-B838-F4985AAE1861@cis.upenn.edu> Dear Unison community, After the public discussions a few weeks ago and some more investigation of alternatives, we?ve decided the best path forward for maintaining the Unison sources is a Github repository. With kind assistance from Paul Phillips, we?ve now transferred the contents and history of the old subversion repo, and I?m pleased to announce that the new git repo is open for business here: https://github.com/bcpierce00/unison Hopefully the new organization will make it easier for interested community members to contribute to Unison?s ongoing maintenance and development. Anyone interested in following or contributing to Unison is invited to ?watch? the repo. You?ll need a (free) github account. The github setup also includes an integrated issue tracker. We?d like to particularly invite the many readers of these lists that have given their time answering questions and helping with problems (thank you!) to watch the repo and help resolve issues reported there. Best, Benjamin