util-1 and util-2 are checked out and have the same content.
Then a feature in project-1 requires an api incompatible change in util, so the
developer makes those changes in util-1.
Unfortunately, because of our workflow, those changes might be sitting around
uncommitted on the developers m
Le 22 janv. 2014 à 06:27, Stefan Bodewig a écrit :
> On 2014-01-22, Nicolas Lalevée wrote:
>
>> To avoid confusion and make things simpler, I suggest we modify the
>> release process to that everything goes through the svn of
>> dist.apache.org, and not use anymore people.apache.org.
>
> +1
>
+1
2014/1/21 Per Arnold Blaasmo
> +1
>
>
> On 20. jan. 2014 19:19, Charles Duffy wrote:
> > I have built a release candidate for Ivy 2.4.0.
> >
> > You can download it from this URL:
> > http://people.apache.org/~cduffy/ivy-2.4.0-rc1/
> >
> > Do you vote for the release of these binaries?
> >
>
+1
Is it normal that tag name is 1.4_RC1 but not in the maven version or name
in dist.apache.org ?
2014/1/21 Stefan Bodewig
> Hi all,
>
> following the Commons Compress 1.7 release I'd like to release a new
> version of the Antlib as well. Most importantly this adds tasks and
> resources for
On 2014-01-22, Jean-Louis Boudart wrote:
> +1
> Is it normal that tag name is 1.4_RC1 but not in the maven version or name
> in dist.apache.org ?
This vote is not about a RC but I have created an RC and the vote is
about calling that 1.4 - final, if you will.
If the vote passes, I'll copy the t
Fine :)
2014/1/22 Stefan Bodewig
> On 2014-01-22, Jean-Louis Boudart wrote:
>
> > +1
>
> > Is it normal that tag name is 1.4_RC1 but not in the maven version or
> name
> > in dist.apache.org ?
>
> This vote is not about a RC but I have created an RC and the vote is
> about calling that 1.4 - fi
