Re: [jgrapht-users] 0.9.1 release proposal

[Chris K W. <ch...@we...>]

this is great new, thanks!

> On Apr 5, 2015, at 4:24 PM, John Sichi <js...@gm...> wrote:
> 
> I got some time for it this weekend, so I just published the release in Maven central.  There will be an official announcement once I've completed the non-Maven portion of the release process, but if you get a chance, please test the release via mvn now to make sure everything is correct.
> 
> On Thu, Apr 2, 2015 at 12:25 AM, John Sichi <js...@gm... <mailto:js...@gm...>> wrote:
> I'll try to get it done sooner if possible.
> 
> On Mon, Mar 30, 2015 at 8:03 PM, Chris K Wensel <ch...@we... <mailto:ch...@we...>> wrote:
> I realized a few minutes after hitting send that independently publishing won’t really work. 
> 
> now that JGraphT is in maven central, and If any users are using JGraphT or have made it an explicit dependency, they will end up with two versions in the CLASSPATH, defeating Ivy/Maven’s attempts at resolving versions.
> 
> If end of April is a hard date, we will need to revert to 0.9.0 for our release.
> 
> ckw
> 
> 
>> On Mar 25, 2015, at 3:48 PM, Chris K Wensel <ch...@we... <mailto:ch...@we...>> wrote:
>> 
>> That’s fair.
>> 
>> but to limit the trouble/confusion by our downstream projects (both open-source and commercial Cascading embedders) and to get the most bake time, I’ll need to 'fork and publish' in our public maven repo under a new group name and without the SNAPSHOT classifier.
>> 
>> we did this some years ago before jgrapht was in maven central.
>> 
>> ckw 
>> 
>>> On Mar 25, 2015, at 1:40 PM, John Sichi <js...@gm... <mailto:js...@gm...>> wrote:
>>> 
>>> Sounds good; I'll try to get around to it by end of April.
>>> 
>>> On Mon, Mar 23, 2015 at 8:16 PM, Chris K Wensel <ch...@we... <mailto:ch...@we...>> wrote:
>>> Hi all,
>>> 
>>> The Cascading project would be very interested in a final release of the current 0.9.1 development branch.
>>> 
>>> We are currently relying on a recent patch that has been committed, but in order to make a Cascading 3.0 final release we would need rely on a SNAPSHOT build.
>>> 
>>> So if there aren’t any outstanding blockers on 0.9.1, I would like to move that the current branch be finalized and released.
>>> 
>>> If there are objections or blockers, I’d be happy to help move any issue forward.
>>> 
>>> ckw
>>> 
>>> —
>>> Chris K Wensel
>>> ch...@we... <mailto:ch...@we...>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/ <http://goparallel.sourceforge.net/>
>>> _______________________________________________
>>> jgrapht-users mailing list
>>> jgr...@li... <mailto:jgr...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/jgrapht-users <https://lists.sourceforge.net/lists/listinfo/jgrapht-users>
>>> 
>>> 
>> 
>> —
>> Chris K Wensel
>> ch...@we... <mailto:ch...@we...>
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the 
>> conversation now. http://goparallel.sourceforge.net/_______________________________________________ <http://goparallel.sourceforge.net/_______________________________________________>
>> jgrapht-users mailing list
>> jgr...@li... <mailto:jgr...@li...>
>> https://lists.sourceforge.net/lists/listinfo/jgrapht-users <https://lists.sourceforge.net/lists/listinfo/jgrapht-users>
> 
> —
> Chris K Wensel
> ch...@we... <mailto:ch...@we...>
> 
> 
> 
> 
> 
> 

—
Chris K Wensel
ch...@we...