Re: Migration to Github

Jim Baker <[email protected]>
Newsgroups gmane.comp.lang.jython.devel
Message-ID <CAOhO=aOtwr4jztE2NOq3ALLFhNYbiaHKL8Md=jBmr4S03hcjkg@mail.gmail.com>
First, awesome work to convert to a Gradle build. This will give us a lot
more versatility for modern Java builds, including publication onto Maven.
Other functionality that is converted over can be presumably done, since
Gradle > Ant in terms of functionality (given the ability to run Ant tasks
from Gradle).

Next, this list seems comprehensive to me, because it removes from the
Jython history anything that is a build artifact, especially large binaries.

The only other thing I can think of is that we may want to revisit
lib-python/2.7/ as a module/external link/however this can be done in git
:) Right now, we have updated this manually by copying over from CPython,
because we have found automatic upstream changes to be highly unstabilizing
to our builds, but we should do a better job of syncing with CPython. So
maybe this should be modeled as a module for now in git? There may be
better approaches, given that submodules might be too independent in their
history. But I wouldn't want this specific aspect to hold up our move to
GitHub.

Regardless, we don't need perfection. We do want to avoid most unnecessary
history that should have never been there because of limitations in how we
brought artifacts/code in from external sources; and your list accomplishes
this goal.

- Jim

-

On Sat, May 20, 2017 at 1:03 PM, Darjus Loktevic <[email protected]> wrote:

> Hey Guys,
>
> As i just got a basic gradle based build working, thought I'd kick off a
> discussion about the necessary tasks/plan:
>
>    1. Complete Gradle support (maybe not complete complete, but enough to
>    do a release and regrtest).
>    2. Rewrite history and remove extlibs.
>    3. Move jython.exe and python27.dll into submodule.
>    4. Share and validate rewritten repo with peers.
>    5. Create and share appropriate permissions in github.com/jython/jython
>    6. Adopt CPython core-workflow https://docs.python.org/
>    devguide/committing.html
>    7. hg.python.org read-only?
>
>
> What am i missing?
>
>
> Thanks,
>
> Darjus
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.