[Biojava-dev] Code freeze for git transition

[Spencer Bliven]

Is that a problem? I have no idea how to check what version of a maven
plugin is being used.

Michael, would you be willing to look into adapting the release procedure
to the proposed git workflow? I've never had much success understanding the
intricacies of maven.

-Spencer


On Wed, Mar 27, 2013 at 1:53 PM, Michael Heuer <heuermh at gmail.com> wrote:

> Michael Heuer <heuermh at gmail.com> wrote:
> > Spencer Bliven <sbliven at ucsd.edu> wrote:
> >
> >> Last week I suggested this Friday would be a good date for the SVN to
> >> github migration. That would mean that everyone needs to commit all
> >> outstanding code to SVN by 3/29. There will be a code freeze for the
> >> duration of the weekend, after which you can checkout code from github.
> Any
> >> code not checked in by friday would need to be moved over to a git
> >> repository manually, which is doable but somewhat involved.
> >
> > Looking over your transition notes, the only thing that concerns me is
> > whether or not the maven release process (and the maven release plugin
> > in particular) will work with the git branching proposal.  Is there
> > any way to test this before the migration?
> >
> > I have never used the maven release plugin with a git repository, and
> > in fact the only piece of software that makes me curse more than git
> > is the maven release plugin.  :)
>
> http://jira.codehaus.org/browse/MRELEASE
>
> "NOTE GIT users are adviced not to use 2.4 but 2.3.2 instead!"
>
>
> http://jira.codehaus.org/issues/?jql=project+%3D+MRELEASE+AND+resolution+%3D+Unresolved+AND+component+%3D+Git+ORDER+BY+priority+DESC
>
>
> Uh oh.
>
>    michael
>