Ok, Can't we try to do a dummy release (or a real one as IIRC, one of the
core lib hasn't been built correctly in the 2 last releases), so we could
fill what is missing in the wiki and in the same time we could experiment
Git for a release and fill a .gitignore ?
Btw, because I didn't do any SDK release yet, I probably might miss things
to understand your points, I want to sweep that.
Well, that's a proposal that even if you approve it now will have to be
delayed until the Installer has been released and I played with Mustella to
update the .gitignore
Thanks,
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Monday, March 25, 2013 9:51 AM
To: dev@flex.apache.org
Subject: Re: git commit: Removed files that do actually need to be edited
and commited from time to time
Hi,
But, sorry, the official release build is not supposed to go into a
release branch ?
No but the files needed to compile a release need to be :-)
otherwise guys, why not check in *.swc, .zip and my grand mother photo at
this point ?
No swc or zips should be in Git but we might be able to get a photo of your
grandmother into a mustella test :-)
you can easily turn back on the develop branch doing a git statsh -u "my
release untracked files" before.
Given I might have a few hundred files scattered all over what would be the
best way to do this? ie some I want to push but others I don't. Objvious
only ones I commit will be pushed but I can't do a pull rebase in this
state.
Thanks,
Justin
