Re: Lost changelogs

ida277 <[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <[email protected]>
ida277 wrote
> And there was another one I which I cannot recall right now, but I'll add
> it here, when it hits me again.

plone.app.jquery doesn't even have a CHANGES.rst and additionally it seems
that versions older than 1.4.4 have completely dissapeared, why's that and
where are they?


ida277 wrote
> True. Yet, changelogs are ment to be complete always and how would I know
> something's actually missing, if I just had a look at CHANGES.txt of the
> newest version of a package. I hope it is not expected to do extra
> research to find out about that.

So, if I'd had to do it, what would be a reliable way to get a list of all
versions of a package (via pypi's UI and/or commandline)? A quick search
couldn't help me here.


ida277 wrote
> Additionally I'll have a look at the current status of relevant docs

And yes, it's all there! See " Updating CHANGES.rst
<http://docs.plone.org/develop/plone-coredev/intro.html#updating-changes-rst-and-checkouts-cfg> 
" and the following chapters, shortly I get it like this:
We are all collectively responsible for all packages, practicing best by
always leaving a note in CHANGES and encourage each other to use PR's and do
reviews (e.g. "Hey Ida, you forgot to make a note in CHANGES, please
***CENSORED*** and correct it.").

-ida



--
View this message in context: http://plone.293351.n2.nabble.com/Lost-changelogs-tp7571208p7571299.html
Sent from the Core Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.