On Wed, 25 Sep 2019 at 16:59, Gary Gregory <[email protected]> wrote: > > On Wed, Sep 25, 2019 at 8:44 AM sebb <[email protected]> wrote: >> >> On Wed, 25 Sep 2019 at 11:34, Roberto Oliveira <[email protected]> wrote: >> > >> > On Wed, Sep 25, 2019 at 12:31 PM sebb <[email protected]> wrote: >> > > >> > > On Wed, 25 Sep 2019 at 07:41, Daniel Kreling <[email protected]> wrote: >> > > > >> > > > We need to build the package from source >> > > >> > > In which case you should be using the formal release package. >> > > >> > > > and we need to know precisely >> > > > where the development ended. >> > > >> > > What do you mean by that? >> > He means that if he wants to build version 2.6 from source he doesn't >> > know from where he should build. >> >> He should build from the official source release. >> >> These are linked from the download page, i.e. >> >> https://commons.apache.org/proper/commons-io/download_io.cgi >> >> For automated builds you can use: >> >> http://www.apache.org/dyn/closer.cgi/?filename=commons/io/source/commons-io-2.6-src.zip&action=download >> >> You should check the sig or hash from: >> https://www.apache.org/dist/commons/io/source/commons-io-2.6-src.zip.asc >> https://www.apache.org/dist/commons/io/source/commons-io-2.6-src.zip.sha256 >> >> You can replace .zip with .tar.gz above >> >> > Can you or someone confirm the version 2.6 was built from tag >> > "commons-io-2.6-RC3" ? >> >> Only the source packages linked from the download page are official releases. > > > But that does not address the poster's question. If we are confident that > commons-io-2.6-RC3 is indeed 2.6, then we should create a tag called > rel/commons-io-2.6, right?
The tag would not be an official source release. > Gary > >> >> > > >> > > > Thanks, >> > > > Daniel >> > > > >> > > > On Tue, Sep 24, 2019 at 6:52 PM sebb <[email protected]> wrote: >> > > > > >> > > > > Might I ask why the tag is so important? >> > > > > >> > > > > If you are looking to download the source, then that is available >> > > > > from >> > > > > the usual download page: >> > > > > >> > > > > https://commons.apache.org/proper/commons-io/download_io.cgi >> > > > > >> > > > > On Tue, 24 Sep 2019 at 11:32, Roberto Oliveira <[email protected]> >> > > > > wrote: >> > > > > > >> > > > > > Hi Gary, >> > > > > > >> > > > > > Thanks for looking at it. Is there any update? >> > > > > > >> > > > > > On Fri, Sep 20, 2019 at 2:10 PM Gary Gregory >> > > > > > <[email protected]> wrote: >> > > > > > > >> > > > > > > Looking... >> > > > > > > >> > > > > > > On Fri, Sep 20, 2019 at 7:32 AM Daniel Kreling >> > > > > > > <[email protected]> wrote: >> > > > > > >> >> > > > > > >> Hi >> > > > > > >> >> > > > > > >> I am looking for the final tag for commons-io version 2.6 and I >> > > > > > >> have >> > > > > > >> not been able to find it [0]. The last one I can see is the >> > > > > > >> commons-io-2.6-RC3, released in Oct 2017, which I assume to be >> > > > > > >> the >> > > > > > >> final one. >> > > > > > >> >> > > > > > >> Is there a "Final" tag for commons-io, or one which I can >> > > > > > >> explicitly >> > > > > > >> tell it's the final one? >> > > > > > >> If not, is it possible for you to create one, please? >> > > > > > >> >> > > > > > >> [0] https://github.com/apache/commons-io/releases >> > > > > > >> >> > > > > > >> Thanks, >> > > > > > >> Daniel >> > > > > > >> >> > > > > > >> --------------------------------------------------------------------- >> > > > > > >> To unsubscribe, e-mail: [email protected] >> > > > > > >> For additional commands, e-mail: [email protected] >> > > > > > >> >> > > > > > >> > > > > > >> > > > > > -- >> > > > > > Regards, >> > > > > > Roberto Oliveira >> > > > > > >> > > > > > --------------------------------------------------------------------- >> > > > > > To unsubscribe, e-mail: [email protected] >> > > > > > For additional commands, e-mail: [email protected] >> > > > > > >> > >> > >> > >> > -- >> > Regards, >> > Roberto Oliveira --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
