| Age | Commit message (Collapse) | Author |
|---|
|
Add upload_file() temporary file unlinking (or the lack of it) to Pomf
2.1.0 changed features.
|
|
Actually, this is not what we want to note. The change log was
added to this release as a new feature, thus it is not a fix to a
previous release.
This reverts commit a7e0c93be2952910e454c7ad8b3ebc57d0bc902c.
|
|
Add recent two changelog meta fixes to Pomf 2.1.0 fixed features. These
commits are:
- CHANGELOG: Move "removed" before "fixed" sections (a64dea5)
- CHANGELOG: Move 1.0.0+8757e9a XSS to security section (a8aff8d)
|
|
Per "Keep a CHANGELOG" guideline.
See: http://keepachangelog.com/
|
|
Per "Keep a CHANGELOG" guideline.
See: http://keepachangelog.com/
|
|
For Pomf 2.1.0, add improved abbreviation support to added features.
For Pomf 2.0.3, add missing space character before file size to fixed
features.
|
|
Add Japanese "baka" lang attribute fix to Pomf 2.0.3 fixed features.
|
|
Add "Response: Return 500 Internal Server Error on error()" (commit
18f66c8) to fixed issues in Pomf 2.0.3.
|
|
Add changed contact email (info@pantsu.cat) to changes in Pomf 2.1.0.
|
|
Create a new section for unreleased Pomf 2.0.3.
Mention the fixed bug where the FAQ would incorrectly refer to
uploaded/published works as "content".
|
|
Add output buffering to 2.1.0 deprecated features.
|
|
Sometimes I have been slightly inconsistent and used 72 characters limit
for wrapping. The 72 character line wrap is a habit from emails. The
intention is to use 80 characters for change logs.
|
|
Add PHPDoc DocBlocks feature to 2.1.0 added features (merge commit
52a6916abe3a9fe74c4d86bee5536557c7a6fa5d).
|
|
get_sha1() was deprecated in a5314a2ff4cb503ff41da13ffd0e907f49ee4009,
so formally $sha1 was also formally deprecated but not commented.
Clarify we really want to deprecate $sha1 too.
Updates CHANGELOG.md.
|
|
Add two topics merged recently to master:
- Merge branch 'wub/refactor-upload_file'
- Replace include_once statements with require_once
Signed-off-by: Juuso Lapinlampi <wub@partyvan.eu>
Signed-off-by: Austin Gillmann <alucard@cuntflaps.me>
Reviewed-by: Austin Gillmann <alucard@cuntflaps.me>
|
|
Pomf 2.0.2 has been released today and tagged v2.0.2.
|
|
See: 25ec99f6f8b184dc29804358185104c800f2bcdb
|
|
One v1.0.0 change log line was too long and to wrapped to 80 characters.
Fixes commit e09581c06b8340309f86d2dc3ef2a5cd4defeaae.
|
|
Replaces 1.0.0+8757e9a change log stub with verbose, full change logs.
I am so glad I did not have to write every single moe panel change and
README.md comment about how moe panel is shit into these logs. The
commit history is awful around v1.0.0 and 1.0.0+8757e9a.
There are some things here that I took liberally, for example cenci0's
case 413 decoding hack which in turn was actually a bug itself and fixed
later in 2.0.x. So, I simply called it a "HTML validation" fix.
While we are here, clarify that there was no formal release for this
version.
|
|
As explained in v1.0.0 tag message, the 1.0.0 tag is incorrectly
positioned to mark a release. v1.0.0 is the superset at the point when
it was merged to nokonoko/Pomf.
|
|
Replaces stub 1.0.0 change logs with verbose ones.
tits.php was added but then removed before it made into the 1.0.0
"release", and thus not mentioned in these change logs.
Grunt was added in, but Swig pages only came in the next commit and the
Git history is linear rather than branched. Thus, 1.0.0's Grunt build
system is "broken" and only partially implemented.
|
|
See: 617c4409e76b4a86316c81b50ff1edca70b329e2
|
|
|
|
camelCase is the preferred coding style for function names in the PSR-2
coding style guide used by Pomf since version 2.0.0.
Reference: http://www.php-fig.org/psr/psr-2/
|
|
There are two issues with get_sha1():
- The function name doesn't follow the PSR-2 coding style guide for
function naming, followed in Pomf since version 2.0.0.
- SHA-1 is no longer considered resilient to collisions, versus SHA-256.
In current plans, this feature is to be replaced with getHash() or
similar function name in the next major version (Pomf 3.0.0).
For consideration for future SHA-256 hashing implementation, the MySQL
schema's hash value needs to be changed from char(40) to char(64) to
accommodate the longer SHA-256 length of 64 bytes in hexadecimal string.
|
|
|
|
File expiration support has never been properly implemented in Pomf core
or moe panel. It serves as legacy baggage before nekunekus got an idea
to create nokonoko/Uguu for temporary uploads.
In current plans, this non-feature will be removed in the 3.0.0 release
which is the next SemVer major version that allows to remove this.
Reviewed-by: Austin Gillmann <alucard@cuntflaps.me>
|
|
Fixes commit 6495e3a214e6c745f06a9b842ef2e59a9c116c7c.
Also fix the incorrect name of Gruntfile to Gruntfile.js.
Reference:
http://www.cirosantilli.com/markdown-style-guide/#what-to-mark-as-code
|
|
Add a mention about HTML metadata generator value.
|
|
|
|
I have a belief that Swig banners are a Grunt only thing, and they don't
really integrate very well into Swig anyway. It's kind of a hack, and a
bad one because we don't need it anymore.
By deprecating Swig banners, we should have easier time replacing
Grunt/npm with Make in a future release.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Pomf 2.1.0 has not been released yet, but we're keeping track of changes
anyway as per "Keep a CHANGELOG" [1] guidance. Thus, the date is marked
"Unreleased".
More changes will be tracked as development will continue and progress
forward.
[1]: http://keepachangelog.com/
|
|
|
|
|
|
Includes changelogs for 1.0.0+8757e9a..v2.0.0. The format used is "Keep
a CHANGELOG" [1] as a result of conversation with Eliot.
For future improvement, changelogs for newer releases (e.g. v2.0.1 and
unreleased v2.1.0) should be written.
[1]: http://keepachangelog.com/
Acked-by: Eliot Whalan <ewhal@pantsu.cat>
|
