Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release process for 1.0 #103

Closed
ViralBShah opened this issue Jul 9, 2011 · 13 comments
Closed

release process for 1.0 #103

ViralBShah opened this issue Jul 9, 2011 · 13 comments
Assignees

Comments

@ViralBShah
Copy link
Member

Do we fork off the codebase for 1.0? We may want to get rid of a number of things from that branch, as it is prepared for release. This issue can also track all the things that are removed and stay only on the development branch.

@ghost ghost assigned StefanKarpinski Jul 9, 2011
@StefanKarpinski
Copy link
Member

Yeah, maybe. Let me look into successful git-based release processes for projects like ours and get back on this.

@JeffBezanson
Copy link
Member

So far I doubt we have the luxury of experimental features. Everything is a frantic attempt to get essential functionality.

@StefanKarpinski
Copy link
Member

Yeah, I agree with this. Let's release 1.0 solidly, regroup, and then start worrying about this.

@ViralBShah
Copy link
Member Author

I meant removing j files that will not be part of the release, removing attic, adding release specific docs and such things. I agree that we are frantically working to get essential functionality.

@ViralBShah
Copy link
Member Author

Just a thought - while we keep referring to the release as 1.0, I don't think the full julia is 1.0. The core language is probably good enough for a 0.9, but standard library is surely at 0.5.

Should we release at 0.5 for now? In general, we may want future releases to be backward compatible with the 1.0 core language - and perhaps we should go to 1.0 after having a couple of intermediate releases.

@StefanKarpinski
Copy link
Member

That's fair. Version inflation seems to be in these days though.

@JeffBezanson
Copy link
Member

If we remove attic where will those files go?
The only file I'm not sure what to do with is vcloud.j, which only works in the terremark environment. Maybe it should go to attic.

@StefanKarpinski
Copy link
Member

I think the idea is that attic gets removed from the release version but can stay in the development version, which seems reasonable enough.

@StefanKarpinski
Copy link
Member

The basic idea is that there's three stages of readiness for production:

  1. branch: experimental, doesn't really work yet, don't merge into master because it will break other peoples systems.
  2. master: everything works so people can develop against it, but things that are maybe not ready for prime-time general usage may still be left laying around as long as they don't get in anyone's way (e.g. vcloud.j or latin1.j).
  3. release: not-ready-for-prime-time stuff removed from master; specific releases are tagged with appropriate names.

@JeffBezanson
Copy link
Member

Sounds good to me. So it seems all we need to do is make a release-1.0 branch at some point, then eventually tag one of its commits as the 1.0 release. I assume after that point only critical bug fixes are allowed in the release branch, and those fixes should be made in the release branch then merged into master if applicable? Then future commits in that branch can be tagged as 1.0.1 etc. if we want.

We probably shouldn't create the release-1.0 branch for at least another month, since at this point there would be too much merging back and forth due to things generally being in flux.

@StefanKarpinski
Copy link
Member

Yeah, that's about it. I'm not sure we need a release-specific branch, just a general release branch and we keep not-fully-ready things off of it. The 1.0, 1.0.1, etc. tags will all be on that branch.

@JeffBezanson
Copy link
Member

GCC keeps multiple release branches so bug fixes can be applied to earlier releases. If somebody depends on the gcc 4.4.x series, they can go from 4.4.1 to 4.4.2 to get bug fixes without disturbing anything else, even when the current version is 4.7.0. I guess we can do that by making new branches off the release branch if necessary?

@StefanKarpinski
Copy link
Member

Yeah, I'm just figuring that's kind of overkill for us at this point. Although maybe we should.

StefanKarpinski pushed a commit that referenced this issue Feb 8, 2018
RFC: Added compat bindings for new Timer code in v0.4
cmcaine pushed a commit to cmcaine/julia that referenced this issue Sep 24, 2020
…-ref

Fix reference to renamed repo in README
Keno pushed a commit that referenced this issue Oct 9, 2023
optimize!: don't look up GlobalRefs on the lhs of an assignment
inkydragon pushed a commit that referenced this issue Dec 15, 2024
Stdlib: SHA
URL: https://github.com/JuliaCrypto/SHA.jl.git
Stdlib branch: master
Julia branch: master
Old commit: aaf2df6
New commit: 8fa221d
Julia version: 1.12.0-DEV
SHA version: 0.7.0(Does not match)
Bump invoked by: @inkydragon
Powered by:
[BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl)

Diff:
JuliaCrypto/SHA.jl@aaf2df6...8fa221d

```
$ git log --oneline aaf2df6..8fa221d
8fa221d ci: update doctest config (#120)
346b359 ci: Update ci config (#115)
aba9014 Fix type mismatch for `shake/digest!` and setup x86 ci (#117)
0b76d04 Merge pull request #114 from JuliaCrypto/dependabot/github_actions/codecov/codecov-action-5
5094d9d Update .github/workflows/CI.yml
45596b1 Bump codecov/codecov-action from 4 to 5
230ab51 test: remove outdate tests (#113)
7f25aa8 rm: Duplicated const alias (#111)
aa72f73 [SHA3] Fix padding special-case (#108)
3a01401 Delete Manifest.toml (#109)
da351bb Remvoe all getproperty funcs (#99)
4eee84f Bump codecov/codecov-action from 3 to 4 (#104)
15f7dbc Bump codecov/codecov-action from 1 to 3 (#102)
860e6b9 Bump actions/checkout from 2 to 4 (#103)
8e5f0ea Add dependabot to auto update github actions (#100)
4ab324c Merge pull request #98 from fork4jl/sha512-t
a658829 SHA-512: add ref to NIST standard
11a4c73 Apply suggestions from code review
969f867 Merge pull request #97 from fingolfin/mh/Vector
b1401fb SHA-512: add NIST test
4d7091b SHA-512: add to docs
09fef9a SHA-512: test SHA-512/224, SHA-512/256
7201b74 SHA-512: impl SHA-512/224, SHA-512/256
4ab85ad Array -> Vector
8ef91b6 fixed bug in padding for shake, addes testcases for full code coverage (#95)
88e1c83 Remove non-existent property (#75)
068f85d shake128,shake256: fixed typo in export declarations (#93)
176baaa SHA3 xof shake128 and shake256  (#92)
e1af7dd Hardcode doc edit backlink
```

Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
DilumAluthge added a commit that referenced this issue Dec 17, 2024
Stdlib: Distributed
URL: https://github.com/JuliaLang/Distributed.jl
Stdlib branch: master
Julia branch: master
Old commit: 6c7cdb5
New commit: c613685
Julia version: 1.12.0-DEV
Distributed version: 1.11.0(Does not match)
Bump invoked by: @DilumAluthge
Powered by:
[BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl)

Diff:
JuliaLang/Distributed.jl@6c7cdb5...c613685

```
$ git log --oneline 6c7cdb5..c613685
c613685 Merge pull request #116 from JuliaLang/ci-caching
20e2ce7 Use julia-actions/cache in CI
9c5d73a Merge pull request #112 from JuliaLang/dependabot/github_actions/codecov/codecov-action-5
ed12496 Merge pull request #107 from JamesWrigley/remotechannel-empty
010828a Update .github/workflows/ci.yml
11451a8 Bump codecov/codecov-action from 4 to 5
8b5983b Merge branch 'master' into remotechannel-empty
729ba6a Fix docstring of `@everywhere` (#110)
af89e6c Adding better docs to exeflags kwarg (#108)
8537424 Implement Base.isempty(::RemoteChannel)
6a0383b Add a wait(::[Abstract]WorkerPool) (#106)
1cd2677 Bump codecov/codecov-action from 1 to 4 (#96)
cde4078 Bump actions/cache from 1 to 4 (#98)
6c8245a Bump julia-actions/setup-julia from 1 to 2 (#97)
1ffaac8 Bump actions/checkout from 2 to 4 (#99)
8e3f849 Fix RemoteChannel iterator interface (#100)
f4aaf1b Fix markdown errors in README.md (#95)
2017da9 Merge pull request #103 from JuliaLang/sf/sigquit_instead
07389dd Use `SIGQUIT` instead of `SIGTERM`
```

Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
stevengj pushed a commit that referenced this issue Jan 2, 2025
Stdlib: SHA
URL: https://github.com/JuliaCrypto/SHA.jl.git
Stdlib branch: master
Julia branch: master
Old commit: aaf2df6
New commit: 8fa221d
Julia version: 1.12.0-DEV
SHA version: 0.7.0(Does not match)
Bump invoked by: @inkydragon
Powered by:
[BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl)

Diff:
JuliaCrypto/SHA.jl@aaf2df6...8fa221d

```
$ git log --oneline aaf2df6..8fa221d
8fa221d ci: update doctest config (#120)
346b359 ci: Update ci config (#115)
aba9014 Fix type mismatch for `shake/digest!` and setup x86 ci (#117)
0b76d04 Merge pull request #114 from JuliaCrypto/dependabot/github_actions/codecov/codecov-action-5
5094d9d Update .github/workflows/CI.yml
45596b1 Bump codecov/codecov-action from 4 to 5
230ab51 test: remove outdate tests (#113)
7f25aa8 rm: Duplicated const alias (#111)
aa72f73 [SHA3] Fix padding special-case (#108)
3a01401 Delete Manifest.toml (#109)
da351bb Remvoe all getproperty funcs (#99)
4eee84f Bump codecov/codecov-action from 3 to 4 (#104)
15f7dbc Bump codecov/codecov-action from 1 to 3 (#102)
860e6b9 Bump actions/checkout from 2 to 4 (#103)
8e5f0ea Add dependabot to auto update github actions (#100)
4ab324c Merge pull request #98 from fork4jl/sha512-t
a658829 SHA-512: add ref to NIST standard
11a4c73 Apply suggestions from code review
969f867 Merge pull request #97 from fingolfin/mh/Vector
b1401fb SHA-512: add NIST test
4d7091b SHA-512: add to docs
09fef9a SHA-512: test SHA-512/224, SHA-512/256
7201b74 SHA-512: impl SHA-512/224, SHA-512/256
4ab85ad Array -> Vector
8ef91b6 fixed bug in padding for shake, addes testcases for full code coverage (#95)
88e1c83 Remove non-existent property (#75)
068f85d shake128,shake256: fixed typo in export declarations (#93)
176baaa SHA3 xof shake128 and shake256  (#92)
e1af7dd Hardcode doc edit backlink
```

Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
stevengj pushed a commit that referenced this issue Jan 2, 2025
Stdlib: Distributed
URL: https://github.com/JuliaLang/Distributed.jl
Stdlib branch: master
Julia branch: master
Old commit: 6c7cdb5
New commit: c613685
Julia version: 1.12.0-DEV
Distributed version: 1.11.0(Does not match)
Bump invoked by: @DilumAluthge
Powered by:
[BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl)

Diff:
JuliaLang/Distributed.jl@6c7cdb5...c613685

```
$ git log --oneline 6c7cdb5..c613685
c613685 Merge pull request #116 from JuliaLang/ci-caching
20e2ce7 Use julia-actions/cache in CI
9c5d73a Merge pull request #112 from JuliaLang/dependabot/github_actions/codecov/codecov-action-5
ed12496 Merge pull request #107 from JamesWrigley/remotechannel-empty
010828a Update .github/workflows/ci.yml
11451a8 Bump codecov/codecov-action from 4 to 5
8b5983b Merge branch 'master' into remotechannel-empty
729ba6a Fix docstring of `@everywhere` (#110)
af89e6c Adding better docs to exeflags kwarg (#108)
8537424 Implement Base.isempty(::RemoteChannel)
6a0383b Add a wait(::[Abstract]WorkerPool) (#106)
1cd2677 Bump codecov/codecov-action from 1 to 4 (#96)
cde4078 Bump actions/cache from 1 to 4 (#98)
6c8245a Bump julia-actions/setup-julia from 1 to 2 (#97)
1ffaac8 Bump actions/checkout from 2 to 4 (#99)
8e3f849 Fix RemoteChannel iterator interface (#100)
f4aaf1b Fix markdown errors in README.md (#95)
2017da9 Merge pull request #103 from JuliaLang/sf/sigquit_instead
07389dd Use `SIGQUIT` instead of `SIGTERM`
```

Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants