Some release dates differ from Bram's presentation and Wikipedia #8
Comments
|
Hi Ken, thanks for checking. I also investigated a bit using the tags from the repositories (current, vim-ancient) Here is the date the code was tagged. This is from those two mentioned repositories: Now I also had a look at the vim_announce mailinglist, which seems to So putting it all together, let me update your table:
[6]: I think it is an error in the wikipedia page and very unlikely, that Vim 5.2 was released just 20 days after 5.1 I guess, for some versions the code has just been tagged a bit later, than the actual announcements. |
|
Ah, checking the official announcements is a good way. BTW, vim-ancient has the history only between v5.5 and v6.4, and we don't have older history than that. Only we have tarballs in the official FTP site. |
|
I created the vim-ancient repository by git importing the old CVS repository (which I think is still available at the vim.sf.net webpage.) It only had the version back until tag 5.4.something. I agree joining with your vim-history repository would be nice and sometimes looking up some things back in the old code was a nice excercise :) So yeah, something below the official repository github.com/vim/ would be really cool. |
|
Christian, Ken -
I created the vim-ancient repository by git importing the old CVS
repository (which I think is still available at the vim.sf.net
webpage.) It only had the version back until tag 5.4.something.
I agree joining with your vim-history repository would be nice and
sometimes looking up some things back in the old code was a nice
excercise :) So yeah, something below the official repository
github.com/vim/ would be really cool.
Feel free to create this. I don't have a big interest or preference on
how to do this. It could be useful to find out some changes in the
past.
I believe the release dates are used are when the announcement went out.
Sometimes the code was already there for a few days.
- Bram
…--
Don't Panic!
-- The Hitchhiker's Guide to the Galaxy
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
|
|
I transferred my vim-history repository to https://github.com/vim/vim-history (with archived status). It seems that I don't have write access to the repository, but it should be okay. |
|
I also created a mirror of vim-ancient to https://github.com/vim/vim-ancient . |
|
If you unarchive vim-history, I would create a PR which contains the merged history of our both repositories: |
|
Oh, I didn't think that we can merge the two repositories. Then we can remove https://github.com/vim/vim-ancient . @brammool Could you add the admin rights of https://github.com/vim/vim-history and https://github.com/vim/vim-ancient to me and @chrisbra ? |
|
Oh, I didn't think that we can merge the two repositories. Then we can remove https://github.com/vim/vim-ancient .
Unfortunately I cannot unarchive vim-history.
@brammool Could you add the admin rights of https://github.com/vim/vim-history and https://github.com/vim/vim-ancient to me and @chrisbra ?
Looks like that doesn't worked as long as it's archived.
I unarchived it.
…--
"Making it up? Why should I want to make anything up? Life's bad enough
as it is without wanting to invent any more of it."
-- Marvin, the Paranoid Android in Douglas Adams'
"The Hitchhiker's Guide to the Galaxy"
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
|
|
@brammool Thank you! @chrisbra Is it better to push your commits directly to https://github.com/vim/vim-history by using |
|
@k-takata Have a look at https://github.com/chrisbra/vim-history/ @brammool can you please give us commit rights? I'll force push then (for now to a different branch) so that we can make sure everything is correct. thanks! |
|
@chrisbra chrisbra/vim-history@1ccf3fa#diff-04c6e90faac2675aa89e2176d2eec7d8R6 chrisbra/vim-history@1ccf3fa#diff-04c6e90faac2675aa89e2176d2eec7d8R9 |
|
Christian -
@k-takata
I think tags should still be correct. README.md has also been updated. I tried pushing to a new branch, but don't have permissions to do so.
Have a look at https://github.com/chrisbra/vim-history/
@brammool can you please give us commit rights? I'll force push then
(for now to a different branch) so that we can make sure everything is
correct.
Should work now.
- Bram
…--
I have a drinking problem -- I don't have a drink!
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
|
|
@k-takata @k-takata and @brammool I did not want to replace the old master branch as Kens repository seems to be gone. So if you both are satisified, we can simply remove the old branch and rename the newhistory branch back to master. Thanks! |
|
BTW: Does it make sense to include the release table into the project Readme? |
|
PS: Oh I just saw, that the release dates are now also visible at https://github.com/vim/vim-history/releases |
It's okay for me. Please go ahead.
That might be good.
Yeah, but I tagged them based on the dates written in |
|
Can I delete the https://github.com/vim/vim-ancient repository? |
|
Hmm, It seems that the commits after v5.5 have different hash IDs from https://bitbucket.org/vim-mirror/vim-ancient . |
|
Yeah, since I was using And I forgot to push the tags. That is fixed now. The master branch now contains all tags, the newhistory branch has been removed and the release table has also been included into the README.md. I think I am done now. If you think there is something missing in the README, feel free to amend it. |
|
Oh and sure, feel free to remove the vim-ancient repository again. |
|
It seems that the tags are on an orphan branch instead of the master branch. When I tried the command |
|
according to my history file, I did run |
|
Ah, understand. I also found that the following tags are exist in the CVS repository, but missing in the vim-ancient repository: I don't know how to fix, though. |
|
Thanks. Well, I think I would not care too much about the "trailing letter tags", that look like alpha/beta releases. The other three, I don't know. I can try to re-import the CVS repository and see if they are there. Not sure if this is worth the effort. |
Agree. |
|
Ah, great. Thanks! |
|
Thanks. Well, I think I would not care too much about the "trailing
letter tags", that look like alpha/beta releases. The other three, I
don't know. I can try to re-import the CVS repository and see if they
are there. Not sure if this is worth the effort.
The pre-release versions often contain bug fixes.
It might be interesting to see what happened just before a release (when
we didn't use version control for distribution).
…--
How To Keep A Healthy Level Of Insanity:
4. Put your garbage can on your desk and label it "in".
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
|
Ah, we use lightweight tags (non-annotated tags), so we don't need to care the author, author date, committer and commit date of the tags. We can just use I have added the missing tags and fixed 2 tags: $ git push -f --tags
Total 0 (delta 0), reused 0 (delta 0)
To github.com:vim/vim-history.git
+ e3b5e1458...cec76bd68 vim-6-1-277 -> vim-6-1-277 (forced update)
+ 349c3f467...92f11cf03 vim-6-2-003 -> vim-6-2-003 (forced update)
* [new tag] vim-6-0-044 -> vim-6-0-044
* [new tag] vim-6-0-159 -> vim-6-0-159
* [new tag] vim-6-0-160 -> vim-6-0-160
* [new tag] vim-6-0ai -> vim-6-0ai
* [new tag] vim-6-0ak -> vim-6-0ak
* [new tag] vim-6-0ao -> vim-6-0ao
* [new tag] vim-6-0d -> vim-6-0d
* [new tag] vim-6-0h -> vim-6-0h
* [new tag] vim-6-0i -> vim-6-0i
* [new tag] vim-6-0k -> vim-6-0k
* [new tag] vim-6-0l -> vim-6-0l
* [new tag] vim-6-0r -> vim-6-0r
* [new tag] vim-6-0s -> vim-6-0s
* [new tag] vim-6-0t -> vim-6-0t
* [new tag] vim-6-0w -> vim-6-0w
* [new tag] vim-6-0z -> vim-6-0z
* [new tag] vim-6-1-276 -> vim-6-1-276
* [new tag] vim-6-1-319 -> vim-6-1-319
* [new tag] vim-6-1-409 -> vim-6-1-409
* [new tag] vim-6-1b-002 -> vim-6-1b-002
* [new tag] vim-6-2-002 -> vim-6-2-002
* [new tag] vim-6-2-278 -> vim-6-2-278
* [new tag] vim-6-2-328 -> vim-6-2-328
* [new tag] vim-6-2-350 -> vim-6-2-350
* [new tag] vim-6-2f-003 -> vim-6-2f-003
* [new tag] vim-6-2f-004 -> vim-6-2f-004
* [new tag] vim-6-3-019 -> vim-6-3-019
* [new tag] vim-6-3b-005 -> vim-6-3b-005
* [new tag] vim-6-3b-017 -> vim-6-3b-017
* [new tag] vim-6-4-003 -> vim-6-4-003
* [new tag] vim-6-4-010 -> vim-6-4-010
* [new tag] vim-6-4a -> vim-6-4a
|
|
I updated the history table. I added information from the source code. |
|
I updated the history table. I added information from the comp.editors news group. I also updated how to merge the history. |
|
Thanks for doing that. I created a PR to add some more links to the release announcements. |
I compared the release dates with Bram's presentation[1] and Wikipedia[2].
[1]: https://www.youtube.com/watch?v=ayc_qpB-93o (1:37)
[2]: https://en.wikipedia.org/wiki/Vim_(text_editor)#History
There are some differences between them: ("=": Same as vim_faq)
I haven't checked the repository, so I don't know which is correct.
The text was updated successfully, but these errors were encountered: