<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Mark,<div><br></div><div>I just released</div><div>pom-bigdataviewer 1.1.2</div><div><div>bigdataviewer-core 1.0.8</div></div><div><div>bigdataviewer_fiji 1.0.10</div></div><div><div>bigdataviewer-server 1.0.3</div></div><div>Parent of pom-bigdataviewer 1.1.2 is pom-fiji 8.0.0.</div><div><br></div><div>best regards,</div><div>Tobias</div><div><br><div><div>On 18 Mar 2015, at 17:42, Mark Hiner <<a href="mailto:hiner@wisc.edu">hiner@wisc.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div>Hi Tobias,<br><br>>I really do have to fix ij1-patcher before uploading anyway<br><br></div>Just wanted to let you know that the latest ij1-patcher and imagej-legacy are released.<br><br></div>Let me know if you run into any problems!<br><br></div>Thanks,<br></div>Mark<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 16, 2015 at 6:06 PM, Tobias Pietzsch <span dir="ltr"><<a href="mailto:pietzsch@mpi-cbg.de" target="_blank">pietzsch@mpi-cbg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Mark,<div><br></div><div>imglib2-tests and</div><div>imglib2-algorithm-gpl</div><div>are fixed already.</div><div><br></div><div>I’ll check BDV and TrackMate tommorrow.</div><div><br></div><div>all the best,</div><div>Tobias</div><div><br></div><div><div><div><div class="h5"><div>On 17 Mar 2015, at 00:03, Mark Hiner <<a href="mailto:hiner@wisc.edu" target="_blank">hiner@wisc.edu</a>> wrote:</div><br></div></div><blockquote type="cite"><div><div class="h5"><div dir="ltr"><div>>Next pizza & beer are on me.</div><div><br></div><div>You should rename packages more often! :)<br></div><div><br>Neither of you should be hard on yourselves - our release history is filled with mistakes like this, and worse. Until dependency convergence is automatically tied to the release process, there will be more.<br><br>>If you could point me to packages that are hit by the imglib-algorithm change<br><br></div><div>Potentially affected components that I know of:<br></div><div>BDV-core<br></div><div>TrackMate<br></div><div>imglib2-tests<br></div><div>imglib2-algorithm-gpl</div><div><br></div><div>I really do have to fix ij1-patcher before uploading anyway, and just adding back the moved classes would be minimal effort. So the situation is far from dire.<br><br></div><div>Best,<br></div><div>Mark<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 16, 2015 at 4:43 PM, Tobias Pietzsch <span dir="ltr"><<a href="mailto:pietzsch@mpi-cbg.de" target="_blank">pietzsch@mpi-cbg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hmm, actually I think I’m to blame in this case because I did the release without properly thinking about the version numbers.<div>If you could point me to packages that are hit by the imglib-algorithm change, I’ll try to fix them.</div><div>best regards,</div><div>Tobias</div><div><br><div><div>On 16 Mar 2015, at 21:58, <<a href="mailto:tinevez@pasteur.fr" target="_blank">tinevez@pasteur.fr</a>> <<a href="mailto:tinevez@pasteur.fr" target="_blank">tinevez@pasteur.fr</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div dir="ltr" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic',sans-serif;font-size:12pt"><div>Fudge fudge fudge I did this.</div><div>I am really sorry this is something I vastly overlooked.<span> </span><br></div><div><div>Next pizza & beer are on me.</div><div><br></div></div><div style="padding-top:5px;border-top-color:rgb(229,229,229);border-top-width:1px;border-top-style:solid"><font style="line-height:15pt;letter-spacing:0.02em;font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic',sans-serif;font-size:12pt" face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'"><b>De :</b> <a href="mailto:hiner@wisc.edu" target="_blank">Mark Hiner</a><br><b>Envoyé :</b> lundi 16 mars 2015 20:38<br><b>À :</b> <a href="mailto:pietzsch@mpi-cbg.de" target="_blank">Tobias Pietzsch</a>,<span> </span><a href="mailto:tinevez@pasteur.fr" target="_blank">Jean-Yves Tinevez</a><br><b>Cc :</b> <a href="mailto:imagej-devel@imagej.net" target="_blank">imagej-devel@imagej.net</a></font></div><div><br></div><div dir=""><div dir="ltr"><div><div><div><div><div><div>Hi all,<br><br> I wanted to share a brief case study on the current dependency skew of ImgLib2-algorithm-related components.<br><br> Last week, an<span> </span><a href="https://github.com/imglib/imglib2-algorithm/commit/e1460f140a0b03554fcb6f3d14ca43362d7d86a5" target="_blank">innocent-looking commit</a><span> </span>was merged into imglib2-algorithm. It then made its way into a patch release of imglib2-algorithm, and<span> </span><a href="https://github.com/imagej/pom-imagej/commit/d28f954494f76898d80296b168b5352238d25915" target="_blank">patch release of pom-imagej</a>. Unfortunately, even a trivial package move like this is actually a breaking API change, and both the component and pom releases should have incremented a major version to indicate this.<br><br></div> Further, pom-imagej now declares a set of components that are incompatible with each other - as components downstream of imglib2-algorithm are not updated to use the new packages. Thus if these libraries were consolidated (e.g. to upload to Fiji), there would be hit by dependency skew.<br><br></div> For those interested, there are two possible solutions:<br><br></div>1) Track down all uses of the old packages, update them, cut releases, update pom-imagej.<br></div>or<br></div>2) Add deprecated, trivial extensions of the moved classes back to the old locations, which can then be removed at a later date.<br><br></div> Naturally, #2 is much simpler and thus looking more attractive right now. :) Either way, developers should be aware of the current problems with pom-imagej 5.12.3 and 5.13.0 (the latter also points to an unreleased ij1-patcher, due to incompatibilities with ImageJ 1.49p - so certainly don't use that one).<br><br><div><div> Our versioning practices are on the wiki:<span> </span><a href="http://imagej.net/Architecture#Versioning" target="_blank">http://imagej.net/Architecture#Versioning</a><span> </span>but please let us know if anything is unclear or hard to find.<br><br></div><div> The burden of manually accounting for SemVer changes is hopefully one we will soon be free from. For now, it's just something we have to consider whenever we cut releases.<br><br></div><div>Best,<br></div><div>Mark</div></div></div></div></div></div></blockquote></div><br></div></div></blockquote></div><br></div></div></div>
_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br><a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br></blockquote></div><br></div></div></blockquote></div><br></div>
_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net">ImageJ-devel@imagej.net</a><br>http://imagej.net/mailman/listinfo/imagej-devel<br></blockquote></div><br></div></body></html>