Reuben Thomas writes:
> Thanks very much for engaging with my criticism to improve things!
Thanks to you for the suggestions!
--
Bastien
Hello,
Achim Gratz writes:
> No, we shouldn't. It's either automatic or a release, it can't be
> both.
I can't see why. We already "release" automatically new packages.
> Also, the releases are distinct from the ELPA packages and you seem to
> mix up the two. They are not
On 1 November 2016 at 17:01, Bastien Guerry wrote:
>
> Let me know if the current page is at least 90% "good enough" :)
>
You can have your 90% rating now!
Thanks very much for engaging with my criticism to improve things!
--
http://rrt.sc3d.org
Nicolas Goaziou writes:
> This is not what I'm suggesting. Let me try to expunge a bit.
>
> I thing we should automate bugfix releases with regular version
> numbering scheme, e.g., 8.3.7 release, /as a replacement for/
> org-MMDD releases. Therefore:
No, we shouldn't. It's either automatic
Hi,
Reuben Thomas writes:
> 1. The top heading is "Download and install", but the second half of
> the section is a list of links that look like they belong in a
> different section (List of features, Manuals and tutorials…).
I could not find an elegant solution for this. I
Hi Nicolas,
Nicolas Goaziou writes:
> I thing we should automate bugfix releases with regular version
> numbering scheme, e.g., 8.3.7 release, /as a replacement for/
> org-MMDD releases.
Okay.
> Therefore:
>
> 1. org-MMDD could be renamed
Hello,
Bastien Guerry writes:
> We could simply have daily snapshot of the maint branch in addition to
> daily snapshot of the master branch.
>
> For now http://orgmode.org/org-latest.tar.gz is build from the master
> branch, but we could also have
On 1 November 2016 at 10:32, Bastien Guerry wrote:
> Hi,
>
> I changed the order of presentation for installation methods on the
> website, promoting Org ELPA method.
>
That's much better, thanks.
However, I still find the first section of the main page rather confusing.
I
Hi,
I changed the order of presentation for installation methods on the
website, promoting Org ELPA method.
Thanks,
--
Bastien
Hi all,
Nicolas Goaziou writes:
> However, I think we should make more frequent bugfix releases. We may
> even automate such releases, e.g., one week after the last unreleased
> bugfix in the branch. I don't do releases however, so this may just be
> a weird idea.
>
>
On 31 October 2016 at 14:56, Nicolas Goaziou wrote:
> Hello,
>
> Reuben Thomas writes:
>
> > That's great! However, is a cut of the release branch as good as an
> actual
> > release?
>
> It is better, since it contains more bugfixes than last release
Hello,
Achim Gratz writes:
> Nicolas Goaziou writes:
>> However, I think we should make more frequent bugfix releases. We may
>> even automate such releases, e.g., one week after the last unreleased
>> bugfix in the branch. I don't do releases however, so this may just be
>>
Nicolas Goaziou writes:
> However, I think we should make more frequent bugfix releases. We may
> even automate such releases, e.g., one week after the last unreleased
> bugfix in the branch. I don't do releases however, so this may just be
> a weird idea.
We already have that, it's the Org
Hello,
Reuben Thomas writes:
> That's great! However, is a cut of the release branch as good as an actual
> release?
It is better, since it contains more bugfixes than last release without
adding new features.
However, I think we should make more frequent bugfix releases. We
On 30 October 2016 at 23:57, Josiah Schwab wrote:
> Hi Reuben,
>
> > It would be great if it were possible to install stable org-mode
> > versions from GNU ELPA or MELPA Stable. At present, one has to choose
> > between installing bleeding-edge versions simply, or stable
Hi Reuben,
> It would be great if it were possible to install stable org-mode
> versions from GNU ELPA or MELPA Stable. At present, one has to choose
> between installing bleeding-edge versions simply, or stable versions
> built by hand.
>
> (I am a bit surprised I can’t find anything about this
16 matches
Mail list logo