On 19 September 2012 20:51, Anders Hammar <[email protected]> wrote: > > But this reminds me of another ancient peeve: the process of making > > the release tends to make the SCM page point at the release tag, not > > the trunk. I wish it were otherwise. > > Yes, this is true and there was some user complaining about this not > too long ago. He used that link and checked out that tag and did a > patch, which then didn't apply cleanly onto trunk... > So I guess a new release is the best option then. > > GIT fixes that pet peeve AFAIK as the scm url does not include the branch... unless I have been doing my GIT SCM urls wrong
> /Anders > > > > > > > > >> > >> /Anders > >> > >> On Wed, Sep 19, 2012 at 7:58 PM, Benson Margulies < > [email protected]> wrote: > >>> A typical thing for people to do is to google for maven-foo, find the > >>> published 'site' doc, and then go to the SCM page. > >>> > >>> So, while we've got various ways to rescue people from the confusion > >>> that might ensue if they do the above before the next release, I'd > >>> suggest a point release or some other scheme just to get those scm > >>> pages upgraded. > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
