Apptainer v1.0.0 Release Candidate 1 is available

[Dave Dykstra]

I am pleased to announce that the Apptainer v1.0.0 Release Candidate 1
is now available for testing!
https://github.com/apptainer/apptainer/releases/tag/v1.0.0-rc.1

Please build and test it in your environment and report problems to
https://github.com/apptainer/apptainer/issues

Although the Apptainer application code rename is now complete, the
rename has not yet been done in the documentation. That is planned to
be completed before the final Apptainer v1.0.0 release.

Questions can be raised here or on the Apptainer #general slack channel.

Dave

[Will Furnass]

On Wed, 19 Jan 2022, 22:17 Dave Dykstra, <d...@fnal.gov> wrote:

I am pleased to announce that the Apptainer v1.0.0 Release Candidate 1
is now available for testing!
    https://github.com/apptainer/apptainer/releases/tag/v1.0.0-rc.1

If the versioning hadn't been 'reset' to 1.0.0 then would this be released as 3.8.1, 3.9 or 4.0 (assuming semver compliance)? Could a note be added to the docs re this discontinuity in versioning? Would be useful to folks moving forwards. 

Cheers,

Will

[Dave Dykstra]

Will,

I'm not sure exactly what kind of note you have in mind in the docs,
please elaborate.

If the apptainer rebranding hadn't happen, this version would have been
3.9.0. If the rebranding had still happened but the number not reset to
1.0.0, it would have been 4.0.0 because some functionality was removed
(most notably the build --remote option and SylabsCloud as a default
library service).

This release candidate has most of the new features, bug fixes, and
changes that went into singularity-ce up through their version 3.9.4,
except where the maintainers of this project disagreed with what went
into singularity-ce since the project fork. The biggest difference that
I can think of is that we do not support the --nvccli option in
privileged mode, since we think it is too big of a security risk. This
release also has the additional major feature of instance checkpointing
which isn't in singularity-ce (at least not yet).

Dave

> --
> You received this message because you are subscribed to the Google Groups "singularity" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to singularity...@lbl.gov.
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/singularity/CAHpBHzBGTb8JeO1CJ0qLUUp4KN3_cZf0RnAKxVWqMe_f7M6_FA%40mail.gmail.com .

[Will Furnass]

Hi Dave,

On Thu, 20 Jan 2022 at 23:15, Dave Dykstra <d...@fnal.gov> wrote:
>
> If the apptainer rebranding hadn't happen, this version would have been
> 3.9.0. If the rebranding had still happened but the number not reset to
> 1.0.0, it would have been 4.0.0 because some functionality was removed
> (most notably the build --remote option and SylabsCloud as a default
> library service).
>
> This release candidate has most of the new features, bug fixes, and
> changes that went into singularity-ce up through their version 3.9.4,
> except where the maintainers of this project disagreed with what went
> into singularity-ce since the project fork. The biggest difference that
> I can think of is that we do not support the --nvccli option in
> privileged mode, since we think it is too big of a security risk. This
> release also has the additional major feature of instance checkpointing
> which isn't in singularity-ce (at least not yet).

Thanks, that's all really helpful. I think including those two
paragraphs in the 1.0.0 release notes / changelog would really help
users' and sysadmins' understanding of the provenance of 1.0.0 and
relationship with the latest Singularity-CE.

Cheers,

Will