> On Nov 13, 2016, at 6:27 AM, Rainer Müller wrote:
>
> On 2016-11-12 22:30, Ryan Schmidt wrote:
>> We do actually have a "trunk" rsync directory. Isn't the purpose of
>> that to allow users of master to selfupdate using it? I've never
>> tried it.
>
> Even if you change the rsync_dir in macpor
Hi,
to summarize:
- The consensus seems to be that the feature should be in the next
release.
- We're not sure whether that next release should be 2.3.5 or 2.4, but
it should definitely come from the release branch for 2.3.x.
- There are risks associated with releasing a 2.4 that does not have
On 2016-11-12 22:30, Ryan Schmidt wrote:
> We do actually have a "trunk" rsync directory. Isn't the purpose of
> that to allow users of master to selfupdate using it? I've never
> tried it.
Even if you change the rsync_dir in macports.conf, the version on master
is always 2.3.99. This is the same
> On Nov 12, 2016, at 3:30 PM, Ryan Schmidt wrote:
>
> Precisely. Which is why we mustn't cause a downgrade to occur for users of
> master.
Conveniently, https://trac.macports.org/ticket/52855 demonstrates one problem
users will encounter if they downgrade.
> On Nov 12, 2016, at 3:23 PM, Rainer Müller wrote:
>
> On 2016-11-12 21:50, Ryan Schmidt wrote:
>>
>>> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez
>>> wrote:
>>>
On Nov 12, 2016, at 12:44 PM, Rainer Müller
wrote:
master is definitely not in a state to be released, b
On 2016-11-12 21:50, Ryan Schmidt wrote:
>
>> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez
>> wrote:
>>
>>> On Nov 12, 2016, at 12:44 PM, Rainer Müller
>>> wrote:
>>>
>>> master is definitely not in a state to be released, but the
>>> roadmap should be discussed separately. Changing the main
> On Nov 12, 2016, at 3:50 PM, Ryan Schmidt wrote:
>
> One consequence that occurs to me is that people using master
> currently have version 2.3.99. If we branch 2.4 from 2.3, then when
> those users run selfupdate they would be "upgraded" to 2.4 which
> doesn't contain all the features they had
> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez wrote:
>
>> On Nov 12, 2016, at 12:44 PM, Rainer Müller wrote:
>>
>>> On 2016-11-12 17:39, Ryan Schmidt wrote:
>>>
>>> Perhaps it should more properly be called 2.4, but since our master
>>> is in no fix state to be branched for 2.4 at this ti
> On Nov 12, 2016, at 12:44 PM, Rainer Müller wrote:
>
>> On 2016-11-12 17:39, Ryan Schmidt wrote:
>>
>> Perhaps it should more properly be called 2.4, but since our master
>> is in no fix state to be branched for 2.4 at this time and we are
>> still figuring out our release process on GitHub, i
On 2016-11-12 17:39, Ryan Schmidt wrote:
> Many of the changes in 2.3.5 are to deal with the GitHub transition, so I
> would be in favor of releasing this change now as well.
https://github.com/macports/macports-base/blob/release-2.3/ChangeLog
That would be only the warning on 'port sync' for us
> On Nov 12, 2016, at 9:33 AM, Clemens Lang wrote:
>
> Hi *,
>
> On Sat, Nov 12, 2016 at 04:19:44PM +0100, Clemens Lang wrote:
>>
>> https://github.com/macports/macports-base/commit/30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
>
>> commit 30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
>> Author: Clem
Hi *,
On Sat, Nov 12, 2016 at 04:19:44PM +0100, Clemens Lang wrote:
>
> https://github.com/macports/macports-base/commit/30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
> commit 30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
> Author: Clemens Lang
> AuthorDate: Sun Nov 6 18:11:49 2016 +0100
>
>
12 matches
Mail list logo
