Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
vlc
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Redmine
Redmine
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
videolan
vlc
Commits
4839c1c5
Commit
4839c1c5
authored
Oct 18, 2012
by
Jean-Baptiste Kempf
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update the release Howto
parent
5e61e248
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
31 additions
and
41 deletions
+31
-41
doc/release-howto.txt
doc/release-howto.txt
+31
-41
No files found.
doc/release-howto.txt
View file @
4839c1c5
[ Note: this howto is probably useful to core vlc developers only ]
Release HOWTO
-------------
Release HOWTO
-------------
[ Note: this howto is probably useful to core vlc developers only ]
* Tests: compilation, regression tests ...
...
...
@@ -17,42 +17,36 @@
which case the revision goes back to zero.
* Commit
* Tag the commit
* "Tag" the release
git tag -a -m "VLC Release VERSION" <VERSION>
(Create an annotated tag, you can skip -a if you used -m)
git push origin <VERSION>
* Tarballs (Use a clean tree !!!)
- Use 'make distcheck' to make sure all files are exported correctly
- copy the tar.xz file on altair.videolan.org
- copy the binaries files on altair.videolan.org, if possible
- copy the tar.xz file on ganesh.videolan.org
- generate SHA, MD5 hashes and OpenPGP signature of these files
(use sha*sum --binary, md5sum --binary, gpg --sign --detach --armor)
Use the
~/bin/
sumandsign.sh script
Use the sumandsign.sh script
* Contribs
- Put a copy of the libraries or git snapshot in
vlc-X.X.X/contrib
- Put the relevant win32 contrib package
- Update
developer
s.v.o/vlc and www.v.o/vlc/download-sources.html
- Put a copy of the libraries or git snapshot in
ftp://ftp.videolan.org/pub/contrib/
- Put the relevant win32
and Mac OS
contrib package
- Update s.v.o/vlc and www.v.o/vlc/download-sources.html
* Win32 Packages
- configure using the extras/package/win32/configure.sh script
-
move to altair and generate md5 plus SHA1 hashes and gpg signature of these files
(c.f. Tarballs)
-
copy the packages files on ganesh.videolan.org
- copy the vlc-2.0.4 and symbols-2.0.4 to balthazar for stacktraces
* OS X packages
- configure using ./configure --enable-macosx
- compile the source on both a PowerPC and an Intel-based Mac. Don't try to
cross-compile for either platform. Don't forget the framework.
* Mac OS X packages
- configure using the extras/package/macosx/configure.sh script
- compile the source on both a PowerPC and an Intel-based Mac.
- use extras/package/macosx/ub.sh to create a Universal Binary.
- move to altair and generate md5 plus SHA1 hashes and gpg signature of these files
(c.f. Tarballs)
* Commit changes ... it never works the first time
- use extras/package/macosx/codesign.sh to sign it.
- copy the packages files on ganesh.videolan.org
* "Tag" the release
git tag -a -m "VLC Release VERSION" <VERSION>
(Create an annotated tag, you can skip -a if you used -m)
git push origin <VERSION>
* Move the signed files from altair to ganesh, on /opt/ftp/pub/videolan/vlc/X.X.X
* Sign all the files and move the signed files on /opt/ftp/pub/videolan/vlc/X.X.X
- At first block access to this directory by http or ftp. Only authorize rsync.
This is to avoid leak as some journalists and forums seem to watch the ftp.
- Update the "last" symlink
...
...
@@ -62,6 +56,7 @@
- create a /vlc/release/X.X.X page
- add a news item to news.msg
- update the front page OS dependant screenshots if the interface changed.
- update the md5
* "Check for updates" functionality
- edit update.videolan.org/vlc/status
...
...
@@ -69,7 +64,7 @@
* Mirrors (if necessary)
- Forwarn the mirror admins
- Update the list of files for the mirror check
- Update the list of files for the mirror check
(/var/www/local/mirrors.v.o/files)
- Disable mirrors which haven't synced yet and possibly ganesh if there are
enough other mirrors (see http://mirrors.videolan.org/release.html)
...
...
@@ -77,26 +72,21 @@
* Update the wiki
- edit http://wiki.videolan.org/Template:VLC:latest_version
* Announce on www.freshmeat.net (let jb or sam do it)
- you need a freshmeat account
- go to http://www.freshmeat.net/projects/vlc/
- chose "Submit a release" in the right menu
- fill out all the info and submit
- the update can take several hours
* Announce on VersionTracker
- ask Meuuh
* Announce on www.freecode.com (let jb or sam do it, if you lack the account)
- go to https://freecode.com/projects/vlc/
- chose "Submit a release" in the right menu, in "Administration"
- Do the steps and wait (the update can take several hours)
* Announce on
twitter and facebook...
Unfortunately, those are more followed than the
other means
* Announce on
Twitter, Facebook and G+
Unfortunately, those are more followed than the
all other mediums combined
* Announce email and forum topic
-
w
rite something along the lines of previous releases
-
p
ost in videolan-announce (moderated), vlc et vlc-devel
-
W
rite something along the lines of previous releases
-
P
ost in videolan-announce (moderated), vlc et vlc-devel
You are advised to add the author list for this version using
'git shortlog -s PREVIOUS_VERSION..VERSION'
And to add git diff --stat PREVIOUS_VERSION..VERSION if it's relevant.
You can play a bit with git to show the piece of information that may be
interesting.
-
a
dd a sticky thread in the "General VLC media player discussion" forum
-
A
dd a sticky thread in the "General VLC media player discussion" forum
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment