Migration of jenkins-charm to upstream repo

[Ryan Beisner]

Hi All,

With the Jenkins (master) charm moved into upstream [1], we need to do some
cleanup on the old code/bug spaces [2].

My thought is that we should triage and move any valid LP bugs over to the
upstream issue tracker [3] and retire the old code repo [4] to avoid
confusion in development going forward.

[1]  https://github.com/jenkinsci/jenkins-charm
[2]  https://code.launchpad.net/~charmers/charms/trusty/jenkins/trunk/
[3]  https://github.com/jenkinsci/jenkins-charm/issues
[4]  lp:charms/trusty/jenkins

Any takers?  Additional thoughts on the scope/approach needed here?

Cheers,

Ryan



On Fri, Feb 19, 2016 at 2:27 PM, Jorge O. Castro <jorge at ubuntu.com> wrote:

> Hi everyone,
>
> Just a quick note that the Jenkins charm is now at https://github.com/
> jenkinsci/jenkins-charm
>
> Thanks to the Jenkins folks who worked with us to make this happen!
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160826/592c811b/attachment.html>