> -----Original Message----- > From: Barrie Treloar [mailto:[email protected]] > Sent: 06 February 2013 02:37 > To: Maven Developers List > Subject: Re: Testing [Vote] plugins? > > On 6 February 2013 10:39, Benson Margulies <[email protected]> > wrote: > > The issue here is that someone in our community might live in a world > > where an MRM has interposed its body, in the words of Lytton > > Strachey, between themselves and all external repos. Such people had > > better follow olamy's advice about downloading source and building it > > themselves. > > They can still do this, they just need to configure their MRM correctly. > > The staging releases should be quarantined on a separate URL. > No developer should be using this particular URL, only the person delegated > to test the staged release. > They should then follow normal practice and delete the quarantined MRM > repository when done.
This then requires more work than is ideal and as such it is likely that me as a community member will be able to do less testing (if any). Testing would be done through the CI environment (which can include automates testing of the built product) and swapping maven settings for jobs, duplicating jobs and fiddling with MRMs is more work than I am able to do. Wouldn't it be nice if all I needed to do was create a branch in my repo and update the plugin version and not have to worry that someone is possibly going to recreate another release with the same version. /James --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
