Move pandegroup/msmbuilder to msmbuilder/msmbuilder2 (????)

[schwancr]

Now that msmbuilder3 is out, does it make sense to move this to the same location and call it v2, or at least change the name here so that people know they should be moving to the other version?

@rmcgibbo @mpharrigan @kyleabeauchamp

@tjlane @tjlane @tjlane

[tjlane]

i get 3 votes?

yes the name should be changed i think -- to what I NO CARE

[rmcgibbo]

I think we should change the README.md to say that this version is depricated. I'm not sure if moving this repo to msmbuilder/msmbuilder2 is the right thing though, since people who don't know what version number we're on will see two repos named msmbuilder/msmbuilder and msmbuilder/msmbuilder2, and from that i would assume that msmbuilder2 is the more modern version, just by name. Maybe we could name this repo msmbuilder-legacy or something.

[schwancr]

Yea that's a good point, i think legacy or something to that end works for me.

@tjlane how do you feel about this plan?

[rmcgibbo]

Okay, @schwancr, I appoint you to move the repo.

[kyleabeauchamp]

LGTM, I like "legacy".

On Tue, Dec 2, 2014 at 12:04 AM, Christian Schwantes < notifications@github.com> wrote:

Yea that's a good point, i think legacy or something to that end works for me.

@tjlane https://github.com/tjlane how do you feel about this plan?

— Reply to this email directly or view it on GitHub https://github.com/pandegroup/msmbuilder/issues/452#issuecomment-65183864 .

[schwancr]

well that really backfired, huh @tjlane

[tjlane]

you wanted to assign me something? im confused

[schwancr]

alright how about this for a plan then:

pandegroup/msmbuilder --> msmbuilder/msmbuilder-legacy

What's the best mechanism to let people know to upgrade? Should we email msmbuilder-users?

[rmcgibbo]

yes. i can send the email.

[schwancr]

alright this is done now