You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Dave Brondsema <da...@brondsema.net> on 2004/07/08 01:31:41 UTC
Re: svn commit: rev 22274 - in forrest/trunk/src/core/context: resources/schema/dtd
skins/common skins/common/xslt/html skins/krysalis-site skins/krysalis-site/css
skins/krysalis-site/xslt/html
thorsten@apache.org wrote:
> Author: thorsten
> Date: Tue Jun 29 13:22:31 2004
> New Revision: 22274
>
> Modified:
> forrest/trunk/src/core/context/resources/schema/dtd/skinconfig-v06-2.dtd
From a theoretical purist perspective, DTDs should never change; we
should make a new file for each version. Practically, it doesn't matter
much when optional parts are added, so don't worry about fixing it this
time. But in the future you should create skinconfig-v06-3.dtd. And
then update references to it in the appropriate places:
src/core/context/resources/schema/catalog.xcat
src/core/context/resources/schema/catalog
src/core/fresh-site/src/documentation/skinconf.xml
src/documentation/skinconf.xml
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: svn commit: rev 22274 - in forrest/trunk/src/core/context: resources/schema/dtd
skins/common skins/common/xslt/html skins/krysalis-site skins/krysalis-site/css
skins/krysalis-site/xslt/html
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
Dave Brondsema wrote:
> thorsten@apache.org wrote:
>
>> Author: thorsten
>> Date: Tue Jun 29 13:22:31 2004
>> New Revision: 22274
>>
>> Modified:
>>
>> forrest/trunk/src/core/context/resources/schema/dtd/skinconfig-v06-2.dtd
>
>
> From a theoretical purist perspective, DTDs should never change; we
> should make a new file for each version.
Ok, I did not know! I was thinking why I was editing the
skinconfig-v06-2.dtd and not v06 ;-).
> Practically, it doesn't matter much when optional parts are added, so
> don't worry about fixing it this time. But in the future you should
> create skinconfig-v06-3.dtd. And then update references to it in the
> appropriate places:
>
> src/core/context/resources/schema/catalog.xcat
> src/core/context/resources/schema/catalog
> src/core/fresh-site/src/documentation/skinconf.xml
> src/documentation/skinconf.xml
>
>
Ok, I will keep that in mind for the next time!
Thanks for the feedback :).
thorsten
--
Thorsten Scherler
Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
Re: svn commit: rev 22274 - in forrest/trunk/src/core/context: resources/schema/dtd
skins/common skins/common/xslt/html skins/krysalis-site skins/krysalis-site/css
skins/krysalis-site/xslt/html
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
Juan Jose Pablos wrote:
> Dave Brondsema escribió:
>
>> thorsten@apache.org wrote:
>>
>>> Author: thorsten
>>> Date: Tue Jun 29 13:22:31 2004
>>> New Revision: 22274
>>>
>>> Modified:
>>>
>>> forrest/trunk/src/core/context/resources/schema/dtd/skinconfig-v06-2.dtd
>>>
>>
>>
>>
>> From a theoretical purist perspective, DTDs should never change; we
>> should make a new file for each version. Practically, it doesn't
>> matter much when optional parts are added, so don't worry about
>> fixing it this time. But in the future you should create
>> skinconfig-v06-3.dtd. And then update references to it in the
>> appropriate places:
>>
>
> SVN is good on keeping version number, I do not see why we need to do
> this by hand.
>
> I think that we should not do it in this way. Should we vote this?
>
I can understand Cheche on that. I think it would be suffient to version
just the focused release.
e.g. I hope to finish up the css-style skin *before* we release 0.6. I
would then extend only the skinconfig-v06.dtd. If we focus the release
0.7. I would add all the changes that I need for 0.7 to the
skinconfig-v07.dtd.
...but I do not see the need to further destinguish between
skinconfig-v06-3.dtd / skinconfig-v06-4.dtd. Another thing is when do I
have to open up a new subversion? As soon as I modify the dtd? If so
what happen if I have to introduce a couple of new elements to the dtd,
should I create a new subversion for each new element.
I reckon before the release we have to merge this version anyway to
skinconfig-v06.dtd, or not? Like Cheche stated we are using SVN so why
not let SVN do the /dirty work/ of (sub)versioning.
King regards
thorsten
--
Thorsten Scherler
Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
Re: DTD version numbers (Was: svn commit: rev 22274)
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
Nicola Ken Barozzi wrote:
> Dave Brondsema wrote:
>
>> On Thu, 8 Jul 2004, David Crossley wrote:
>>
>>> Nicola Ken Barozzi wrote:
>>>
>>>> Juan Jose Pablos wrote:
>>>>
>>>>> Dave Brondsema escribió:
>>>>
>>>> ...
>>>>
>>>>>> From a theoretical purist perspective, DTDs should never change; we
>>>>>> should make a new file for each version. Practically, it doesn't
>>>>>> matter much when optional parts are added, so don't worry about
>>>>>> fixing
>>>>>> it this time. But in the future you should create
>>>>>> skinconfig-v06-3.dtd. And then update references to it in the
>>>>>> appropriate places:
>>>>>
>>>>>
>>>>> SVN is good on keeping version number, I do not see why we need to do
>>>>> this by hand.
>>>>
>>>>
>>>> I think that we should version only released DTDs, not during
>>>> development. As you say, SVN keep track of all commits in any case.
>>>
>>>
>>> That might be okay as long as we release often.
>>
>>
>> Okay. But even during development we still need to have a new DTD if
>> the
>> change is not backwards compatible.
>
>
> If we change a released DTD we change the version, if not we don't.
>
+1
--
Thorsten Scherler
Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
Re: DTD version numbers (Was: svn commit: rev 22274)
Posted by Dave Brondsema <da...@brondsema.net>.
On Thu, 8 Jul 2004, Nicola Ken Barozzi wrote:
> Dave Brondsema wrote:
>
> > On Thu, 8 Jul 2004, David Crossley wrote:
> >
> >>Nicola Ken Barozzi wrote:
> >>
> >>>Juan Jose Pablos wrote:
> >>>
> >>>>Dave Brondsema escribió:
> >>>...
> >>>>> From a theoretical purist perspective, DTDs should never change; we
> >>>>>should make a new file for each version. Practically, it doesn't
> >>>>>matter much when optional parts are added, so don't worry about fixing
> >>>>>it this time. But in the future you should create
> >>>>>skinconfig-v06-3.dtd. And then update references to it in the
> >>>>>appropriate places:
> >>>>
> >>>>SVN is good on keeping version number, I do not see why we need to do
> >>>>this by hand.
> >>>
> >>>I think that we should version only released DTDs, not during
> >>>development. As you say, SVN keep track of all commits in any case.
> >>
> >>That might be okay as long as we release often.
> >
> > Okay. But even during development we still need to have a new DTD if the
> > change is not backwards compatible.
>
> If we change a released DTD we change the version, if not we don't.
>
I think there are enough people who use the dev version that in a way all
DTDs are "released". Changing the version when a backwards-incompatible
change occurs means end-users of the dev version will become aware of the
significant change even if they don't follow the mailing lists closely.
Hopefully this won't happen much anyway before we go to the new skinconf
format which will have a stable DTD.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: DTD version numbers (Was: svn commit: rev 22274)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Dave Brondsema wrote:
> On Thu, 8 Jul 2004, David Crossley wrote:
>
>>Nicola Ken Barozzi wrote:
>>
>>>Juan Jose Pablos wrote:
>>>
>>>>Dave Brondsema escribió:
>>>...
>>>>> From a theoretical purist perspective, DTDs should never change; we
>>>>>should make a new file for each version. Practically, it doesn't
>>>>>matter much when optional parts are added, so don't worry about fixing
>>>>>it this time. But in the future you should create
>>>>>skinconfig-v06-3.dtd. And then update references to it in the
>>>>>appropriate places:
>>>>
>>>>SVN is good on keeping version number, I do not see why we need to do
>>>>this by hand.
>>>
>>>I think that we should version only released DTDs, not during
>>>development. As you say, SVN keep track of all commits in any case.
>>
>>That might be okay as long as we release often.
>
> Okay. But even during development we still need to have a new DTD if the
> change is not backwards compatible.
If we change a released DTD we change the version, if not we don't.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: DTD version numbers (Was: svn commit: rev 22274)
Posted by Dave Brondsema <da...@brondsema.net>.
On Thu, 8 Jul 2004, David Crossley wrote:
> Nicola Ken Barozzi wrote:
> > Juan Jose Pablos wrote:
> > > Dave Brondsema escribió:
> > ...
> > >> From a theoretical purist perspective, DTDs should never change; we
> > >> should make a new file for each version. Practically, it doesn't
> > >> matter much when optional parts are added, so don't worry about fixing
> > >> it this time. But in the future you should create
> > >> skinconfig-v06-3.dtd. And then update references to it in the
> > >> appropriate places:
> > >
> > > SVN is good on keeping version number, I do not see why we need to do
> > > this by hand.
> >
> > I think that we should version only released DTDs, not during
> > development. As you say, SVN keep track of all commits in any case.
>
> That might be okay as long as we release often.
>
Okay. But even during development we still need to have a new DTD if the
change is not backwards compatible.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
DTD version numbers (Was: svn commit: rev 22274)
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
> Juan Jose Pablos wrote:
> > Dave Brondsema escribió:
> ...
> >> From a theoretical purist perspective, DTDs should never change; we
> >> should make a new file for each version. Practically, it doesn't
> >> matter much when optional parts are added, so don't worry about fixing
> >> it this time. But in the future you should create
> >> skinconfig-v06-3.dtd. And then update references to it in the
> >> appropriate places:
> >
> > SVN is good on keeping version number, I do not see why we need to do
> > this by hand.
>
> I think that we should version only released DTDs, not during
> development. As you say, SVN keep track of all commits in any case.
That might be okay as long as we release often.
--
David Crossley
Re: svn commit: rev 22274 - in forrest/trunk/src/core/context: resources/schema/dtd
skins/common skins/common/xslt/html skins/krysalis-site skins/krysalis-site/css
skins/krysalis-site/xslt/html
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Juan Jose Pablos wrote:
> Dave Brondsema escribió:
...
>> From a theoretical purist perspective, DTDs should never change; we
>> should make a new file for each version. Practically, it doesn't
>> matter much when optional parts are added, so don't worry about fixing
>> it this time. But in the future you should create
>> skinconfig-v06-3.dtd. And then update references to it in the
>> appropriate places:
>
> SVN is good on keeping version number, I do not see why we need to do
> this by hand.
I think that we should version only released DTDs, not during
development. As you say, SVN keep track of all commits in any case.
> I think that we should not do it in this way. Should we vote this?
Let's not vote on everything, we have to reach consensus, not polarize
every issue needlessly.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: svn commit: rev 22274 - in forrest/trunk/src/core/context: resources/schema/dtd
skins/common skins/common/xslt/html skins/krysalis-site skins/krysalis-site/css
skins/krysalis-site/xslt/html
Posted by Juan Jose Pablos <ch...@che-che.com>.
Dave Brondsema escribió:
> thorsten@apache.org wrote:
>
>> Author: thorsten
>> Date: Tue Jun 29 13:22:31 2004
>> New Revision: 22274
>>
>> Modified:
>>
>> forrest/trunk/src/core/context/resources/schema/dtd/skinconfig-v06-2.dtd
>
>
> From a theoretical purist perspective, DTDs should never change; we
> should make a new file for each version. Practically, it doesn't matter
> much when optional parts are added, so don't worry about fixing it this
> time. But in the future you should create skinconfig-v06-3.dtd. And
> then update references to it in the appropriate places:
>
SVN is good on keeping version number, I do not see why we need to do
this by hand.
I think that we should not do it in this way. Should we vote this?
Cheers,
Cheche